How to read this?

• Focus: iGaming-specialized vs. generalist (needs policy clearance).
• Best for: Where the platform shines.
• Standouts: Notable strengths you’ll feel in day-to-day ops.
• Watch-outs: Common friction or caveats.
• Pricing: Typical posture; expect quotes to vary.

Software	Focus	Best for	Standouts	Watch-outs	Pricing
Scaleo	iGaming-specialized	Casino & sportsbook operators wanting a modern stack and strict anti-fraud	Flexible hybrid commissions, granular API/webhooks, device/IP intelligence, fast UI, multi-brand	Advanced features need deliberate setup; plan the migration	Quote
Income Access (Paysafe)	iGaming-specialized	Regulated markets and legacy programs needing depth + stability	Mature reporting, payment stack pedigree, strong network familiarity	UI feels dated to some teams; custom work adds time	Quote
NetRefer	iGaming-specialized	Established brands with complex deal logic and lots of partners	Robust commission engine, clear audit trails, enterprise controls	Implementation cycles can be longer	Quote
PartnerMatrix (EveryMatrix)	iGaming-specialized	Operators on EveryMatrix or wanting tight sportsbook/casino ties	Native tie-ins to PAM/gaming, solid portal UX, good KYC tools	Best fit when aligned with EveryMatrix ecosystem	Quote
MyAffiliates	iGaming-specialized	Programs needing flexible payouts and many niches	Highly configurable plans, multi-brand management, sane billing	Interface requires onboarding time for new teams	Quote
Cellxpert	iGaming-specialized	Brands prioritizing compliance workflows	Smart compliance gates, practical automation, good partner CRM	Deal setup depth can mean steeper learning curve	Quote
Affilka (SOFTSWISS)	iGaming-specialized	Crypto-friendly casinos and multi-brand setups	Clean portal, quick creative tools, crypto-aware reporting	Works best inside SOFTSWISS stack	Quote
Trackier (Affiliate)	Generalist (iGaming vertical)	Fast rollouts with modern UI and templated flows	Snappy dashboards, sane pricing, solid API	Confirm iGaming policy & GEO acceptance	$–$$
TUNE (HasOffers)	Generalist (network-grade)	Networks and big programs wanting classic control	Battle-tested tracking, granular partner settings	Modern UX varies by module; confirm iGaming use cases	$$–$$$
Affise	Generalist (performance)	Ops that want flexible APIs and BI exports	Good automation, offers marketplace, data pipes	Policy review needed for gambling verticals	$$
Partnerize	Generalist (enterprise)	Big brands with procurement/InfoSec hoops	Governance, workflows, partner discovery	Enterprise cycles; clarify gambling acceptance first	$$$

#	Software	Focus	Best for	Standouts	Watch-outs	Pricing
13	Impact.com	Generalist (enterprise)	Diversified brands mixing affiliates, creators, and media	Contracting, dynamic commissioning, marketplace	Gambling acceptance varies by region—get it in writing	$$$
14	CAKE	Generalist (network)	Networks and large programs needing reliable routing	Solid tracking & caps, fine-grained partner controls	UI is utilitarian; confirm regulated GEO handling	$$–$$$
15	Post Affiliate Pro	Generalist SMB	Smaller brands or side projects	Easy setup, cost-effective	Not built for massive, regulated casino/sports ops	$
16	LinkTrust	Generalist (legacy)	Teams inheriting older setups	Stable tracking, straightforward deal logic	Legacy feel; check roadmap & support SLAs	$$
17	HitPath	Generalist (network)	Network-style operations	Scalable tracking, good offer management	Confirm gambling acceptance and fraud tooling	$$–$$$
18	Refersion	Generalist DTC	Merch-style promos, content partners	Simple portal, ecom-friendly	Often not suited for regulated iGaming; check TOS	$–$$
19	Tapfiliate	Generalist SaaS	Niche/side brands, simple campaigns	Quick launch, clean UI	Feature ceiling for casino/sports at scale	$
20	FirstPromoter	Generalist SaaS	Software-style referral loops	Dead-simple flows, great for trials/referrals	Not intended for casino-grade compliance	$
21	Intelitics	iGaming-leaning	Performance analytics + affiliate/media in one	Strong BI, paid media + affiliate convergence	Pair with core tracking if you need deep deal logic	$$–$$$
22	ReferOn	iGaming-specialized	Newer programs wanting slick portal UX	Clean design, solid day-one features	Newer entrant—validate scale & SLAs	Quote
23	Rightlander	Compliance tool	Operators policing affiliate pages	Brand-bidding/search & content compliance scans	It’s add-on, not tracking—pair with a core platform	$$
24	GiG Comply	Compliance tool	Heavier compliance footprints	Broad scanning rules, regulator-friendly reports	Also an add-on; clarify data retention	$$–$$$

