For verified iGaming operators
Affiliate Risk Intelligence for iGaming Operators
Structured affiliate intelligence for due diligence, risk assessment and informed commercial decisions.
Relationships
Incidents
Resolved
Incident
EvidenceStatement
Context
Affiliate history rarely travels beyond a single operator
Payment disputes, contract disagreements, chargebacks and traffic quality issues are usually known only to the operator involved. Due diligence on a new affiliate then depends on informal references and screenshots.
Commercial risk
Payment disputes, contract disagreements and claims to return amounts already paid out.
Compliance risk
Advertising and target-market requirements that were agreed or apply by law.
Operational risk
Traffic quality that falls short of the agreement.

The Registry
One place for documented affiliate history
Operators record business relationships and incidents with supporting evidence. Participating operators access the consolidated information through exact lookups.
Affiliate profiles
Identifiers, business relationships and history per affiliate, matched by domain, email address, company name, payout account, wallet or channel name.
Incidents
Payment disputes, contract disputes, chargebacks, traffic quality and compliance topics, each tied to a documented business relationship.
Supporting evidence
Contracts, invoices, platform exports and proof of payment, each stored with a checksum.
Statements
The party concerned can respond without an account. The statement is displayed next to the incident.
Historical records
Entries keep their date, status and resolution state, so history remains traceable over time.
Structured ratings
From Pro, ratings from a fixed question catalog, averaged across independent operator groups.
Due diligence
Review affiliate history before entering a partnership
Use the Registry before commercial onboarding and during ongoing review. Query an exact identifier, state the purpose of the check and review the documented information.
- 1
Verified access
Each operator is verified individually. Lookups are enabled after the first documented contribution.
- 2
Exact lookup
Query one identifier: domain, email address, company name, payout account, wallet, Telegram, Twitch or Kick name, or a profile on YouTube, Instagram, TikTok, X or Linktree. The purpose of each check is recorded.
- 3
Review
See counts and, depending on the plan, published incidents with statements and ratings.
- 4
Integration
Bulk checks and watchlist notifications support ongoing review. API and webhooks (Agency, Enterprise) connect the Registry to existing systems.

Risk intelligence
Risk assessment under your control
The Registry supplies documented information. Your team decides how it feeds into the risk assessment, optionally with custom review logic built on your own rules.
Counts for every lookup
Relationships, published incidents, resolved and disputed cases at a glance.
Your custom review logic
Optional rules, for example on the number of open incidents or the age of the latest one, with a risk status as the result. Off by default, versioned and visible only to your team.
Alerts on change
Watchlist notifications by email, Telegram or inbox when counts or the risk status under your review logic change.

Evidence and incidents
Documented information, structured consistently
Every incident follows the same structure, so entries stay comparable across operators.
- Business relationship
- Incident type and date
- Factual description
- Supporting evidence
- Amount and currency
- Statement of the party concerned
- Resolution status
Evidence and wording are reviewed before an entry becomes visible. Incident types are described on the product page.

Operator intelligence
Information contributed by participating operators
Operators document incidents from their own relationships and, in return, query the consolidated Registry. The Registry connects operators through the information, not through each other.
Contribution first
Lookups are enabled after a first documented contribution.
One source per operator
Several brands of one operator count as one source, so a single operator cannot multiply an entry.
Targeted access
Each lookup covers one identifier and is logged with its purpose.

How the Registry works
Structured affiliate intelligence
Clawback Registry gives operators structured information for affiliate due diligence and risk assessment. Reported incidents, supporting evidence and historical information follow one consistent framework.
Documented information
Reported information and supporting evidence are structured and presented in context.
Operator-controlled decisions
The Registry provides intelligence. Commercial and risk decisions remain with the operator.
Protected sources
Reporting operators are not disclosed within the Registry.
Traceable records
Reports, incidents and relevant activity are recorded with context and timestamps.
Absence of information is not clearance
If no record exists, no corresponding information is currently available in the Registry.
Teams
Built for affiliate, compliance and risk teams
Access is limited to verified iGaming operators and granted by invitation. Each brand is verified individually before it can query or document.
- Affiliate managers and heads of affiliates: due diligence before and during commercial relationships.
- Compliance and risk teams: traceable, documented information for reviews and internal controls.
- Operator groups and senior management: one view across several brands, with roles and access control.
Platform
Platform overview
Product
Lookup, documentation, review and custom review logic.
Product overview →Plans
Four plans, from counts to group view and API access, with fixed prices per plan.
View plans →Compliance
Review process, evidence handling and technical safeguards.
Review and safeguards →About
Positioning, scope and operator of the platform.
About Clawback Registry →Bring affiliate due diligence into one structured workflow
Each operator is verified individually before access is enabled.
Request access