Revenue Sharing Online

1) The essence and goals of RevShare

• align incentives (increase in FTD/ARPU/LTV while meeting RG/compliance);
• reduce controversy and Cost-to-Serve through uniform attribution and calculation rules;
• Ensure cache predictability and incident resilience.

2) Basic distribution models

2. 1 Linear (two-sided)

Operator ↔ Partner (studio/affiliate): fixed% of Net Revenue when performing SLO and no sanctions.

2. 2 Multi-party (network split)

Operator ↔ Studio ↔ Aggregator ↔ Affiliate ↔ Infrastructure providers: shares are distributed according to contribution and quality (see § 5).

2. 3 Hybrid

RevShare + CPA/CPL/minimum warranty; adjusted for quality factors and penalties.

2. 4 Dynamic

Rates and multiples vary by trigger (rush hour, region, play/liquidity pool, risk profiles).

3) What counts as income: Net Revenue canon

[
\text{NetRev} = \text{GGR} - \text{BonusCost} - \text{Jackpot/Pool Share} - \text{Payment Fees} - \text{Chargebacks} - \text{Tax/Levy} - \text{Fraud Losses}
]

GGR: Gross Gaming/Betting Revenue.
BonusCost: actual value of bonuses/FS/cashback.
Payment Fees/Chargebacks: APM/PSP fees and returns.
Tax/Levy: jurisdictional taxes/deductions.
Fraud Losses: confirmed fraud losses (per procedure).

4) Attribution and windows (who "brought" income)

Rule: last optional touch with windows by jurisdiction and event type (click/register/FTD).
Cross-device stitching: only for agreed tokens without raw PD.
Multi-hop contribution: if the player's path includes mediuses/chains, weight distribution is applied (see § 5. 2).
Dedup/idempotency: 'eventId' + postback signature, window ± 5 minutes, cursor history replication.

5) Quality and Fairness: Odds and Weights

5. 1 Quality (Q)

[
Q_i = w_{sli}\cdot SLI_i + w_{rg}\cdot RG_i + w_{attr}\cdot ATTR_i + w_{sec}\cdot SEC_i
]

SLI/SLO: uptime, p95 API/webhooks, bus lag.
RG: No red triggers/penalties.
ATTR: accuracy and timeliness of postbacks/tracking.
SEC/COMP: No leaks/sanctioned fouls.

Weights (w _) are rationed to 1 and approved by the ecosystem council.

5. 2 Network split (contribution to × quality)

[
share_i=\frac{CT_i\cdot Q_i}{\sum_j CT_j\cdot Q_j}
]

where (CT_i) is the contribution (rake/traffic/pool contributions, operating costs), (Q_i) is the quality factor.

5. 3 Payout

[
payout_i = share_i \times NetRev \times rate_i \times Adj_i
]

'rate _ i '- RevShare rate (fix/range/dynamics).
'Adj _ i '- adjustments (credits/penalties for SLO, RG penalties, recalculations).

6) Data contracts, oracles and provability

Data Contracts: event/metric diagrams, windows, owners, freshness SLA.
Oracles: signed summaries (GGR, bonuses, chargebacks, taxes) with 'traceId' and versioned formulas.
Reconciliation: cursor uploads, reconciliation of aggregates and hashes, discrepancy acts.
WORM audit: unchanging formula/rate/rule change logs.

7) Rights, access and privacy

Zero Trust: mTLS/JWS, short-lived tokens, egress-allow-list.
PII minimization: tokens instead of PDs; detoxification - only in safe zones.
RBAC/ABAC/ReBAC: access to aggregates and own window tabs; SoD (look ≠ change rates ≠ admin keys).
Jurisdictions: localization of data/money, DPA/DPIA, prohibition of cross-border export of personal data.

8) Sanctions, stop buttons and exceptions

SLO-Malus/Bonus - Automatically adjusts payout for deviations from target SLOs.
RG/sanctions: RevShare instant pause and revenue hold to RCA.
Break-glass: emergency access with mandatory audit.
Justified Exceptions: with TTL, Owner and Autofit only.

9) Cache Economics and Forecasting

