Three regulatory regimes are live or imminent. Reserve adequacy, redemption mechanics, operational safeguards, VASP travel-rule data sufficiency, tokenized-RWA classification — every one is a separate audit lens, and they overlap unevenly. Eight scenarios give an issuer the readiness surface in the browser, exportable as Policy Mandates the audit team can replay.
For teams working with Paxos · Circle · Bridge (post-Stripe) · Anchorage · usable by any covered VASP entering EU or US licensing
The four ordered stages of the stablecoin-compliance chain, with explicit handoff payloads on each edge. VASP Travel Rule and AML monitoring are cross-cutting overlay branches, not inline stages. West Africa and mBridge form a separate frontier-settlement branch. Each scenario card below remains individually openable.
Stages demonstrated at Post Oak Labs; run + audited at AINumbers
Start at the issuance surface — reserve adequacy, redemption rights, operational safeguards. Move to the VASP-to-VASP edge (Travel Rule). Pin the tokenized-RWA adjacency (where issuer business models increasingly extend). Close with the financial-crime overlay that pulls every transaction through AML transaction monitoring.
Reserve composition × redemption rights × operational safeguards scored against MiCA Title III (Arts. 35–42) and GENIUS Act payment-stablecoin regime. Live MiCA checklist line-by-line, GENIUS classification check, composite readiness score /100, Policy Mandate export — the artifact the issuer's risk committee can sign.
Originator + beneficiary data sufficiency scored across FATF baseline, EU TFR (Reg. 2023/1113, applicable from 30 Dec 2024), FinCEN 31 CFR 1010.410(f), UK MLR and MAS PSN02. Field-by-field requirement matrix, de-minimis threshold, sunrise-issue handling. The VASP-edge layer the stablecoin issuer's redemption partners read.
Pre-issuance pathway determination — 8 asset classes × 7 jurisdictions × offering structure → MiCA + Howey classification + pathway verdict (viable / remediate / not-viable). The adjacency every stablecoin issuer's business team is modelling.
Six rule families with FP/TP modeled against a synthetic 100K-tx population, precision/recall live, AP2 ruleset export. Cross-link from the RegTech hub; every issuer reads every transaction through this surface before settlement.
Four-step architecture designer for CBDC and distributed-ledger deployments — structural model, platform selection (Corda / Fabric / R3 / Canton), cross-CBDC interoperability scenario, and Policy Mandate export. For issuers evaluating wholesale CBDC rails or DLT settlement infrastructure.
Model cross-border settlement across West Africa — Nigeria eNaira/cNGN, Ghana e-Cedi, ECCU DCash. Settlement economics vs correspondent banking, FATF compliance overlay, Policy Mandate export. A live playbook for issuers targeting African retail or remittance markets.
Model multi-CBDC PvP settlement across mBridge participant corridors — e-CNY, Digital Dirham, e-Baht, e-HKD, Digital Riyal. Settlement mechanism design, UTC overlap diagnostics, interoperability assessment. The wholesale settlement layer every institutional issuer must stress-test.
Validate reserve composition against GENIUS Act (effective Jan 2027). 1:1 backing, UST ≤93-day maturity caps, Fed deposit allocation, asset segregation, monthly disclosure, AML/BSA programme. The US regulatory layer every dollar-stablecoin issuer must clear before January 2027.
MiCA Title III is live in the EU; the GENIUS Act has set the US standard; FATF R.16 governs the VASP-to-VASP edge; AMLA 2026 will harmonise. The reserve audit team, the redemption-mechanism team, the VASP-onboarding team, and the TM team all read different parts of the same regulation set — and the issuer pays for the overlap once.
The eight scenarios here are the curated path. Reserve adequacy and redemption mechanics in the first scenario. VASP-to-VASP data sufficiency in the second. Tokenized RWA adjacency in the third — because every issuer's growth story now includes a tokenized-asset sleeve. The AML cross-link is the layer that catches the issuer if the issuance side is well-engineered but the downstream rails leak.
Every output exports as an Policy Mandate — the audit team replays it, a downstream agent runtime enforces it, the same JSON is the trail.
The stablecoin / RWA cluster in the catalog — reserve auditing, VASP travel-rule checking, stablecoin AML mapping, tokenized-asset compliance, RWA tokenization cost modelling.
The Tool Chain Composer renders the AINumbers catalog as a DAG with the 45 scenarios highlighted. The stablecoin / RWA cluster connects sideways to the regtech surface and to the agentic-runtime mandate layer.
MiCA / GENIUS readiness, FATF Travel Rule, tokenized RWA and wholesale settlement corridors — we’ve advised on tokenized rail implementations across frontier markets. Let’s talk.
Talk to our team →