TL;DR: FATF’s updated gambling and gaming typologies include 123 red-flag indicators across 80 jurisdictions and show how e-wallets, virtual assets, VPNs and sham merchants move risk from the casino floor into banking and payments operations, according to SEON. The key issue is not only customer onboarding, but joining device, payment, platform and account data fast enough to see laundering patterns that each stack misses alone.
Editorial analysis by NHI Mgmt Group, based on content published by SEON: “FATF Published a Gambling Risk List, and Part of It Belongs to Banks”.
Key questions
Q: What breaks when gambling laundering detection relies only on KYC checks?
A: Onboarding can confirm who a customer claims to be, but it cannot reveal whether deposits, devices, withdrawals and platform activity line up as a laundering pattern.
Q: Why do shared devices and payment instruments increase laundering risk in gaming channels?
A: They create a relationship signal that individual transactions conceal.
Q: What are the signs that sham merchant activity is being missed in acquiring?
A: Look for domestic retail presentation paired with unusual cross-border value flows, implausible service contracts, rapid beneficial ownership changes or merchant behavior that looks operationally legitimate but economically inconsistent.
Practitioner guidance
- Build cross-stack entity resolution Link device, IP, email, phone and payment instrument so that one person holding several accounts resolves to a single risk entity across fraud, payments and AML workflows.
- Monitor deposit-to-wager ratios Instrument alerts for money that arrives and leaves with minimal play, because FATF treats deposit, wager and withdrawal sequencing as a plain laundering pattern.
- Reassess merchant categorization Review merchant categories, geographies and business descriptions where gambling adjacency is plausible, especially where domestic retail presentation may conceal illicit gaming traffic.
Bottom line: The article shows that gambling laundering is increasingly detected through cross-system relationships, not isolated onboarding checks.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →