Jurisdictions & standards
A base layer that speaks the standards your counterparties already run on.
ISO 20022 on the message layer, FATF Recommendation 16 on transfers, Basel SCO60 where a bank carries the exposure, and the GENIUS Act on the cash leg. Below that, the ledger. Above it, the jurisdiction — which decides who may be sold to and which registered party must do the selling.
Standards, with the dates that matter
Stated as of September 2026. Where a rule is proposed rather than final, this page says so.
| Standard | Status | What it governs | What the platform does about it |
|---|---|---|---|
| GENIUS Act US payment stablecoins | Rules proposed Enacted 18 Jul 2025. Treasury NPRM published 18 Aug 2026; comments close 19 Oct 2026. Section 3(b)(1) applies 18 Jul 2028. | Who may issue a payment stablecoin, reserve composition, and a registration path at the OCC for qualifying foreign issuers | We never issue. The cash leg is a permitted issuer’s instrument, and the issuer is named on the instruction |
| Basel SCO60 Bank cryptoasset exposures | In force, under review Standard effective 1 Jan 2026. The Committee expedited a targeted review of elements in Feb 2026 with an update due later in 2026. | Group 1 versus Group 2 classification, and the capital a bank must hold against each | Instrument metadata carries the classification inputs a bank’s treasury needs, rather than making them ask |
| FATF Recommendation 16 Travel Rule | Adopted by jurisdiction | Originator and beneficiary information travelling with a qualifying transfer between service providers | Transfer messaging is a policy step at OPS-05.01, gated per jurisdiction threshold |
| ISO 20022 Payment messaging | Live on the fiat leg | Structured payment messages with rich remittance data | The reconciler matches on structured remittance fields instead of parsing a free-text reference |
| MiCA EU markets in cryptoassets | Applies in the EU | Authorisation of service providers, and issuance of asset-referenced and e-money tokens | EU tenants route only to authorised counterparties; the authorisation is the partner’s, not ours |
| Reg D / Reg S / Reg A+ US securities exemptions | Enforced in the engine | Solicitation, eligibility, verification burden, preemption and reporting | Selected at OPS-01.02 and enforced downstream — see the issuance studio |
Jurisdiction picker
Pick a domicile. The engine shows the regime, who must hold the licence, and what it enforces.
How this is configured
Nothing above is hard-coded per country. Each layer is a versioned rule set, and a jurisdiction is a selection across those layers. Adding a country is a configuration and a partner, not a release — which is what makes a multi-jurisdiction programme survivable. The version that applied to a decision is recorded with the decision, so a rule change next quarter does not rewrite what was lawful last quarter.