TL;DR: Multi-accounting is defined by linked identity and behavioral signals across accounts, according to Sift. Fraud teams need cluster-level detection and lifecycle scoring or they will keep missing rings that reuse devices, payment methods, IP ranges, addresses, and behavior.
Editorial analysis by NHI Mgmt Group, based on content published by Sift: “How to Detect Fake Accounts and Multi-Accounting”.
Key questions
Q: Why does multi-accounting create so much risk in marketplaces?
A: Marketplaces reward new accounts through bonuses, referrals, discounts, and listing access, so fraud rings can replay the same playbook repeatedly.
A: They know controls are working when verification outcomes, fraud loss rates, and escalation patterns stay stable after normalising for market risk.
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.
Practitioner guidance
- Implement graph-based account linkage Correlate device, payment, network, and behavioural attributes so analysts can see rings, not just separate accounts.
- Apply dynamic friction at high-risk events Trigger step-up checks at first login, first listing, first payout request, and password reset instead of relying on signup-only controls.
- Review payout and payment reuse Treat reused cards, wallets, payout addresses, and billing overlaps as stronger ring indicators than name or email variation.
Bottom line: Multi-accounting is not best understood as a bad account problem, but as a coordinated relationship problem across linked identities.
Glossary terms: Multi-accounting, Link Analysis, Dynamic Friction, Device Fingerprinting Accuracy
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Multi-accounting is a relationship problem, not a record problem. Trust and Safety teams lose coverage when they treat identity as a per-account object instead of a network of linked signals. The practical boundary shifts to shared device, payment, and behavioural evidence, which means the governing question is whether the programme can see clusters rather than rows. Practitioners should design fraud controls around connected identity, not isolated account review.
A question worth separating out:
Q: What should teams do after a suspicious account is linked to a wider cluster?
A: Escalate the whole linked cluster for review, then apply proportional friction based on risk level. Evidence should travel with the case so analysts can see the shared device, payment, and behavioural signals immediately. That prevents repeated manual work and reduces the chance that one blocked account simply spawns the next one.
👉 Read our full editorial: Multi-accounting detection depends on linked identity signals, not single accounts