TL;DR: Multi-accounting fraud on marketplaces and iGaming platforms evades rules-based detection by using multiple identities, device farms, residential proxies, and behavioral reuse to claim bonuses, bypass enforcement, and manipulate platform economics, according to Sift. Network-level analysis is now the practical divide between suppressing abuse and repeatedly paying for it.
NHIMG editorial — based on content published by Sift: Multi-accounting fraud in marketplaces and iGaming
Questions worth separating out
Q: What breaks when multi-accounting fraud is evaluated one account at a time?
A: Single-account evaluation misses the relationship pattern that defines multi-accounting.
Q: Why do multi-accounting rings bypass many registration controls?
A: They exploit the fact that registration controls often verify attributes rather than relationships.
Q: How do teams know if multi-accounting detection is actually working?
A: Look for fewer successful bonus claims from newly created clusters, faster linking of suspicious accounts, and higher investigator confidence in clustered cases.
Practitioner guidance
- Correlate accounts into identity clusters Link registrations by device fingerprint, payment metadata, subnet history, and behavioural cadence so the fraud team investigates clusters instead of isolated accounts.
- Use graph-based review queues Prioritise clusters with shared infrastructure or repeated behavioural edges, then route them into investigation workflows that can explain why the accounts are connected.
- Add behavioural reuse signals to enforcement logic Track typing cadence, navigation sequence, and first-session flow similarity so repeated operator behaviour is visible even when identifiers change.
What's in the full article
Sift's full article covers the operational detail this post intentionally leaves for the source:
- How Sift models thousands of signals across registration, login, and transaction journeys
- How dynamic friction is applied selectively to high-risk registrations and sessions
- How workflow rules can be tuned without engineering involvement as fraud patterns change
- How cross-platform network intelligence helps flag known abuse infrastructure
👉 Read Sift's analysis of multi-accounting fraud in marketplaces and iGaming →
Multi-accounting fraud: why network signals beat single-account rules?
Explore further
Multi-accounting is a trust graph problem, not a registration problem. The article shows that the decisive evidence emerges only when teams connect devices, payment methods, and behaviour across accounts. That shifts the governance model from single-identity screening to relational identity assurance, which is closer to how coordinated fraud actually operates. Practitioners should design controls around linked identities, not isolated sign-ups.
A question worth separating out:
Q: Who is accountable when multi-accounting bypasses responsible gambling or seller enforcement?
A: Accountability sits with the platform owner because the platform chose the identity and enforcement model. In regulated iGaming, failure to enforce exclusions can create compliance exposure; in marketplaces, weak re-entry controls undermine trust and seller governance. The control gap is usually persistence, not policy wording.
👉 Read our full editorial: Multi-accounting fraud is a network problem, not an account problem