Skip to main content
Musubi fits alongside your existing treasury operation. Your payment flow, counterparty directory, FX risk policy, and accounting system all stay where they are. Musubi adds three things: an Onboard path to get connected, a Console where your treasury team initiates orders and tracks settlements, and Statements your accounting team downloads on its usual cadence.

​
What stays the same

​
Architecture

Your custodian participates in every settlement — their co-signature is one of four required for the atomic DvP. You don’t need to run your own Canton participant if your custodian’s infrastructure handles it; standing up your own backend is optional for institutions with custom treasury automation.

​
The three pages in this section

Onboard

Credentials, custodian coordination, (optional) backend deployment, connectivity test.

Console

How your treasury team creates orders, reviews competing quotes, and tracks settlements in the Musubi console.

Statements

Settlement confirmations, FX execution reports, month-end reconciliation — the download path for accounting.

Programmatic Access

Webhook + REST + SSE for institutions wiring Musubi into a TMS / ERP (Kyriba, SAP, Oracle) or custom treasury automation.
For most institutions, Onboard + Console + Statements covers the integration. Programmatic Access is the path for institutions with downstream systems that initiate orders or reconcile accounts automatically.