Most platforms screen after settlement and unwind mistakes. The gate runs first: KYC/KYB, sanctions, Travel Rule, and your program's rules execute as preconditions — an ineligible account never gets a wallet, and an ineligible transfer never executes. There is nothing to unwind.
Verification is a precondition of existence, not a follow-up task.
Every movement is checked in the transfer path itself — pre-settlement.
Individual and entity verification through integrated vendors — verification state gates wallets, portals, and tokens alike.
Onboarding and continuous screening with list-update rechecks — a match freezes the gate, not your ops team's week.
IVMS101 payload construction and counterparty-VASP exchange above thresholds, wired into the transfer path.
Rules-based detection — structuring, velocity, jurisdiction risk — evaluated pre-settlement, not in a monthly report.
Escalations, review queues, and disposition records for the humans who own the program.
Every decision exportable with its evidence — built for examiners, auditors, and counterparty diligence.
| Enforcement point | In the transfer path — pre-settlement; failed checks mean the transaction never executes |
| Identity standards | KYC/KYB via integrated verification vendors; ONCHAINID claims for on-chain eligibility |
| Travel Rule | IVMS101 data model; threshold-based originator/beneficiary exchange |
| Screening | OFAC and global sanctions lists; onboarding + continuous re-screening |
| Audit trail | Append-only, cryptographically signed; every decision carries its evidence |
| Deployment | Same gate across EVM (ERC-3643), XRPL, and the Unykorn L1 |
| Fee posture | Platform fees only; zero transaction-contingent fees |
Vaults that only exist for cleared counterparties — the gate decides who gets keys.
Explore →Tokens that enforce the same eligibility on every secondary transfer.
Explore →Every gated transfer settled atomically with a signed record.
Explore →