Plan-actual: monthly NetRev, splits, seasonality, FX.
Cost-to-Serve: per rps/txn/event/stream; the cost of inference and clearing.
Uplift analysis: contribution of A/B/routing paths to NetRev.
Reserves/holds: under fraud/chargebacks/bonus abuse; NET7/14/30 policy.

10) Shop windows and scorecards

Partner panel: NetRev, splits, quality (SLI/ATTR/RG), status of disputes, payment forecast, acts.
Ecosystem panel: NetRev distribution map by chain/game/jurisdiction, credits/penalties, incident MTTR.
SLO showcases: freshness ≤ 1-5 s (operating panels), p95 render ≤ 1. 5–2. 0 s, uptime ≥ 99. 9%.

11) Processes: invoicing and reconciliation

1. Cutoff period (UTC, clear window).
2. Summaries/oracles: signed NetRev/contribution/sanction aggregates.
3. Reconciliation: cursor tapes, discrepancies, reconciliation protocol.
4. Invoices/acts: automatic generation, portal status, FX course.
5. Payout: NET conditions, holds/klau-backs.
6. RCA "no fault": on controversial cases and SLO incidents.

12) Incidents and war-room

P1: money/PII/mass degradation - stop RevShare payments, canary rollback of rates/rules.
P2: local discrepancies - local cooling of splits, accelerated reconciliation.
SLA per trace package: 60-90 s; closing criterion - agreed summaries.

13) Anti-patterns

"Many truths" NetRev: different formulas/windows → disputes and payment locks.
Postback Zoo: unsigned/different schemes → takes/passes.
Offset pagination of history under load → holes/doubles (use cursors).
SLO "on paper": no alerts, auto-malus/bonus and stop buttons.
PII in shop windows and unloading: leaks, fines.
Single SPOF gateway for redirects/invoicing without N + 1/DR.
Unlimited betting hybrids: Toxic economics and unpredictable cash flow.

14) Checklists

Design

• NetRev/GGR canon and formula owners (versions, windows, sources).
• Attribution rule, windows, dedup and webhook signatures.
• Split model: CT × Q, rates/ranges, sanctions/bonuses.
• Oracles/summaries, Metric Store, WORM audit.
• RBAC/ABAC/ReBAC, SoD, Zero Trust, tokenization.
• Change-calendar, stop-buttons, war-room.

Start

• Sandbox and conformance tests (API/EDA/webhooks).
• Canary bets/limits, auto-rollback.
• Dashboards/scorecards, SLO alerts, SLAs per trace package.

Operation

• Weekly reconciliation, discrepancy reports.
• Quarterly Rate/Multiple Reviews.
• RCA incidents and guardrails update.

15) Maturity Roadmap

v1 (Foundation): NetRev base formula, two-sided splits, signed postbacks, manual reconciliation.
v2 (Integration): CT × Q network splits, oracles and cursor uploads, auto-malus/SLO bonus, showcases and scorecards.
v3 (Automation): dynamic rates for predictive SLI/RG/attr signals, auto-cut-over revenue routes, smart-reconciliation.
v4 (Networked Governance): interconnect pools and federated splits, DAO rules of rates and transparent treasuries (on/off-chain).

16) Success metrics

Business: NetRev/ARPU/LTV growth, predictable cache share, CAC/payback decline.
Quality: accuracy/timeliness of postbacks, disputability <X%, share of SLO incidents.
Technique: p95 API/webhooks, bus lag, trace coverage, MTTR incidents.
Compliance/RG: PD incidents = 0, jurisdictional compliance, RG triggers/1k active.
Economy: Cost-to-Serve per rps/txn/event, credits/penalties,% auto-reconciliation.
Partnership: the share of partners with scorecard ≥ the threshold, the time to provide a trace package.

Brief Summary

Revenue Sharing on the network is not a "percentage of the box office," but a provable system: a single NetRev canon, honest attribution, × quality contribution formula, oracles and reconciliation, strict privacy and SLO gardrails. Pin rules as code, show splits in storefronts, automate bonus/malus and invoicing - and RevShare will be an accelerator of growth and trust throughout the ecosystem.