Crossnorm
Request access
Crossnorm

For PSPs, platforms and operators in gambling

Gambling regulation data, traceable to the source

Payment and AML rules for 67 jurisdictions as structured fields, not prose — each value with its source, an original-language quote, the effective date and when it was last checked. Plus ~80 official regulator licence lists and blacklists, loaded daily.

Request accessSee how a value is sourced
  • Plans from €1,000 / year
  • Free for regulators
  • Reference data, not legal advice
Payments & AML rules
Show the record as
PL · PolandPayment methodsIndicative

Payment-blocking lists

PSPs stop payment services for register-listed domains within 30 days

Applies to
payment service providers
Deadline
30 days from entry in the register
List
Ministry of Finance domain register
Scope
Online

Ministry of Finance (gov.pl)(opens the official source in a new tab) · Official · tier 1

dostawcy usług płatniczych zobowiązani są, w terminie 30 dni od dnia dokonania wpisu domeny do Rejestru, do zaprzestania świadczenia usług płatniczych na stronie internetowej wykorzystującej nazwę domeny wpisaną do Rejestru
pl
Show translation

Translation by Crossnorm:payment service providers are obliged, within 30 days of the date a domain is entered in the Register, to stop providing payment services on a website that uses a domain name entered in the Register

Effective
Retrieved
Checked
Not checked yet

1 version · history kept

