What stays exactly as it is
| Existing system | Role unchanged |
|---|---|
| KYC vendor (Persona, Sumsub, Jumio, in-house) | Originator / beneficiary identity verification |
| Sanctions vendor (Chainalysis, Elliptic, TRM) | Screening, list-version tracking, freshness |
| Travel Rule provider (CODE, VerifyVASP, Notabene, TRUST, Sygna) | Wire-protocol transmission to counterparty VASP for your KoFIU / JVCEA / FATF filing |
| STR filing pipeline | JAFIC / KoFIU submission on BLOCK alerts |
| Compliance archive + retention | Your internal archive (Musubi also retains independently on-ledger for 10 years) |
| Key management + HSM | Your existing signing infrastructure protects the Canton Party ID key |
| Whitelist tooling | Whitelist the Musubi settlement address once, same model as every other destination |
Architecture
Attestation metadata (KYC / sanctions / risk / consent) flows into the Musubi backend at order creation — snapshotted from your existing systems, never re-verified by Musubi. Settlement records flow out as downloadable audit exports into your archive and accounting systems.The three pages in this section
Deploy
Canton participant + Musubi backend in your infrastructure. Provisioning, connectivity, TLS, Day-2 operations.
Console
How your ops team works in the Musubi console — proposal inbox, quote review, co-signature, dashboards. No code.
Audit Exports
CSV / JSON / PDF dossier downloads by date range, intent, or status. The default integration path for compliance archives.
Programmatic Access
REST + SSE for custodians with custom compliance rails or real-time reconciliation. Java / Spring examples included.