These aren’t affiliate program platforms; they’re the add-ons many casino teams bolt on to protect budgets and measure app installs. They belong in your stack discussion.

#	Software	Role	Why casinos use it	Watch-outs
25	BrandVerity	PPC brand compliance	Catches affiliates hijacking your brand terms	Needs enforcement process to matter
26	The Search Monitor	Search compliance	Monitors PPC/SEO trademark use and geo-specific SERPs	Budget scans to your highest-risk GEOs
27	RedTrack	Ad tracker	Multi-channel attribution beyond affiliate links	Not a partner portal—pairs with core platform
28	Voluum	Ad tracker	Traffic routing, split tests, bot filters	Affiliate-side tool too—align definitions
29	AppsFlyer	Mobile attribution	iOS/Android app install attribution for affiliates	Privacy frameworks can limit signals
30	Kochava / Adjust	Mobile attribution	Alternatives to AppsFlyer with strong fraud tools	Pick one; don’t run overlapping SDKs

Not sure which of the “generalist” platforms permit gambling in your markets? Make policy clearance your first RFP question. Get it in writing by GEO.

---

Quick pick help

• Need a modern iGaming-first platform with fast UI and flexible commissions? Start with Scaleo, PartnerMatrix, MyAffiliates, Cellxpert, or Affilka.
• Running a mixed affiliate + paid media engine? Consider Intelitics layered with Scaleo or Affise.
• Heavy compliance remit? Bolt Rightlander or GiG Comply onto your core stack and enforce findings with contract teeth.
• Mobile app growth focus? Add AppsFlyer/Adjust to your affiliate stack so your app teams and affiliate ops see the same truth.

iGaming Affiliate Software: Top Picks, Comparisons, Playbooks

Top Picks: In-Depth

Scaleo

Best for: Casino/sports operators that want a modern, anti-fraud-forward stack with real-time reporting and flexible hybrid plans.
Setup window: 2–6 weeks (single brand), 6–10 weeks (multi-brand + warehouse feeds).
Strengths: Fast UI, granular API/webhooks, promo-code overrides, device/IP intelligence, clear audit logs, multi-brand controls, sane migration tooling.
Limiters: Advanced rules (weighted attribution, deal simulators) need deliberate design; plan the data model first.
Good to know: Anti-fraud logic inspects IP/ASN/device/browser/OS and cookies; scoring plus blacklists cut junk signups and bonus abuse without manual whack-a-mole.

PartnerMatrix (EveryMatrix)

Best for: Operators already on EveryMatrix PAM or wanting tight sportsbook/casino ties.
Setup window: 6–12 weeks depending on how deep you integrate.
Strengths: Native ties to gaming stack, strong portal UX, region toggles, practical KYC/AML gates.
Limiters: Sweet spot is inside the EM ecosystem; out-of-stack builds may add lift.

MyAffiliates

Best for: Mature programs juggling many brands, regions, and payout recipes.
Setup window: 6–12 weeks.
Strengths: Very flexible commission engine, multi-brand orchestration, thorough billing.
Limiters: Power features mean more knobs; document conventions so new managers don’t get lost.

Cellxpert

Best for: Teams with a compliance-first posture.
Setup window: 4–10 weeks.
Strengths: Clean compliance workflows, good automation, partner CRM touches.
Limiters: Deal setup depth = steeper learning curve for juniors.

Affilka (SOFTSWISS)

Best for: Crypto-aware casinos and multi-brand setups.
Setup window: 3–8 weeks when inside the SWISS stack.
Strengths: Quick portal, creative tools, crypto-friendly reporting.
Limiters: Best fit when you lean into the native ecosystem.

Income Access (Paysafe)

Best for: Regulated footprints and legacy migrations that need stability and finance comfort.
Setup window: 8–16 weeks typical.
Strengths: Deep reporting, payment pedigree, enterprises trust the governance.
Limiters: Interface can feel legacy; custom work elongates timelines.

NetRefer

