Affiliate Program

Any signed-in OpenFate account can submit an application. The form requires a name or brand, the account email, platform, audience, and promotion plan; website and region are optional. Submission starts a manual review and does not guarantee approval.

The current system does not promise a fixed review time. Your application remains pending until an administrator reviews it. Approval creates your short link, approved commission rule, and earnings dashboard.

Yes. When a rejection reason is provided, it appears on this page. You can update the application and submit it again for manual review.

A short code is assigned during approval, and an administrator can set a custom code at that stage. There is no self-service rename control, so share only the active link shown in your dashboard.

No. The affiliate program pays cash commission from eligible payments. The friend-referral program grants points under a separate rule set. Use the partner link in this dashboard when you want cash-commission attribution.

The system does not automatically approve a channel or campaign. Describe the real platform, audience, and plan in your application and wait for manual review. Confirm any materially different campaign with support before launch.

The server-recorded click must precede new-account creation by no more than 60 days. The claim may finish during the 24-hour new-account grace. This is not an earnings limit; after a valid claim, attribution is permanent.

Only during the new-account grace period. A valid recorded click made before signup may be claimed for up to 24 hours after account creation; an older account cannot be newly assigned or reassigned.

The first valid capture wins. A later link cannot overwrite a stored capture or an attribution already created in the database.

Yes, until the signup attribution is claimed. OpenFate does not fingerprint people or perform cross-device tracking. If local storage is blocked, cleared, or unavailable in private browsing, or the customer changes devices before signup, automatic attribution may fail.

Nothing changes after a valid attribution has been written to the database. The customer may clear storage, change browsers, or use another device; the permanent account-to-partner relationship remains.

No affiliate cookie is used. The short-link redirect provides a one-time proof in the URL fragment, the browser temporarily stores it in local storage, and the server validates the hashed proof against a recorded click before creating attribution.

Yes. A same-site destination can use a link such as openfate.ai/r/luna?to=/bazi. OpenFate localizes the destination from the visitor preference. External destinations, protocols, and extra query or hash data inside the target are discarded for safety.

Not automatically. Cash-commission attribution requires the approved partner link, a valid one-time click proof, and a qualifying new-account signup. A direct visit, coupon, location, phone number, or mention alone does not create entitlement.

No. Self-referral is blocked when attribution is claimed and checked again when a payment is processed, so it cannot create commission.

A click is a recorded short-link visit, a signup is a claimed new-account attribution, and a lifetime paid customer has completed an eligible positive payment. A refund never reduces that customer count; it reverses standard commission but not guaranteed partner commission. Storage loss, device changes, recording limits, or failures can let the redirect succeed without advancing every stage.

The currently eligible purchase categories are paid point packs, paid prepaid Pro or Exclusive passes, and positive-value paid subscription invoices. When OpenFate processes the payment event, the customer must already be attributed and the partner must still be approved.

The default program counts eligible one-time purchases and subscription renewals. If a partner has custom approved terms, the exact recurring or first-payment-only rule appears in their dashboard and applies to future payments.

The default program is recurring and tiered: 20% at the start, then 25% for future eligible payments after 11 distinct referred customers have ever paid. Refunds do not reduce this lifetime tier count. Percentage rules never exceed 25%; your dashboard shows your exact approved rule, which may be custom.

No under the current default calculation. The row snapshots the lifetime paid-customer count already recorded when the payment is processed. The 11th customer's first payment is therefore 20%; after it raises the count to 11, subsequent eligible payments use 25%. Concurrent payments at the boundary can observe the same earlier count.

An administrator can update an approved standard deal, but the change applies only to future payments. A guaranteed partner deal is permanently locked at a recurring 25% with refund and dispute protection and cannot be edited. Each commission stores its resolved rate, gross and commission amounts, currencies, and protection snapshot, so later standard-deal edits do not recalculate history.

Free usage, starter credits, failed or unpaid transactions, and invoices with no positive paid amount do not create cash commission. A coupon or discount does not disqualify an otherwise eligible purchase; commission is calculated from the positive amount Stripe reports as paid.

Cancellation creates no commission by itself. Standard commission can later reverse with its payment; guaranteed partner commission remains earned. If Stripe reports another positive eligible paid invoice, the approved recurring rule applies when OpenFate processes it.

Percentage commission stays in the payment currency and is rounded to that currency's smallest Stripe unit. A custom fixed rule uses its configured currency. Totals and payouts remain grouped by currency; OpenFate does not invent an exchange rate.

A new commission normally follows the program’s 30-day payout-review schedule. For standard rows, this period also covers refund and dispute safety; guaranteed partner rows stay protected, and the wait only controls when they become payable. An administrator may approve a row earlier after review. A job on a 1-hour interval changes due rows to payable. If that job is late, payout preview and export still include due rows, and confirmation matures and rechecks the exact signed batch inside one transaction.

After commission becomes payable, payout follows a manual, monthly cycle with no promised fixed calendar date. After coordinating the external transfer, an administrator records the paid timestamp, included count, and any method or reference entered. The system does not verify bank settlement automatically.

The current system does not enforce an automatic minimum. Approved unpaid commission, plus pending commission whose scheduled date has passed, can enter the next signed batch. One signed batch contains at most 5000 commission rows; a truncated remainder needs another batch. Because the transfer rail is manual, confirm practical destination or transfer constraints with OpenFate before your first payout.

The public application does not collect payout credentials, and payouts are not automated through Stripe Connect or Wise. OpenFate coordinates the destination manually. After an administrator confirms the external payout, the ledger stores the batch amounts, count, timestamp, and any method or reference entered—not bank credentials.

For a standard deal, a successful refund or opened or lost dispute reverses the matching row; a won dispute restores its prior state. A guaranteed partner row never reverses: OpenFate records and absorbs the later refund or dispute, and the full commission remains pending, payable, or paid.

A matching partial refund conservatively reverses the full standard commission. Guaranteed partner commission remains fully earned after both partial and full refunds because OpenFate covers the refund cost.

Your short link continues redirecting and recording bounded clicks, and existing attribution and ledger history remain. While suspended, new attribution claims and new commissions are blocked. Reactivation can resume future eligible earnings without deleting the prior record.

Not in the current public flow. Region is optional, and the application does not determine legal or tax eligibility or collect tax forms. Because payout is coordinated manually, confirm your country, payout destination, and any required documents with OpenFate before relying on program income.

You can verify lifetime funnel and ledger totals plus bounded recent referrals, commission-basis amounts, resolved rates, protection, statuses, details, and payout batches. The gross figure is the basis of active commission rows, not every historical Stripe sale. Amounts stay in their recorded currencies without invented exchange rates.

Lifetime aggregate statistics use the full stored record. The detailed view is limited to the 100 most recent referrals, 100 commissions, and 50 payouts. An older reversal can therefore change a lifetime total without appearing in the recent table. Older rows remain stored, but partners do not yet have a self-service full-history export.

It appears after Stripe confirms a successful eligible payment and OpenFate processes the payment webhook—not when the customer merely opens checkout or submits a card. Webhook processing can be later than the customer-facing success screen.

No. Each eligible payment has a unique event key in the commission ledger. Retried or overlapping Stripe notifications cannot insert a second row with that key.

Check that the approved link was used, signup happened in the same browser within the window, the account was new, attribution completed before payment, your partner status was approved, and the payment was successful and eligible. If those conditions were met, contact OpenFate with the date, product, currency, and customer account email—never card or bank data—for reconciliation.

Only the masked account email needed to distinguish referral rows, together with signup and payment-derived ledger facts. Full contact details, card numbers, bank details, authentication data, and private OpenFate content are not exposed to partners.