Regulatory Terminalszyma.co
terminal / about

About

A map of payment and e-money licensing: which regimes exist in which jurisdiction, what each one permits and for which client types, how far it passports, who holds it, and where a provider's claimed coverage cannot be traced to an authorisation. Every value carries the document behind it.

Scale, as of this snapshot

Jurisdictions
73
Regulators
100
Licensing regimes
193
Companies
991
Licence holdings
1,013
Passporting edges
2,610
Activity grants
780
Sourced claims
2,222
Distinct sources
561

Snapshot g-f69ad89f0956a997, built 2026-09-01. Computed from the loaded corpus at render time, never transcribed.

What the evidence looks like

From a register (A)
1,381
Quoted from a document (B)
584
Inferred (C)
210
Reported missing
156
Contested
8

The missing and contested counts are published on purpose. A corpus that reports no gaps is either complete or not looking, and this one is not complete. See Method.

Who maintains it

Built and maintained by Mariusz, who works on cross-border payment and e-money licensing. The corpus is assembled from regulators' own registers and primary legal texts, claim by claim, with the retrieval date recorded for each.

Connect an agent · Report a gap

Limits, stated plainly

Not legal advice. Not a substitute for a regulator's own register. Not complete, and it says where it is not. Where a source has gone offline the value keeps its evidence and is marked unreachable rather than deleted, because a document that existed on a date is still a fact about that date.

Need this implemented in your product?

I turn requirements like these into flows, vendor setups, tests and audit evidence.

Page: /about

Work with me