Affiliate Payment Terms Benchmarks 2026 (All Verticals)

Five dimensions define an affiliate payment policy: frequency, minimum payout threshold, payment-method mix, hold-back and carryover treatment, and the dispute or clawback window. Across every vertical benchmarked here, monthly settlement on NET15 terms is the single most common frequency, minimum thresholds cluster at $100 in iGaming and $250 in forex, hold-backs run 5-15% of the payable balance where they are applied at all, and clawback windows sit at 30-90 days from the commission event. Every figure below is presented as a range with a median, because payment terms vary with licence, partner size, settlement currency, and negotiated exceptions. Ranges that are not published in operator rate cards are labelled as Track360 cross-program analysis (anonymized aggregates), and the method behind them is stated in full in the methodology section.

Master Table: Payment Terms by Vertical, 2026

Five verticals and five terms dimensions produce the 25 benchmark cells in the master table below. The ranges describe what a mid-sized partner should expect on a standard agreement, not what a super-affiliate negotiates: partners above roughly $25,000 per month in commissions routinely secure shorter terms, waived thresholds, and reduced hold-backs, and those exceptions are excluded from the ranges so that the medians describe the standard offer rather than the tail. Where a figure comes from published operator terms and conditions it is marked published; where it comes from Track360 cross-program analysis of anonymized aggregates it is marked aggregate.

Two terms in the table are routinely confused and worth defining precisely before the numbers are read. Payment frequency is how often a payout run happens: monthly means one run per calendar month, weekly means one per week, and the frequency alone says nothing about how quickly money moves. NET terms describe the lag between the close of the earning period and the payment date, so NET15 on a monthly cycle means commissions earned in June are paid by July 15. A program can be monthly and fast (NET7) or weekly and slow, though the second combination is rare. The two settings compound into the metric partners actually care about, which is worst-case time to cash: under monthly NET30, a commission earned on the first day of a month waits up to 60 days for payment, while the same commission under weekly NET7 waits at most 14. Programs that advertise frequency without terms, or terms without frequency, are describing half the policy.

Payment Frequency: Monthly NET15 Is the Default Across iGaming

Monthly settlement on NET15 terms is the default in iGaming, meaning commissions earned in a calendar month are paid within 15 days of month end. That single convention covers the clear majority of casino and sportsbook programs benchmarked here. NET30 is the second most common iGaming pattern and is heavily concentrated among large multi-brand groups whose finance cycles run on standard supplier terms rather than affiliate-specific ones. NET45 appears in iGaming only in unusual cases, typically newly launched brands managing cash flow, and it is a reliable warning sign rather than a neutral commercial choice. Forex and prop programs behave differently: weekly and bi-weekly runs are common because IB commissions accrue on closed trades that are already settled, so there is no equivalent of the player-refund exposure that justifies longer holds in gambling.

The commercial logic behind the spread is refund exposure, not generosity. A SaaS program paying 20-30% recurring commission on a subscription with a 30-day money-back guarantee cannot safely settle before that guarantee expires, which is why NET30 is standard and why SaaS clawback windows are usually tied directly to the refund policy rather than set independently. An iGaming CPA deal has a comparable exposure in the qualification period: a first-time depositor who is later found to be a duplicate account, a bonus abuser, or a self-referral must be reversed, and NET15 exists to give the fraud review a window. Programs that pay weekly in iGaming are either running pure RevShare on already-settled NGR or are accepting a higher reversal rate as a partner-acquisition cost.

The reconciliation cycle behind the payment date is where most programs actually lose time. A monthly NET15 run has roughly 15 working days to close the commission ledger, apply reversals for chargebacks and fraud closures, resolve any qualification-rule exceptions raised during the month, convert balances into settlement currencies, apply thresholds and hold-backs, generate self-billing statements, and execute the payment run across multiple rails. Programs that perform those steps inside the tracking platform typically finish in under a day; programs that export to spreadsheets and reconcile manually routinely need a week and pay late in months with unusual reversal volume. That is why lengthening terms is so often a symptom of process rather than cash: a program that cannot close its ledger in 15 days will eventually move to NET30 and describe it as a policy change.

Minimum Payout Thresholds by Vertical and Currency

Minimum payout thresholds cluster at $100 in iGaming and $250 in forex, and the gap between them is a wire-cost artefact rather than a statement about partner value. Forex and IB programs settle a higher proportion of payouts by international bank transfer, where a single SWIFT payment can cost $15-$40 in sending and correspondent fees, so a higher floor keeps the fee ratio defensible. iGaming programs lean on e-wallets with flat or near-zero sending costs, which supports a lower floor. SaaS programs sit lowest at a $50 median because payouts route through platforms such as Payoneer or PayPal where the marginal cost of an additional payout approaches zero. Thresholds are almost always cumulative: a balance below the floor rolls forward rather than expiring, and any program that expires sub-threshold balances should be treated as a material term, not a formality.