Best for: Enterprise programs with complex tiers and audit requirements.
Setup window: 8–16 weeks.
Strengths: Strong deal logic, audit trails, strong governance.
Limiters: Longer implementation cycles; plan parallel run carefully.

---

Feature Comparison Matrix (Operator View)

Platform	Hybrid Plans (CPA/Rev/CPL/CPC/Flat)	Promo Code Overrides	Device/IP Fraud Signals	Brand-Bidding Scans	Multi-Brand/Skin	GEO/Compliance Gates	Open API + Webhooks	Data Export Ownership	SLA/Status Page	Hosting Region Control	Affiliate Mass-Pay
Scaleo	✅	✅	✅	Via integrations / rules	✅	✅	✅	✅ nightly dumps	✅	✅	✅
PartnerMatrix	✅	✅	✅	Via integrations	✅	✅	✅	✅	✅	✅	✅
MyAffiliates	✅	✅	✅	Via integrations	✅	✅	✅	✅	✅	✅	✅
Cellxpert	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Affilka	✅	✅	✅	Via integrations	✅	✅	✅	✅	✅	Region options	✅
Income Access	✅	✅	✅	✅	✅	✅	✅	✅	✅	Region options	✅
NetRefer	✅	✅	✅	Via integrations	✅	✅	✅	✅	✅	Region options	✅
Affise	✅	✅	✅	Via integrations	✅	Rules	✅	✅	✅	✅	✅
TUNE	✅	✅	✅	Via integrations	✅	Rules	✅	✅	✅	✅	✅

Tip: “Data Export Ownership” should mean your S3/Blob bucket, nightly, with schema versioning—not a one-off CSV when you ask nicely.

---

Implementation Playbooks

Small Brand (1–2 markets, 1–2 affiliate managers)

Goal: Go live fast, avoid technical debt.
Timeline (6–8 weeks):

1. Week 1–2: Choose platform, define attribution rules, finalize NGR formula, set CPA qualifications.
2. Week 3–4: Configure offers, creatives, deep-link/promo code rules. Spin up API keys and warehouse exports.
3. Week 5: Parallel-tag pilot partners (5–10) and run a dual-tag accuracy check.
4. Week 6–8: Train team, open applications, soft launch, close first payout cycle.

Staffing: 1 AM, 1 analyst (part-time), 1 dev for tags/webhooks.
Must-have: Deal simulator to avoid margin surprises when you tweak tiers.

Mid-Size (multi-brand, 4–6 markets)

Timeline (8–12 weeks):

• Add compliance scans (brand-bidding, RG copy), build data warehouse connectors, codify anomaly alerts (CTR spikes, zero-FTD traffic).
• Create migration runbook with ≤3% KPI variance target during parallel run.

Staffing: 2–3 AMs, compliance lead, BI engineer, marketing ops.

Enterprise (regulated states/countries)

Timeline (12–20+ weeks):

• Formal RFP, InfoSec review, pen test, SOC/ISO attestation, DPA/BAA, DR exercises.
• Build GEO rules for ad disclosures, age gates, and promo legality.
• Integrate mass pay with dual-control approvals and tax form workflow.
• Run 2–4 weeks of parallel tagging with daily variance reconciliation and a signed “go/no-go” criterion.

Staffing: Program director, finance controller, legal/compliance, 2–3 engineers, BI team, 3–6 AMs.

---

Pitfalls & Fixes

Attribution fights with influencers

• Symptom: “My code sent the sale; last click stole it.”
• Fix: Contract states promo code overrides last click; system enforces override with idempotent event keys.

Brand-bidding leakage

• Symptom: Rising CPAs from partners “magically converting.”
• Fix: Activate brand-term monitors, auto-flag violating placements, claw back month’s commission per contract.

Data warehouse drift

• Symptom: Finance vs. affiliate dashboard NGR don’t match.
• Fix: Treat cost components as a configurable table (bonus, processing, jackpot, fraud). Version it; don’t bury math in free-text.

Payout bottlenecks

• Symptom: End-of-month support avalanche.
• Fix: Batch approvals, calendar cut-offs, visible ETA banners in the portal, and strict KYC gating before first payout.

Migration variance >3%

• Symptom: Click/FTD counts off in parallel run.
• Fix: Normalize time zones and currency, ensure SubID parity, and check adblock-safe click endpoints (SSL, CNAME).

Regulated GEO missteps

• Symptom: State warning about missing RG disclaimer.
• Fix: Compliance scans + GEO templating for banners; refuse creatives that lack mandatory copy.

