See the gambling your transaction filters can’t
The detection layer for young-account-holder gambling — surfacing the sweepstakes, prediction-market, skin, and P2P rails that MCC filtering misses, so your teams can finally see them.
What MCC filtering can’t catch
UK banks block gambling at MCC 7995 from inside the auth flow. The US gray market doesn’t carry that code. Four rails it hides in:
See the exposure, not just the merchant code.
- Labeled registry of gambling and gray-market entities with their payment signatures
- Detection that survives obfuscated descriptors and P2P routing
- A per-account exposure read your risk team can act on
Controls your product team can ship.
- Embedded gambling controls with the engine invisible underneath
- Policy set per customer, never different facts — one canonical registry
- The account holder always controls enrollment
One registry, 51 jurisdictions, kept current.
- Entities scored on three orthogonal axes — confidence, severity, and legal status
- Classifications are factual, never accusatory
- Statute alerts as legal status changes by jurisdiction
The flows that look like everything else
Sweepstakes, prediction markets, skin marketplaces, and P2P settlement move through the same rails as ordinary spend. The engine surfaces them — across 51 jurisdictions.
Built for how banks evaluate vendors
De-identified by default
The exposure audit runs on a de-identified sample. No PII required to show you what's there.
Model-risk ready
Methodology documentation, descriptor provenance, and a dispute process, structured for SR 11-7-style review.
SOC 2 on the pilot path
SOC 2 Type II, DPAs, and pen testing sequenced with your pilot.
Why risk and product teams take the audit
“It’s free and de-identified.”
Every risk team says yes to a read on data they already hold.
“It shows what we’re already missing.”
The result is the pitch: exposure your current filters score as clean.
“The user stays in control.”
Consumer enrollment is always opt-in; institutions buy the detection, not surveillance.
See what your filters are scoring as clean
Run the exposure audit on a de-identified sample of data you already hold. No integration required to start.
- Runs on a de-identified sample of data you already hold
- No integration required to start
- Opt-in by design — the account holder stays in control