Currency handling is the term most often left undefined and most often disputed. Three questions decide whether a threshold is workable in practice. First, is the threshold evaluated in the commission currency or the payout currency, because a partner earning in EUR and paid in USD can sit above the floor in one and below it in the other. Second, which rate and which timestamp convert the balance, since a month-end rate and a payment-date rate produce different amounts on the same ledger. Third, who absorbs the conversion spread and the receiving bank's fees. Programs that answer all three in the agreement generate materially fewer payment disputes than programs that answer none, and the answers cost nothing to write down.

Payment Method Mix: Bank Transfer, Skrill, Neteller, Crypto, Payoneer

Five payout rails cover the overwhelming majority of affiliate payments in 2026, and the mix differs sharply by vertical. Bank transfer and Skrill remain the two most common rails in iGaming, with Neteller close behind and still meaningful for partners in markets where it has a long installed base. Crypto settlement, predominantly USDT on low-fee networks, has become the default rail in prop trading and in crypto-vertical programs, and it is now a standard secondary option in iGaming rather than an exotic one. Payoneer dominates SaaS and cross-border e-commerce because it solves the receiving-side compliance and local-currency problem that neither wire nor e-wallet solves cleanly. PayPal remains common in SaaS and near-absent in regulated gambling, where acceptable-use terms make it unreliable.

Two compliance constraints shape the mix more than partner preference does. The first is the payout-side identity and sanctions check: a program paying a partner in crypto inherits virtual-asset transfer obligations under the FATF travel rule framework in most regulated jurisdictions, which means wallet attribution and beneficiary data have to be captured at onboarding rather than at first payout. The second is licence-driven record keeping. UKGC licence conditions and MGA licensee obligations both require operators to evidence who was paid, for what activity, and against which marketing, so a payout rail that produces a weak audit trail creates a compliance problem regardless of how cheap it is. The practical answer is to support at least two rails per partner, keep a self-billing invoice or statement for every run, and treat the payment-method choice as a compliance decision with a cost attached rather than a cost decision with a compliance footnote.

Rail economics also explain why thresholds and method availability move together, and the arithmetic is simple enough to run per partner. A $40 SWIFT fee against a $250 payout is 16% of the payment; the same fee against a $2,500 payout is 1.6%. A program paying 300 partners monthly by wire spends roughly $4,500 to $12,000 a year in sending fees alone before correspondent deductions, which is why wire-heavy programs raise floors and e-wallet-heavy programs do not need to. Crypto settlement compresses that cost to near zero per payment but adds onboarding cost in wallet verification and travel-rule data capture, so it pays off in programs with many small partners and not in programs with a handful of large ones. The correct model is cost per payout run across the whole partner base, not cost per transaction, and it should be recalculated whenever the partner mix shifts toward or away from the long tail.

Hold-Back and Negative Carryover Practice

Hold-back reserves run 5-15% of the payable balance where programs apply them, and most iGaming casino programs apply none at all. A hold-back is a deliberately retained portion of an otherwise payable commission, released after a defined period once reversal risk has passed; it is distinct from a clawback, which reverses a commission already recognised. Hold-backs are most common in forex and prop programs, where a single funded-trader CPA can be large enough that one reversal wipes out a month of legitimate commission, and least common in mature iGaming RevShare programs, where negative carryover already performs the same protective function. A program that applies both a 15% hold-back and full negative carryover on the same RevShare deal is double-protecting itself, and partners price that in.

Negative carryover is the more consequential term and the one most worth negotiating. Under full negative carryover, a month in which a partner's cohort produces negative NGR, typically because large withdrawals, bonus costs, or a single high-value winning player exceed gross revenue, carries the deficit forward and suppresses the following month's commission until the balance clears. Under a monthly reset, the deficit is written off and the next month starts at zero. The commercial effect is significant: on a 30% RevShare deal, a single negative month can suppress two to four subsequent months of payouts under full carryover, which is why partners consistently value a reset higher than a few percentage points of headline rate. Hybrid treatments are increasingly common: reset after a fixed number of months, reset above a defined deficit ceiling, or carryover applied per brand rather than across an entire portfolio.

Dispute, Clawback, and Chargeback Windows

Clawback windows run 30-90 days from the qualifying event with a median of 60 days, and the window length matters far less than the evidence standard attached to it. A clawback is a reversal of a commission already credited, and it is legitimate in a defined set of cases: chargebacks and payment reversals on the underlying deposit, accounts closed for fraud, duplicate or multi-account signups, self-referral, bonus abuse, and traffic that fails a qualification rule on review. It is illegitimate as a general-purpose margin adjustment, and programs that reserve an unqualified right to reverse any commission at any time for any reason are the single most common source of affiliate disputes in every vertical benchmarked here.

Four attributes separate a defensible clawback policy from a disputed one, and none of them depend on the window length. A defensible policy names the permitted reversal reasons in a closed list, caps the lookback period so a commission becomes final at a known date, provides a per-event reason code and reference rather than a lump-sum adjustment, and gives the partner a stated window to contest with a named route of appeal. Programs meeting all four resolve disputes in days; programs meeting none resolve them by losing the partner. The operational requirement is that the tracking platform records the qualifying event, the reversal, and the reason on the same ledger line, because a reversal that cannot be traced to an event is indistinguishable from an unexplained deduction from the partner's side of the table.

