Compliance runs inside the settlement path. Travel-rule screening, sanctions checks and attestations execute within every transaction.
| Regulation | Jurisdiction | Coverage |
|---|---|---|
| FATF Travel Rule | Global | Originator and beneficiary information shared at settlement |
| MiCA | EU | CASP / EMT / ART obligations modelled in token templates |
| DORA | EU | ICT risk register, incident reporting, third-party register |
| eIDAS 2.0 | EU | Wallet-ready identity credentials |
| PSR / PSD3 | UK / EU | Strong customer authentication, open finance interfaces |
| MAS Notices | Singapore | Digital token services, technology risk management |
| HKMA SFC | Hong Kong | Virtual asset and tokenised product guidelines |
| NYDFS | United States | Part 200, Part 500 cybersecurity |
| OFAC / EU / UN / UK HMT | Global | Continuous sanctions screening with daily list refresh |
Every transaction passes through the compliance engine before it can settle. The engine verifies identity, screens sanctions and PEP lists against current data, then evaluates the jurisdictional rules against the token template, the parties and the amount. A failed check stops the transaction at zero state, so no part of it happens.
Risk officers, regulators and internal auditors: we will provide the documentation you need to assess AETHER.