{
  "id": "val_example_pl_p15",
  "jurisdiction": "PL",
  "topic": "payment_methods",
  "parameter": "payment_blocking",
  "status": "indicative",
  "needs_confirmation": false,
  "summary": "PSPs stop payment services for register-listed domains within 30 days",
  "value": {
    "kind": "blocking_duty",
    "applies_to": "payment_service_providers",
    "list": "pl-mf-domain-register",
    "deadline": {
      "n": 30,
      "unit": "days",
      "from": "register_entry"
    }
  },
  "scope": {
    "channel": "online",
    "products": [],
    "subnational": null
  },
  "effective_from": "2017-07-01",
  "effective_to": null,
  "source": {
    "class": "official",
    "title": "Ministerstwo Finansów — Rejestr domen",
    "url": "https://www.gov.pl/web/finanse/rejestr-domen-sluzacych-do-oferowania-gier-hazardowych-niezgodnie-z-ustawa",
    "lang": "pl",
    "retrieved_at": "2026-10-08T00:00:00Z",
    "quote": "dostawcy usług płatniczych zobowiązani są, w terminie 30 dni od dnia dokonania wpisu domeny do Rejestru, do zaprzestania świadczenia usług płatniczych na stronie internetowej wykorzystującej nazwę domeny wpisaną do Rejestru",
    "quote_status": "verbatim"
  },
  "source_tier": 1,
  "ai_assisted": false,
  "checked_at": null,
  "checked_by": null,
  "stale": false,
  "versions": 1
  …
Fig. 1 — Anatomy of a value: Poland's payment-blocking duty, with its official source and quote.
  1. Value and unit
  2. Scope
  3. Effective date
  4. Source
  5. Original-language quote
  6. Retrieved and checked
  7. Trust status
  8. History

Crossnorm in numbers

jurisdictionsEurope 35 · Africa 12 · Americas & Caribbean 11 · Eurasia, Middle East & Asia 9.
67
payment & AML parametersGrouped into 7 launch topics of a 13-topic framework.
18
official lists, loaded dailyRegulator licence registers and blacklists, each shown with its last-loaded date.
~80
modulesEach labelled available, in beta, preview or coming.
12

Counted from published data · as of

The problem

Payment rules are written as prose. Your systems need values.

Every market writes its payment and AML rules its own way. The rules sit in acts, decrees, guidance notes and regulator lists, often in the local language and spread across several authorities. Teams copy them by hand into spreadsheets, cashier settings and onboarding checklists, and often learn about a change late.

Multiply that by your markets. Across 30 jurisdictions, our 18 parameters add up to 540 values to keep current, before you count a single licence register or blacklist.

  • Prose reports and annual guides describe the law.

    They don't give your cashier a value, a scope and an effective date.

  • Licence registers and blacklists live on dozens of regulator sites.

    Each uses its own format and changes on its own schedule.

  • Auditors and acquirers ask what applied on a given date.

    You need the old value, the new one and the source for both.

How it works: from rule to field to your systems

Five steps, the same for every jurisdiction.

Show step

1 · Fields

Rules as fields, not prose

  • Each jurisdiction has 18 payment and AML parameters. Among them: permitted payment rails, closed-loop and payout routing, CDD thresholds and aggregation windows, report triggers, payout time limits and payment-blocking lists.
  • Every value has a unit, a scope (online or land-based, products, sub-national area) and a one-line summary.
Available
Payments & AML · grid excerptIllustrative · sample data, fictional
Illustrative grid: fictional example markets, invented counts of filled parameters per topic
MarketPaymentsPayoutsAML
XAExample market AVerified4/4Indicative3/4Indicative2/2
XBExample market BIndicative4/4Change pending4/4Indicative1/2
XCExample market CRegulator-confirmed4/4Verified4/4Verified2/2
XDExample market DIndicative2/4Not covered yet0/4Not found0/2
XEExample market ENot applicable—Indicative1/4Not covered yet0/2

2 · Sources & quotes

Every value shows where it came from

  • Each value carries its source, a verbatim quote in the original language, and three dates: effective, retrieved and last checked.
  • A trust status says how far the value has been verified. Most values start as indicative, and we show them that way.
PL · Payment-blocking lists · sourceIndicative

Ministerstwo Finansów — Rejestr domen

Official · tier 1 · pl

dostawcy usług płatniczych zobowiązani są, w terminie 30 dni od dnia dokonania wpisu domeny do Rejestru, do zaprzestania świadczenia usług płatniczych na stronie internetowej wykorzystującej nazwę domeny wpisaną do Rejestru
Effective
1 Jul 2017
Retrieved
8 Oct 2026
Checked
Not checked yet
Regulator-confirmed
The authority reviewed the record on the date shown.
Verified
A person checked the value against a primary source: the regulator, the act or an official copy of the act.
Indicative
Taken from desk research, not yet checked against the primary source.
Change pending
An adopted change will take effect on a known date.
Not found
Not found in public sources as of the date shown.
Not applicable
The rule does not apply in this market.
Empty
Not covered yet. Shown as “Not covered yet”.

3 · History

History is never deleted

  • A change creates a new version with its own effective date, and earlier versions stay.
  • When an auditor, a bank or an acquirer asks what applied on a given date, the as-of view will show any value as it stood then.
Available· history keptComing· history and as-of views, with paid plans (early access)
PL · Payment-blocking lists · historyComing· Early access

  1. Version 1

    Effective

    Retrieved

    PSPs stop payment services for register-listed domains within 30 days

  2. Next version

    Added with its own effective date when the rule changes. Version 1 stays.

1 version · history kept

4 · Alerts

Alerts per parameter

  • Follow a parameter in the markets you care about. An alert says what changed in one line, with the source and the quote:

was X, now Y, effective Z

Coming· early access
Alert e-mailIllustrative · sample data, fictional
From
Crossnorm alerts
To
compliance@demo-operator.example
Subject
Payment-blocking lists · XE — changed

Example market (XE) · Payment methods

was X, now Y, effective Z

Source: Example regulator (XE) · quote in the original language · retrieved and checked dates

You follow this parameter in XE · Demo Operator Ltd

5 · API

Into your systems

  • The same fields in JSON through API v1, described in OpenAPI.
  • Every response carries the disclaimer, the data version and an as-of timestamp.
Coming· early access
See an example response
GET /v1/values
curl "https://api.crossnorm.com/v1/values?jurisdiction=PL&topic=payment_methods" \
  -H "Authorization: Bearer $API_KEY"
{
  "data": [
    {
      "id": "val_example_pl_p15",
      "jurisdiction": "PL",
      "topic": "payment_methods",
      "parameter": "payment_blocking",
      "status": "indicative",
  …

Payment & AML rules for 67 jurisdictions

18 parameters in 7 launch topics of a 13-topic framework. The 67 jurisdictions break down as:

Available· most values indicative

Jurisdictions by region

  • 35 in Europe
  • 12 in Africa
  • 11 in the Americas and Caribbean
  • 9 in Eurasia, the Middle East and Asia

Seven launch topics, 18 parameters

Launch topics and their payment and AML parameters
TopicParameters
Payment methods
  • Permitted rails and instrument types
  • Instrument origin and currency
  • Mandatory hubs and gateways
  • Payment-blocking lists
Ownership & payouts
  • Holder and ownership rules
  • Closed loop and payout routing
  • Payout time limits
  • Withdrawal conditions
AML thresholds & reporting
  • Check thresholds and aggregation windows
  • Report triggers and deadlines
Player funds protection
  • Player-funds protection and coverage
Taxes at payment
  • Taxes at the point of payment
Reporting & data
  • Submission mode and cadence
  • Data vault and integrity
  • Data location
  • Retention
Player protection at payment
  • Cross-operator limits and registers
  • Eligibility screening at payment

The other six topics in the framework:

  • Five guide topics, coming as the Guides module: licensing, GGR tax, advertising, responsible gambling and technical standards.
  • Market status and licensees, taken from official registers (Licences & lists).

Compare jurisdictions side by side

Put two to four jurisdictions next to each other and show only the differences.

Compare · XA, XBIllustrative · sample data, fictional
Only differences
Illustrative: only the parameters that differ between two fictional markets
ParameterXAXB
Payout time limits24 hours72 hours
Closed loop and payout routingRequiredNot required
Permitted rails and instrument typesDebit cards, transfersDebit and credit cards

Coverage, shown honestly

  • For every jurisdiction we show how many of the 18 parameters are filled, how many are verified, and when its official lists were last loaded.
  • 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

Licences & lists

Official licence lists and blacklists, loaded daily

We load ~80 official regulator lists every day, both licence registers and blocking lists, and keep the history of every entry. Each list shows:

  • its official link
  • the number of entries
  • when it was last loaded
  • what changed this week
In beta

“Listed on … since …”: presence history, not a verdict

We record when a domain or a licence appears on an official list and when it leaves. Our wording stays factual:

Listed on ‹list› (‹regulator›) since ‹date›

Not found in ‹register› as of ‹date›

‹Regulator› register is not loaded — not checked

  • The archive only grows forward: for each list it starts on the day we first loaded it.
  • If a source fails, the list keeps its last good copy and shows “last loaded ‹date›”. It is never silently emptied.

When a regulator's reuse terms are unclear

We republish a list only where its terms allow it. Where they are unclear or restrictive, we show counts and single-domain answers, with a link to the official source.

Check a merchant domain

  • Domain check looks up one domain across official lists and licence registers, with the date each one was loaded.
  • It answers with facts, never verdicts.
Preview· shown with sample dataNeed this
Domain checkIllustrative · sample data, fictional
casino-a.examplechecked 8 Oct 2026
  • Listed on Example blocking list (XE) since 12 Sep 2026
  • Not found in Example licence register (XE) as of 8 Oct 2026
  • Example regulator register is not loaded — not checked

My compliance: your licences, domains and markets

A workspace that starts from your own profile. Changes reach you only when they touch it, with the reason and the impact.

Preview· early access

  • Discovery. Enter your domain or company. We search official registers and suggest what is yours, and you confirm each finding.

  • Licence and domain watch. Your licences and domains are checked every day against official registers and lists. Where a register isn't loaded, we say “not checked”.

  • Inbox with reason and impact. Every alert says why you got it: the market, licence or domain it touches. It also says what it means for you: before and after, the date, and the parameters affected.

  • Obligations matrix. Your markets against the 18 payment and AML parameters and your licence status. Each row shows the source, the last change and your review state.

  • Calendar. Effective dates, licence expiry dates, fees and filing deadlines, each with its source.

  • Decision log and monthly report. Acknowledge, assign and close each alert. The log can't be edited. A monthly PDF snapshot carries its as-of date and data version for your auditor.

Until your pilot starts, we show the workspace on a fictional company with sample data, clearly labelled.

Request early access
Workspace · Demo Operator LtdIllustrative · sample data, fictional
Obligations · XE · Payment methodsYour state
  • Permitted rails and instrument typesImplemented
  • Payment-blocking listsNot reviewed
  • Closed loop and payout routingAcknowledged
  • Check thresholds and aggregation windowsNot reviewed
InboxHigh

Example market (XE) · licence.not_found

Licence number EX-0001 was not found in Example licence register (XE) as of 8 Oct 2026

Why you got this
Licence EX-0001 is in your profile
What it means for you
Obligations › XE · Payment methods · Your state: Not reviewed

12 modules, labelled honestly

One platform and one data model. Each module carries its real status.

Available
live data.
In beta
live data, coverage still growing.
Preview
the interface, shown with labelled sample data.
Coming
planned. Tell us with “Need this”.
  • Available

    Payments & AML rules

    18 payment and AML parameters across 67 jurisdictions, as fields with source, quote, dates and history. Most values are indicative today.

  • In beta

    Licences & lists

    Market status, licensees and official blacklists from ~80 regulator lists, loaded daily, with “listed since” history.

  • Preview

    Operators

    Company → brands → domains → licences by market, built from official registers. Links stay “candidate” until a person verifies them.

    Need this: Operators
  • Preview

    Domain check

    One domain against official lists and licence registers: “listed on … since …” or “not found in … as of …”. Facts, never verdicts.

    Need this: Domain check
  • Preview

    Enforcement

    Weekly movement on official blacklists, court-ordered blocks, and regulator decisions against companies.

    Need this: Enforcement
  • Preview

    Regulatory tracker

    Draft rules, consultations and EU TRIS notifications by stage, linked to the parameters they affect.

    Need this: Regulatory tracker
  • In beta

    Legal library

    Acts, regulations and guidance per jurisdiction, with issuer, dates, official links and snapshots.

  • Coming

    Guides

    Licensing, GGR tax, advertising, responsible gambling and technical standards, on the same sourced-value model.

    Need this: Guides
  • Preview

    Compliance calendar

    Effective dates, consultation deadlines and licence expiry dates for your markets, 30 and 90 days ahead, with ICS export.

    Need this: Compliance calendar
  • In beta

    Market data

    Official market statistics such as active accounts and players, each with publisher, period and source. No estimates.

  • Coming

    Ask

    Questions answered only from published Crossnorm records, every claim linked to its source and date. Otherwise: “Not found in our data.”

    Need this: Ask
  • Coming

    Decision API

    A rule-based check of a payment for a merchant in a market: allowed, restricted, blocked or unknown, with reasons.

    Need this: Decision API

Comparison, the change feed, alerts, exports and the API are platform features shared by every module.

Who it's for

Built for PSPs, operators, platforms and law firms — free for regulators

For PSPs and crypto processors: onboard and monitor gambling merchants against official sources

  • Domain & merchant check (Preview). Check a merchant's domain against official lists and licence registers. You get “listed on … since …” or “not found in … as of …”, with the date each list was loaded.
  • Payment rules as fields. Each market's permitted rails, credit and crypto rules, closed loop, CDD thresholds and payment-blocking duties, structured so your onboarding rules can read them. JSON through API v1 is coming, with early access.
  • Blocking lists that apply to payment providers. Official blocking lists with last-loaded dates and weekly movement. Poland's domain register and its 30-day duty for payment providers is one of them.
  • Merchant portfolio (Preview, in My compliance). Your merchants' domains, checked every day against official lists.

Crossnorm reports what official registers and lists show, with the date of each. It is not a card-scheme merchant monitoring programme and does not replace one.

Request access for PSPs
Domain checkIllustrative · sample data, fictional
casino-a.examplechecked 8 Oct 2026
  • Listed on Example blocking list (XE) since 12 Sep 2026
  • Not found in Example licence register (XE) as of 8 Oct 2026
  • Example regulator register is not loaded — not checked

For operators: your licences, domains and obligations in one place

  • My compliance workspace (Preview). Your licences, domains and markets in one profile, filled in from official registers and confirmed by you.
  • Licence and domain monitoring. Daily checks against official registers and lists, worded as facts with dates.
  • Obligations. Your markets against the 18 payment and AML parameters, with the source and your review state for each.
  • Answers for auditors. A decision log and a monthly snapshot, each carrying its as-of date and data version.

All four are part of My compliance, in preview with early access.

Request access for operators
Your licences · Demo Operator LtdIllustrative · sample data, fictional
  • EX-0001 · Example market (XE)Matched
  • EX-0002 · Example market (XE)Not checked — register not loaded

For platforms and white labels: cashier rules per market, as JSON

  • Cashier rules per market. Permitted rails, instrument origin and currency, closed-loop routing and withdrawal conditions, as fields.
  • API v1 with OpenAPI (Coming, early access). The same fields as the site. The key belongs to your organisation, not to a named user.
  • Change events (Coming). Alerts per parameter, then webhooks, so you can update a rule without a release.
  • Operator portfolio (Preview). A profile for each operator you serve.
  • OEM. Embed Crossnorm data in your own product under an OEM agreement, on request.
Get API early access
{
  "id": "val_example_pl_p15",
  "jurisdiction": "PL",
  "topic": "payment_methods",
  "parameter": "payment_blocking",
  "status": "indicative",
  …

For law firms: cite the source, the quote and the date

  • Values you can cite. Every value comes with its source, a verbatim quote in the original language and its dates. Copy it as a citation.
  • Share with clients. Quote a value in client advice with its source attached and a link back to Crossnorm.
  • Legal library (In beta) and Regulatory tracker (Preview). The acts behind each value, and the drafts that may change it.
  • Client portfolios (Preview). A profile and a report for each client.
Request access for law firms
Copy citationPL · Payment-blocking lists

Ministry of Finance (PL), Rejestr domen, retrieved 8 Oct 2026, via Crossnorm, as of 8 Oct 2026

For regulators: free access

  • Free for regulators. We issue access after verifying your authority's e-mail domain.
  • Compare. Set your jurisdiction's payment and AML rules side by side with other markets.
  • See your record and correct it. E-mail the change and its source to hello@crossnorm.com. Once your authority confirms a record, it shows “regulator-confirmed” with the date.
  • Movement on official lists (Enforcement, Preview). Additions and removals across neighbouring markets, week by week.
Request regulator access
Regulator-confirmedFree for regulators

Why Crossnorm

How Crossnorm compares with the formats this category usually comes in.

How Crossnorm compares with the formats this category usually comes in.
Common in this categoryCrossnorm
FormatProse reports and PDFsStructured fields with unit, scope and dates, also in JSON
EvidenceSummaries, sometimes from secondary sourcesSource, original-language quote and dates on every value. “Verified” only against a primary source
FreshnessAnnual guides, weekly snapshotsOfficial lists loaded daily. Each value shows when it was last checked
HistoryCurrent text onlyEvery version kept. As-of view by date (coming)
CoverageA headline jurisdiction countA coverage meter per jurisdiction: parameters filled and verified, gaps marked “Not covered yet”
AlertsTopic feeds you filter by handAlerts per parameter: “was X, now Y, effective Z” (coming)
PlansSeat-based contractsOrganisation plans. The API key belongs to your organisation
PricingOn request, after a demoPublished: plans from €1,000 / year. Free for regulators
ListsLabels and scoresFacts with dates: “listed on … since …”

A general comparison with common formats in this category, not a statement about any specific provider.

API

Into your cashier and risk engine: API v1

The API returns the same fields as the site, in one envelope: value, scope, dates, source, quote and status. Every response, including errors, carries:

  • the disclaimer
  • the data version it was built from
  • an as-of timestamp
  • a link to the data licence
Coming· early access

Designed into v1:

  • Versioning under /v1, an OpenAPI 3.1 description and a public changelog.
  • API keys that belong to your organisation, not to a named user.
  • Documented rate limits: requests over the limit get 429 with Retry-After.
Get API early access
Show
Example response · abridged to one value · early-access API
Request
curl "https://api.crossnorm.com/v1/values?jurisdiction=PL&topic=payment_methods" \
  -H "Authorization: Bearer $API_KEY"
Response · 200 · application/json
{
  "data": [
    {
      "id": "val_example_pl_p15",
      "jurisdiction": "PL",
      "topic": "payment_methods",
      "parameter": "payment_blocking",
      "status": "indicative",
      "needs_confirmation": false,
      "summary": "PSPs stop payment services for register-listed domains within 30 days",
      "value": {
        "kind": "blocking_duty",
        "applies_to": "payment_service_providers",
        "list": "pl-mf-domain-register",
        "deadline": {
          "n": 30,
          "unit": "days",
          "from": "register_entry"
        }
      },
      "scope": {
        "channel": "online",
        "products": [],
        "subnational": null
      },
      "effective_from": "2017-07-01",
      "effective_to": null,
      "source": {
        "class": "official",
        "title": "Ministerstwo Finansów — Rejestr domen",
        "url": "https://www.gov.pl/web/finanse/rejestr-domen-sluzacych-do-oferowania-gier-hazardowych-niezgodnie-z-ustawa",
        "lang": "pl",
        "retrieved_at": "2026-10-08T00:00:00Z",
        "quote": "dostawcy usług płatniczych zobowiązani są, w terminie 30 dni od dnia dokonania wpisu domeny do Rejestru, do zaprzestania świadczenia usług płatniczych na stronie internetowej wykorzystującej nazwę domeny wpisaną do Rejestru",
        "quote_status": "verbatim"
      },
      "source_tier": 1,
      "ai_assisted": false,
      "checked_at": null,
      "checked_by": null,
      "stale": false,
      "versions": 1
    }
  ],
  "access": {
    "plan": "team",
    "policy": "full",
    "locked": []
  },
  "disclaimer": "This registry is a reference service. It is not legal advice …",
  "data_version": "pub_example",
  "as_of": "2026-10-08T07:00:00Z",
  "license": "https://crossnorm.com/terms#data-license",
  "next_cursor": null
}

An example of the response shape. The live record carries its own status, dates and data version.

Trust

How we keep the data honest

  • Primary sources first.

    “Verified” only against a regulator, an act or an official copy of an act. A law-firm or media source can support an indicative value, never a verified one.

  • A person sets “verified” on rule values.

    Imports and AI never do. AI may help draft a value; when it does, the value is flagged as AI-assisted.

  • Facts, not verdicts.

    We don't label websites. We write “listed on … since …” or “not found in … as of …”.

  • One number everywhere.

    Every count on this site, in the API and in reports comes from the same published data, with a definition and a date.

  • Sample data is labelled.

    Preview modules run on sample data marked “Sample data”. It never reaches the API, exports or alerts. Fictional companies use reserved .example domains.

  • No data about people.

    We don't store directors, beneficial owners or personal contacts. Enforcement data covers companies only.

  • Your workspace stays yours.

    Your profile, alerts, decisions and notes are visible only to your organisation. They never feed the API, other clients or public counts.

  • Spot an error?

    Send the primary source to hello@crossnorm.com. Regulators can correct their own record.

What we don't have yet: single sign-on, or certifications such as ISO 27001 and SOC 2. If your procurement requires them, tell us before a pilot.

Pricing

Published, not on request.

  • Plans from €1,000 / year

    Full values with source, quote, dates and history. Higher plans add team seats and the API.

    Request access

  • Free for regulators

    Free access for gambling regulators, issued after we verify your authority's e-mail domain.

    Request regulator access

  • Start with a pilot

    Early access on your markets. Tell us which jurisdictions and checks matter to you.

    Request access

Frequently asked questions

What is Crossnorm?

Crossnorm is a data platform on gambling regulation for payment and compliance teams. It covers payment and AML rules for 67 jurisdictions as structured fields, and ~80 official regulator licence lists and blacklists loaded daily. Each value shows its source, an original-language quote and its dates. Crossnorm is a reference service, not legal advice.

Which jurisdictions and rules do you cover?

67 jurisdictions: 35 in Europe, 12 in Africa, 11 in the Americas and Caribbean, and 9 in Eurasia, the Middle East and Asia. For each, 18 payment and AML parameters in 7 launch topics of a 13-topic framework: payment methods, ownership and payouts, AML thresholds and reporting, player funds protection, taxes at payment, reporting and data, and player protection at payment. A coverage meter shows how many parameters are filled and verified for each jurisdiction.

Where does the data come from, and how do I know a value is right?

Each value carries its source, a verbatim quote in the original language, the effective date, the date we retrieved the source and the date we last checked it, plus a trust status. Most values start as indicative: taken from desk research and not yet checked against the primary source. “Verified” means a person checked the value against a primary source, such as the regulator or the act. “Regulator-confirmed” means the authority reviewed the record on the date shown.

How often are licence lists and blacklists updated?

We load ~80 official regulator lists every day and keep the history of each entry, so you can see when a domain or licence appeared on a list and when it left. Each list shows the date it was last loaded. If a source fails, the list keeps its last good copy and shows that date rather than going empty.

Can I check whether a merchant's domain appears on an official list?

That is what Domain check does. It is in preview and shown with sample data today. It looks up one domain in official lists and licence registers and answers with facts only, such as “listed on … since …” or “not found in … as of …”. Where a register is not loaded, it says “not checked”.

Do you have an API?

API v1 is coming, with early access on request. It returns the same fields as the site in JSON, described in OpenAPI. Every response carries the disclaimer, the data version and an as-of timestamp.

How much does Crossnorm cost?

Plans start from €1,000 / year. Access is free for regulators. Early-access pilots are available: tell us your markets through Request access.

Is this legal advice?

No. Crossnorm is a reference service. It is not legal advice and creates no lawyer–client relationship. Rules change: check the cited source and, where it matters, the competent authority or qualified counsel before acting.

I work for a regulator. Can I use Crossnorm or correct our record?

Yes. Access is free for regulators once we verify your authority's e-mail domain. To correct your jurisdiction's record, e-mail hello@crossnorm.com with the change and its source. When your authority confirms a record, it shows as “regulator-confirmed” with the date.

How is this different from news services or annual legal guides?

News tells you that something happened, and annual guides summarise the law once a year. Crossnorm keeps each rule as a field with its source, quote and dates; keeps every version; loads official lists daily; and shows its coverage for each jurisdiction, gaps included. As-of views by date and per-parameter alerts are coming.

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

Tell us which jurisdictions and checks matter to you, and we'll set up early access on your markets.

Request accessSign in

Plans from €1,000 / yearFree for regulatorshello@crossnorm.com