What Payment Terms Signal About a Program

Six payment-terms signals predict program reliability better than the headline CPA or RevShare rate does, and experienced affiliates read them first. Payment terms are the part of an agreement that is expensive to honour and cheap to promise, so the gap between a program's stated terms and its actual behaviour is where its financial position becomes visible. A program moving from NET15 to NET30, quietly raising a threshold, or extending a hold-back release is usually managing cash, and the rate card rarely changes at the same time.

• Terms lengthening without a rate change: NET15 moving to NET30 or NET45 is a cash-flow signal, particularly when it applies to existing partners rather than new ones.
• Threshold increases applied retroactively to accrued balances rather than to future earnings only.
• Hold-back introduced or increased mid-agreement without a corresponding reduction in negative carryover.
• Unqualified clawback rights with no closed list of reasons and no lookback cap, so no commission is ever final.
• Reversals delivered as lump-sum adjustments with no per-event reason code, event date, or reference.
• A single payout rail with no alternative, which turns any processor policy change into a missed payment run.
• Sub-threshold balances that expire rather than roll forward, which quietly writes off the long tail of small partners.
• Geo-targeting or qualification-rule changes applied to historic commissions rather than to traffic from the change date onward.

Operators should treat the same list as a design specification rather than a warning list. The terms that reduce disputes are cheap: a closed list of reversal reasons, a lookback cap, per-event reason codes, a stated dispute window, rolling sub-threshold balances, and at least two configured payout rails. None of those cost commission percentage points, and all of them reduce the volume of manual finance work per payout run. Programs that automate thresholds, hold-back release schedules, carryover treatment, and multi-method payout runs inside the tracking platform close their month in hours; programs that reconcile player lifetime revenue, reversals, and currency conversion by hand close it in days and absorb the dispute load that follows.

Payment terms also interact with commission structure in ways that a rate card alone will not reveal, which is why this benchmark should be read alongside the commission rates benchmark rather than instead of it. A CPA deal front-loads the operator's exposure, so it justifies a longer clawback window and a tighter qualification review, and it is where bonus abuse, multi-account signups, and self-referral schemes concentrate. A RevShare deal on NGR spreads exposure across player lifetime, so it justifies shorter terms and lower hold-backs but raises the stakes on the deduction definition and on negative carryover. Hybrid deals inherit both problems and need both sets of terms written explicitly, because a partner paid a reduced CPA plus a RevShare tail will otherwise discover that the clawback rules for one component were quietly applied to the other. The general rule holds across every vertical benchmarked here: the more of a partner's income depends on events the operator can reverse, the more precisely the reversal terms have to be specified.

How to Use and Cite This Benchmark

Five rules keep citations of this benchmark accurate, and the first one matters most: these are ranges with medians, not averages, and quoting a median as an industry average misrepresents the distribution behind it.

1. Cite with the as-of date. The current data snapshot is July 18, 2026, and the updated date at the top of this page changes with every revision.
2. Quote the range and the median together. Several bands here are bimodal, especially payout frequency in forex, so the median alone describes no real program.
3. Preserve the source label. Cells drawn from Track360 cross-program analysis of anonymized aggregates are marked as such and should not be reproduced as published operator data.
4. Segment by vertical. A $100 threshold is standard in iGaming and low in forex; a single cross-industry number for affiliate payment terms is not meaningful.
5. Link to this page rather than reproducing a static table, so readers land on the current version after the next quarterly review.

Methodology & Sources

Two source classes feed this benchmark, and each cell in every table is attributable to one of them. The first is published program documentation: affiliate terms and conditions, rate cards, and payout policies that operators publish openly, which is the source for payment frequency conventions, stated minimum thresholds, and published clawback language. The second is Track360 cross-program analysis, a set of anonymized aggregates derived from affiliate and IB program configurations running on the Track360 platform across iGaming, forex, prop trading, and SaaS. Aggregates are computed at the program level rather than the partner level, are reported only as ranges and medians, and are never attributed to a named operator. No individual program, partner, or commercial agreement is identifiable from any figure on this page.

Three exclusion rules apply. Programs with fewer than 20 active paying partners are excluded, because small programs produce unstable terms that distort a median. Negotiated exceptions for partners above roughly $25,000 per month in commissions are excluded, so the ranges describe the standard offer rather than the top of the market. Any cell that would require a single-source inference is reported as a range rather than a point value, and no point value on this page is presented with precision the underlying data does not support. Regulatory context on record keeping and marketing compensation draws on UK Gambling Commission licence conditions, MGA licensee obligations, FTC endorsement guidance, ESMA and FCA financial-promotions material for the forex and prop verticals, CFTC oversight material for US-facing derivatives programs, and the FATF virtual-asset framework for crypto settlement. Last updated July 18, 2026. This page is reviewed quarterly in January, April, July, and October, and out of cycle whenever a material shift in payout rails or regulatory obligations occurs. Corrections are welcome: if published operator terms contradict a range here, the published terms win and the table is corrected at the next review.

Payment terms are the cheapest promise in an affiliate agreement and the most expensive one to honour. That is exactly why they predict program reliability better than the headline commission rate does.