Crossnorm

Payments & AML rules

Payment and AML rules for 97 jurisdictions, as data

18 parameters per market, from permitted payment methods and payouts to AML thresholds and player-funds protection. Every value carries its status, scope, source and dates, and rules that are about to change are flagged before they apply.

Available· most values verified
See the status of every market, free

Recorded in the product on its real records · AI voice-over · English captions

Transcript

Payment and AML rules for 97 gambling jurisdictions, as data.

18 parameters per market: payment methods, payouts, AML, player funds, taxes, data and player protection.

Every cell says how sure we are: indicative, verified, change pending — or plainly, not covered yet.

Open a cell for the summary, and a market for the full record.

Each value is a typed field — the limit, the period, the scope — with its source and the date it applies from.

Rules that are about to change are flagged before they apply.

Take any record as JSON, straight into your cashier or rule engine.

Put markets side by side, and keep only what differs.

Crossnorm: gambling regulation data, traceable to the source. Request access at crossnorm.com.

What you get

  • 18 parameters as typed fields

    Limits, periods, scopes and lists instead of paragraphs, in 7 launch topics: payment methods, ownership and payouts, AML thresholds and reporting, player funds, taxes at payment, reporting and data, and player protection at payment.

  • A status on every cell

    Regulator-confirmed, verified, indicative, change pending, not found, not applicable or not covered yet: you see how far a value has been checked before you rely on it.

  • Changes flagged before they apply

    A rule with a future effective date reads “change pending”, with the date it applies from. History is kept, so you can show what applied on a given day.

  • Compare, cite, export

    Put two to four jurisdictions side by side and keep only the differences. Copy any record as JSON or as a citation for a client, or read it through API v1 with your organisation's key.

Who uses it

  • PSPs and crypto processors

    Permitted rails, closed loop, CDD thresholds and payment-blocking duties per market, structured for your onboarding rules.

    More for PSPs
  • Operators and platforms

    Cashier rules per market – methods, payout limits, player-funds protection – as fields your systems can read.

    More for operators
  • Law firms and compliance teams

    One sourced answer per market and parameter, with its dates and history for auditors, acquirers and clients.

    More for law firms

Coverage you can check

The module is live, and most values are verified: each names its source and dates, AI-assisted drafts are flagged as such, and “verified” means checked against the official text – by a person, or by an automatic check that finds the quote word for word in a first-tier official source, matches every figure and keeps a copy of the source. Empty cells read “Not covered yet”. Tell us which markets you need first – that is how we decide what to verify next.

Request a market
  • 38 in Europe655 of 684 values filled · 479 verified
  • 22 in Africa248 of 396 values filled · 139 verified
  • 26 in the Americas and Caribbean412 of 468 values filled · 297 verified
  • 11 in Eurasia, the Middle East, Asia and the Pacific162 of 198 values filled · 94 verified
VerifiedCollectedNot covered yetas of 9 Nov 2026

Bring your markets. We'll show you the rules – sourced.

Tell us which jurisdictions and checks matter to you, and we'll open a 14-day trial on your markets, on real data.