Identity Graph
One user.
Many faces.
One truth.
Fraud rings hide behind fake accounts, VPNs, and device spoofing. Identity Graph links every session, device, and payment method across your entire platform — exposing who’s really behind the transaction.
847
Fraud rings mapped on avg. audit
48h
To map your entire network
16K
Linked accounts exposed
Account
Device
IP address
Email
⚠ Flagged
Linked
Fraud link
Rings detected
847
Fraud rings mapped per avg. enterprise audit
Accounts exposed
16K
Linked accounts identified and frozen in 48h
Revenue protected
€2.3M
Avg. multi-account abuse blocked in first month
Detection time
48h
From data upload to full fraud network map
Based on avg. results from enterprise deployments across iGaming, Crypto, and Fintech in the EU.
How it works
Observe. Link. Expose.
01 · Observe
Collect every signal
Every session emits signals — IP, device fingerprint, browser, payment method, email, phone. Identity Graph captures all of them passively, with negligible impact on UX or latency.
200+ signals per session captured
02 · Link
Connect across accounts
Graph algorithms link accounts that share any signal — same device across different emails, same IP across different payment cards, same browser fingerprint across different names.
Cross-session entity resolution in real time
03 · Expose
Surface the ring
Clusters of connected accounts are scored and ranked by risk. A single bad actor touching 3 accounts exposes all 3 — even if each individual account looks clean on its own.
Cluster risk propagates to all linked nodes
Use cases
Every vertical has a
multi-account problem.
iGaming · High severity
Bonus abuse rings
Players create dozens of accounts to claim welcome bonuses repeatedly. Identity Graph maps the shared device and IP fingerprints, freezing all linked accounts the moment one abuses a promotion.
shared_deviceip_clusteremail_patternpromo_velocity
Crypto · High severity
Wallet clustering
Wash trading and layering hides behind multiple wallets and KYC identities. Identity Graph links wallets sharing session fingerprints, connecting the same physical person across synthetic KYC identities.
wallet_linksession_fingerprintkyc_similaritytx_pattern
Fintech · Medium severity
Synthetic identity fraud
Fraudsters combine real and fake personal data to create new identities. Graph links synthetic identities sharing device or behavioral signals back to the originating device cluster.
identity_similaritydevice_reusebehavior_matchdocument_pattern
E-Commerce · Medium severity
Return fraud networks
Coordinated return abuse rings use multiple accounts to exploit return policies at scale. Identity Graph exposes the shared device infrastructure behind seemingly unrelated customer accounts.
return_velocityshared_addressdevice_clusteraccount_age
Interactive demo
Look up any entity.
See who it’s connected to.
Enter an email, IP address, or device ID to see a live identity graph built around that entity.
Entity lookupLive engine
Email address
IP address (optional)
Device ID (optional)
Identity graph— awaiting lookup
Enter an entity above to build the identity graph and see all connected accounts.
Developer first
Query the graph.
Get the full picture.
A single query returns the full entity graph — every linked account, shared signal, cluster risk score, and recommended action. Real time.
- Cross-session linking across all payment methods
- Cluster risk propagation to all linked nodes
- Works alongside Risk Scoring — one integration
- GDPR-compliant graph storage, EU data residency
// Query identity graph for any entity const graph = await serixo.identityGraph({ email: "[email protected]", ip: "82.193.104.22", device_id: "fp_8f3ka92b", depth: 2, // hop depth });
entity_id: "ent_4f8a1c9d"
linked_accounts: 14
cluster_id: "cls_bonus_ring_447"
cluster_risk: 0.94
shared_signals: ["device_fp", "ip_subnet"]
action: "freeze_cluster"
Security & compliance
SOC 2 Type II
PCI DSS L1
GDPR
ISO 27001
99.95% uptime SLA · EU data residency
See your own
fraud network mapped.
Send us 3 months of transaction data. We map every fraud ring, linked account cluster, and revenue leak — in 48 hours, before you write a line of code.
No credit card · Results in 48 hours · Zero integration required
847
48h
16K