Find the one person behind fifty "new" accounts
Multi-accounting is the engine behind most bonus abuse. Kixo9 maps the hidden links between accounts that look unrelated on the surface.
Why this is harder than it sounds
Blocking obvious duplicates is easy. Catching the accounts that were built specifically to not look like duplicates is the actual problem.
Anyone running more than a handful of accounts on purpose already knows the basics: use a different email provider for each one, vary the name slightly, don't sign up from the same IP twice in a row. None of that is hard to do, and none of it fools a system that's only checking one signal at a time. What's harder to vary consistently, across every account, every time, is the full combination — the device fingerprint underneath the browser, the payout method that eventually has to be real to receive money, the timing pattern of how accounts get created and used, and the referral relationships between them.
That's the gap Kixo9 is built for: not catching the lazy duplicate that any basic rule would already block, but surfacing the account clusters that were specifically built to survive a rule-based check.
How accounts get linked
Fraudsters vary names, emails and even devices — but rarely every signal at once.
Device fingerprint reuse
The same physical device or browser fingerprint behind accounts registered under different identities.
Network clustering
Accounts sharing an IP range, VPN exit node, or connection pattern inconsistent with unrelated players.
Payout convergence
Separate accounts that all eventually route winnings or bonuses to the same payment destination.
What you get
Account graph view
A visual map of linked accounts and the specific signals connecting them, so your team can verify before acting rather than trusting a bare risk number.
Real-time signup screening
New signups are checked against the existing account graph before they're approved, not reconciled against it days or weeks later.
Configurable action rules
Auto-hold, auto-reject, or flag for manual review based on your own risk appetite — a platform in growth mode may set a looser threshold than one focused on tightening losses.
Ongoing graph updates
The account graph isn't a one-time snapshot. It updates as new signups and claims come in, so a cluster that starts small and grows over weeks still gets caught.
A worked example
Picture four accounts created over three weeks on a skill-gaming platform, each with a different name, a different free email address, and a different self-reported location. Individually, none of them would trip a simple duplicate check. But all four were opened from the same device fingerprint, all four claimed the platform's entry-fee credit within their first session, and all four eventually withdrew winnings to the same digital wallet. That combination — one device, one payout destination, a repeated claim-then-withdraw pattern — is what Kixo9's account graph surfaces as a single cluster, with each connecting signal shown, so a reviewer can look at the evidence and decide in seconds rather than trying to spot the pattern across four separate account records by hand.
None of those four signals alone would have been enough to act on — plenty of legitimate reasons exist for two accounts to share a device, or for a withdrawal to land in a common wallet provider. It's the combination, repeated consistently across all four accounts, that turns a set of coincidences into a pattern worth reviewing.
Frequently asked
What if two real people share a household device?
Kixo9 weighs device signals alongside dozens of others — a single shared signal rarely triggers a block on its own; the score reflects the full pattern.
Can we review flagged clusters before acting?
Yes — the account graph view is designed for your fraud team to verify a cluster before any account is actioned, if you choose manual review mode.
Does this catch multi-accounting used for self-exclusion evasion?
The same account-linkage signals that surface bonus-abuse clusters often surface a player circumventing their own self-exclusion under a new identity, which many platforms treat as a separate, higher-priority alert.
How far back does the account graph look?
By default Kixo9 builds the graph from your full account history at integration, then keeps it current as new activity comes in — so older dormant clusters aren't missed just because they predate go-live.
See your account graph
We'll run a sample of your signup data and show you the clusters hiding in it.