---

KPI Recipes That Predict Trouble

• DAT/K (Daily Active Traders per 1k tickets) < 6 for three weeks → churn wave in ~60 days. Trigger new micro-markets + retention offers.
• Signup→FTD drops > 30% week-over-week by partner → incentive/fraud audit; pause CPA.
• NGR/FTD downtrend with stable wagering → bonus abuse; reduce overlapping promos, deploy wagering contribution rules.

---

CPA vs. Rev-Share: When to Use What

CPA

• Use for top-funnel partners (review sites, streamers) where you can define tight qualification windows (KYC + min deposit + no chargeback).
• Cap CPA to LTV models; include clawback for fraud/SE/chargebacks.

Rev-Share

• Use for mid/low-funnel partners who nurture VIPs; align on negative carryover policy.
• Consider hybrid for high-intent placements (small CPA + fair rev-share), then review quarterly.

Rule of thumb: New GEO = CPA/hybrid to buy volume signal; mature GEO = rev-share to align on LTV.

---

Templates You’ll Actually Use

Promo Code Policy (excerpt)
“Promotional codes uniquely identify affiliate placements. Where a valid promo code and a trackable last-click are both present within the attribution window, promo code takes precedence. Abuse, resale, or public posting of private codes voids commission for the period.”

Brand-Bidding Clause (excerpt)
“Affiliates may not bid on trademarks, misspellings, or brand + coupon terms. Violations forfeit commissions for the period and may result in removal. Operator reserves audit rights over traffic sources.”

NGR Formula (make it explicit)
NGR = GGR – (bonus costs + jackpot contrib + provider fees + payment fees + fraud/chargebacks)

Put that exact line in the IO. No ambiguity, no forum wars.

---

Post-Go-Live: 30-Day Checklist

• Day 3: First payouts test (small cohort), confirm rails and invoices.
• Day 7: CTR and Signup→FTD anomaly scan; purge underperforming creatives.
• Day 14: Tier review; adjust caps and floors; publish changes in portal feed.
• Day 21: Fraud score recalibration; merge new device/ASN lists.
• Day 30: Executive read-out—CPA efficiency, NGR/FTD, brand-bidding incidents, roadmap for Q+1.

---

One Last Question

If your affiliate portal went dark for four hours on a Saturday, would your alerts, exports, and payout clocks still keep trust intact—or would Reddit learn about it first? Design for that day.

Want a zero-BS readiness scan? Use NOWG’s free online tools for casinos to score your current stack—attribution rules, fraud gates, payout ops, and migration risk—in minutes.

---

Buyer’s Guide: Deep Dive (2026 & AI Ready)

Tracking & Attribution

• First click / Last click. Simple, but slants payouts. Last click rewards coupon/retargeting partners; first click favors content/SEO.
• Time-decay. Early touches get paid, but credit shifts toward the close. Good middle ground for mixed funnels.
• Position-based (40/20/40). Splits between first and last with a tip to the middle. Useful for comparison sites + streamers.
• Rules by vertical/GEO. Sports vs. casino behave differently; regulated states may force last-touch on app installs.

Cross-device identity

• Deterministic. Logged-in user IDs, hashed emails, loyalty IDs. Cleanest merges.
• Probabilistic. Fingerprints (IP + UA + screen), lower certainty; use for hints, not payouts.
• Best practice. Pay on deterministic matches; display probabilistic assists as “assist credit” without cash impact.

Links, codes, and postbacks

• S2S postbacks. Non-negotiable for conversions, deposits, and qualified events (FTD, wagering thresholds). Require idempotency keys so duplicates don’t double-pay.
• Deep links & smartlinks. Auto-route traffic to localized bonus pages, app store, or KYC-light landing. Test with UTM/SubID parity.
• Promo/vanity codes. Mandatory for streamers and short-form. Code ownership must override last click to prevent hijacking.

Qualification logic

• CPA windows. e.g., “FTD ≥ $20 in 30 days.” Put it in code, not email.
• Rev-share throttles. Exclude bonus funds, only count NGR after cost of goods (bonus, jackpot, processing).
• Clawbacks. Fraud, chargebacks, self-exclusions—define lookback window (e.g., 90 days) and reporting obligations.

Operator checklist

• Demand: clickid, sub1–sub5, creative_id, landing_id, promo_code, gclid/fbclid capture.
• Webhooks for: signup, KYC pass/fail, FTD, deposit, qualified CPA, wagered X, net revenue, chargeback, ban/self-exclude.
• Export: nightly S3 dump (CSV/Parquet) with schema versioning.

