Foundry /Product /Anti-fraud

Caught before
the payout.

Multi-accounting, bonus hunting, stolen cards. The engine links accounts by device, card and behaviour, scores every cluster — and holds the payout while it's still your money.

01 · Clusters

One case. Not five accounts.

Same device, same card, same pattern — separate accounts collapse into one cluster with one risk score. You judge the scheme, not chase its copies.

Linked by evidence. Devices, cards, IPs, wallets and behaviour — every edge in the graph is a fact you can show.
Scored, not guessed. Each trigger adds weight; the score decides — watch, review or hold the payout.
Evidence preserved. The cluster snapshot — links, triggers, timeline — is saved for disputes and chargebacks.
admin.yourbrand.example/risk/cluster/88
RISK / CLUSTER #88PAYOUT HELD
KMALRSPVD4
same device ×3same card ×2same IP ×4
3 accounts · 1 deviceTRIGGERED
new card + VPNTRIGGERED
deposit → bonus → withdraw loopTRIGGERED
RISK SCORE87
payout held · limits applied to cluster · reviewer: anna
Fig. 01 · Risk clustersone case, not five accounts
02 · Rules

You set the paranoia level.

Every rule is a switch with a threshold — tuned per market, because BR fraud doesn't look like ES fraud. VIPs go on allowlists so good money never waits.

Thresholds per market. Presets ship with the engine; you tighten or relax them as your data comes in.
Allowlists for the good ones. Verified VIPs skip holds entirely — risk control that doesn't tax your best players.
Every decision auditable. Who changed the rule, when a hold fired, who released it — all in the audit log.
admin.yourbrand.example/risk/rules
RISK / RULESmarket: BR ▾+ rule
3+ accounts · 1 deviceHOLD PAYOUTS
new card + VPNREVIEW
deposit → bonus → withdraw loopFLAG
self-referral in affiliate trafficNO COMMISSION
VIP allowlistSKIP HOLDS
HOLD AT SCORE80
presets: BR · ES · PT · ROW — edited 2 days ago by you
Fig. 02 · Rule editorswitches, not tickets
03 · Downstream

Flagged once. Cut off everywhere.

A risk flag isn't a note — it's a segment. The moment a cluster is flagged, it stops earning across every module, automatically.

CLUSTER #88FLAGGED
same device ×3same card ×2score 87
flagged today · 14:02 · rule: 3+ accounts / 1 device
Bonuses
EXCLUDED
Campaigns
EXCLUDED
Referral rewards
FROZEN
Affiliate FTDs
NOT BILLABLE

Abuse stops earning the day it's spotted — not at the end of the month when someone reads a report. False positive? One click releases the cluster, and the log remembers both decisions.

04 · Cases

A queue, an owner, a deadline.

Every hold becomes a case with a reviewer and an SLA — so risk control never turns into "payouts stuck for a week and nobody knows why".

Owned, not orphaned. Cases assign to your risk role; VIP cases can escalate to you personally.
SLA on every hold. Legit players get released fast — the queue shows what's about to breach.
Paper trail included. Decision, evidence, reviewer — exportable when a dispute or regulator asks.
admin.yourbrand.example/risk/cases
RISK / CASES · TODAYSLA · 4H
CASEWHATHELDSTATUS
#88multi-account · 3 linked€600ANNA · 1H LEFT
#91chargeback pattern€1,250DIEGO · 3H LEFT
#87false positive · VIP travel€2,400RELEASED ✓ 12M
#84bonus loop · confirmed€380REJECTED · DOCS ✓
THIS MONTH · 46 CASES · 9 CONFIRMED FRAUDAVG DECISION 1H 50M
Fig. 04 · Case queueheld money never sits silent

Keep what you won.

Bring your worst fraud story to the demo — we'll show which rule would have caught it, and when.

Message us on Telegrama human replies · no forms, no waiting