Back to overview
Lesson 2 of 6

Commission and Deal Configuration

8 min read

Commission configuration is where most implementation errors happen. An operator agrees to a RevShare deal with an affiliate, but the platform is configured with a slightly different calculation -- using gross revenue instead of net, or applying deductions in the wrong order. The affiliate sees lower numbers than expected, disputes the first payout, and trust is damaged before the relationship begins.

Getting commission logic right during implementation means translating your written partner agreements into precise platform rules. Every assumption must be explicit. Every edge case must be tested.

Commission Model Configuration

Start with the commission models you will use at launch. Most operators begin with two or three: a standard CPA for new affiliates, a RevShare option for established partners, and possibly a hybrid for high-value deals. Configure each model as a separate deal template so you can assign them quickly without rebuilding logic for every new partner.

ModelConfiguration ElementsCommon Pitfalls
CPAEvent trigger, payout amount, qualification rules, capsPaying for unqualified conversions without validation delay
RevShareRevenue base (GGR/NGR/lot volume), percentage, deduction orderAmbiguity on what counts as "net" revenue
HybridCPA component + RevShare component, transition triggersUnclear when the CPA portion stops and RevShare begins
TieredVolume thresholds, tier brackets, reset periodsMonthly vs lifetime tiers creating payout disputes
Multi-tierSub-affiliate levels, override percentages per levelCommission stacking exceeding margin on deep hierarchies

Qualification Rules

Qualification rules determine when a conversion counts for commission purposes. A raw registration is not a qualified player, trader, or customer. Qualification rules protect you from paying commissions on low-quality or fraudulent activity. Configure them during implementation, not after you have already paid out on unqualified conversions.

  • Minimum deposit amount -- filters out micro-deposits from bonus abusers
  • Activity threshold -- requires minimum trading volume, bets placed, or purchases completed
  • Time window -- conversion must meet qualification criteria within 7, 14, or 30 days
  • Geo-validation -- confirms the customer is in an approved jurisdiction
  • Duplicate detection -- flags multiple accounts from the same device, IP, or payment method

Deal Templates vs Custom Deals

Create three to five deal templates that cover your standard offers. These become the baseline: new affiliates start on a template deal, and you negotiate custom terms only for proven partners who have earned it. This approach reduces configuration errors (fewer one-off deals to maintain) and creates a natural progression that motivates affiliate performance.

Document the exact calculation logic for each deal template in plain language, not just in platform configuration. When a partner disputes a payout, you need a reference that both sides can read and agree on.

Payout Rules and Schedules

Configure payout rules alongside commission logic. Define the payout cycle (weekly, bi-weekly, monthly), minimum payout threshold, currency, and payment method options. For RevShare deals, decide whether negative carryover applies -- if a referred player wins more than they lose in a given month, does the negative balance carry to the next period or reset to zero?

Negative carryover is standard in iGaming RevShare but uncommon in Forex lot-based models. Make this decision explicit during configuration and communicate it clearly in partner agreements.

Key Takeaways

  • Translate written partner agreements into platform rules with zero ambiguity on revenue base and deduction order
  • Configure qualification rules during implementation to avoid paying on unqualified conversions
  • Build 3-5 deal templates as your standard offers and reserve custom deals for proven partners
  • Document calculation logic in plain language as a dispute reference
  • Define payout cycles, minimum thresholds, and negative carryover policies before onboarding partners