Red flags: No S2S postbacks; promo codes not overriding last click; no SubID granularity; opaque revenue formulas.

---

Fraud & Compliance

Common abuse patterns

• Brand bidding. Affiliates buy your exact trademark. Solution: search monitoring, auto-penalties, and zero-pay clauses.
• Cookie stuffing / toolbars. Inject tags on unrelated sites. Solution: server-side validation, signed links, strict last-touch windows.
• Incent abuse. Cashbacks for signups; high click→signup with zero FTDs. Solution: cohort-based CPA rules, promo blacklists.
• KYC evasion / multi-accounting. Same device + payment rails across “unique” users. Solution: device graphs, velocity rules, BIN/device blacklists.

Controls to require

• Device fingerprint + IP/ASN risk. Flag datacenter IPs, known proxies, velocity spikes.
• Velocity & threshold rules. e.g., “>3 signups per device/day” or “FTD within 60s of signup.”
• Creative compliance scans. Auto-crawl affiliate pages for restricted phrases, missing RG disclaimers, or illegal GEO claims.
• Age/GEO gating. Show country/state-specific disclosures and auto-block restricted traffic.

Policy teeth (sample clauses)

• Brand terms. “No bidding on [brand + variants]; violation forfeits month’s commission and triggers program removal.”
• Sub-affiliate liability. “Primary affiliate responsible for all subs’ compliance; same clawback rules apply.”
• Audit rights. “Operator may audit traffic sources and suspend payouts pending review.”

Red flags: No device/ASN risk, manual-only reviews, compliance “by best effort,” no audit logs, no automated brand-bidding detection.

---

Payments & Billing

Commission math

• CPA. Pay on qualified events (KYC+FTD thresholds). Always define currency, FX rate source, and round rules.
• Rev-share. Net Gaming Revenue = GGR – (bonus + jackpot contributions + payment fees + fraud/chargebacks + provider fees). Write the formula into the contract.
• Hybrid. CPA + Rev-share by cohort; cap CPA to avoid overpaying on low LTV sources.

Carryover & caps

• Negative carry. Standard in casino; consider no-carry for curated partners to spur growth.
• Tiered deals. Auto-tier based on deposits, NGR, or qualified FTDs. Snapshot the tier monthly to avoid disputes.

Taxes & paperwork

• Collect W-8/W-9/VAT in the portal; block payouts until on file.
• Generate invoices automatically; affiliates should see line-item adjustments (fraud, chargebacks) per period.

Payout rails

• E-wallets / bank transfer / crypto (policy-dependent). Show min/max payout, fees, and cut-off dates.
• Mass pay. Approve batches with multi-factor and dual-control permissions.

Red flags: Manual spreadsheets, unclear NGR formula, no mass-pay, no tax collection, FX surprises.

---

Data & Integrations

API coverage

• Read. Partners, offers, clicks, signups, deposits, wagers, revenue, adjustments, invoices.
• Write. Deals, tiers, caps, creative assets, promo codes, partner status.
• Webhooks. Real-time events (see Tracking section); insist on retries, signatures, and idempotency.

Data export

• Nightly dumps (CSV/Parquet), partitioned by date + brand + GEO.
• Schema versioning with deprecation windows.
• Backfill endpoints for missed days.

BI & warehouse

• Native connectors (BigQuery, Snowflake, Redshift) or iPaaS (Make/Zapier/Mulesoft).
• Attribution tables with chain of touchpoints; keep raw + modeled layers.

DSAR & retention

• GDPR/CCPA support: lookup & purge by user_id/email_hash.
• Retention controls (e.g., 24–36 months for PII; longer for finance in hashed form).

Red flags: No export ownership, rate-limited APIs that break ETL, no webhook signatures, no DSAR process.

---

Security & Uptime

Must-haves

• SOC 2 or ISO 27001 (or audit letter in progress).
• 2FA everywhere, SSO/SAML, RBAC with least privilege.
• IP allowlists for admin roles, audit logs for all deal/rate changes.
• Secrets rotation, encrypted at rest/transit, key rotation schedule.

Resilience

• Public status page with historical incidents.
• RTO/RPO targets (e.g., RTO ≤ 1h, RPO ≤ 15m).
• Define maintenance windows in UTC and your core GEO time zones.

DDoS & edge

• WAF + rate limiting on click endpoints; bot shields on signup/FTD events.

Red flags: Shared admin accounts, no audit trails, opaque uptime, “we’ll email if something breaks.”

---

Usability & Ops

Affiliate portal UX

• Self-serve deep-link builder (with locale picker).
• Creative manager (bulk upload, A/B, expiry).
• Coupon/vanity code manager.
• Ticketing & comms (announcements, compliance warnings).
• Tax/KYC center with status progress.
• Localization (UI + numbers + time zones).
• Mobile-friendly (yes, affiliates work on phones too).

Operator console

• Bulk edits (rates, caps, tiers).
• Deal simulator (change CPA/rev-share → margin impact).
• Anomaly alerts (brand-bidding spikes, CTR jumps, zero-FTD traffic).
• Sandbox to test offers without touching prod.
• Role-based views (finance vs. compliance vs. AM team).

Red flags: No deep-link tool, no bulk edits, no anomaly alerts, exports only via UI.

---

KPIs & Alerts (Put These on Your Dashboard)

KPI	Formula	Action Trigger
Click→Signup	signups / clicks	Sudden +/– 50% = creative/compliance audit
Signup→FTD	FTDs / signups	Low = incentive/fraud check, landing test
Qualified CPA rate	qualified CPAs / FTDs	Gap vs. baseline = attribution/rules bug
NGR per FTD	NGR / FTDs	Downtrend = bonus abuse or LTV cliff
Chargeback rate	chargebacks / deposits	>1% monthly = payment/fraud tighten
Brand-bid incidents	violations / month	>0 = enforce penalties

---

RFP Questions (Verbatim)

1. Data ownership: “Confirm nightly full data export (CSV/Parquet) to our bucket; include schema.”
2. Attribution: “Show how you support code-based attribution overriding last click. Include edge cases.”
3. S2S reliability: “Provide webhook retry policy, signature method, and idempotency approach.”
4. Fraud stack: “Describe device fingerprint, ASN risk, velocity, and rules engine. Sample alerts?”
5. Compliance scans: “How do you detect brand-bidding and RG disclaimer failures? Remediation flow?”
6. Rev-share math: “Share your exact NGR formula and configurable cost components.”
7. Payments: “List payout rails, fees, cut-offs, and max batch size. Support dual approval?”
8. Security: “Certifications, last pen test date, RTO/RPO, and key rotation cadence.”
9. Uptime: “SLA %, credits, maintenance windows, and public status URL.”
10. Roadmap & SLA: “Quarterly roadmap access and response/resolve times for P1/P2 incidents.”
11. Migration: “Tools to import historical clicks/FTDs and preserve attribution? Timeline examples.”
12. Limits: “Rate limits for APIs/webhooks and options to raise them during peak events.”

---

Migration Plan (Don’t Skip)

1. Freeze date. Pick a cutover hour; warn affiliates 2–3 weeks ahead.
2. Dual-tag window. Run both trackers for 2–4 weeks; reconcile variances daily.
3. History import. Move partners, offers, deals, creatives, click/FTD IDs.
4. Payment state. Close old-system invoices; open new clean period.
5. Validation. UAT scripts: deep links, codes, S2S events, whole payout cycle.
6. Decommission. Lock old tags; keep read-only for audits.

Success metric: ≤3% variance on key KPIs (clicks, signups, FTDs, qualified CPAs, NGR) during parallel run.

---

Contract Must-Haves

• Data exit clause. “Full exports for 90 days post-termination.”
• SLA credits. e.g., “1 day fee per hour of unscheduled downtime.”
• Change control. “30-day notice for breaking API/schema changes.”
• Brand-bidding penalties. Automatic clawback terms.
• Privacy. DSAR support and breach notification within 72 hours.
• Compliance. Explicit approval to operate in your regulated GEOs.

---

Go-Live Test Pack (Day 0)

• Synthetic flow. Test account → KYC pass → FTD → bet/wager event → withdrawal → clawback.
• Geo tests. Allowed vs. blocked states/countries.
• Promo override. Code beats last click in all cases.
• Load test. Peak event replay (10× traffic) with alerting dashboards visible.
• Finance dry run. Generate invoices, verify NGR line items, FX, and taxes.

If a vendor nails everything above, you’ll spend your time growing the program—not fighting fires. Want me to turn this into a one-page RFP checklist and a parallel-run test script you can hand to vendors?