Skip to main content
Status: the dedicated statement endpoints described below (CSV, JSON, PDF) are coming. In the interim, settled-order details are retrievable per-intent via GET /api/v1/orders/{intent_id} (full settled record) or the compliance snapshot endpoint for regulatory fields. Scheduled batch statements are on the roadmap.
Statements is the default integration path for the accounting and compliance side of the workflow. Your GL ingests settlement confirmations on a daily or weekly cadence; your compliance archive takes a monthly record set; regulators get jurisdiction-filtered exports on request. For institutions wiring real-time accounting or TMS-driven reconciliation, see Programmatic Access.

​
Statement types

One row per settled intent, over a date range. Columns match the general ledger handoff:
ColumnDescription
intent_idFXOrder UUID — correlate with your internal payment reference
transaction_hashAtomic DvP settlement proof — one hash covers all four legs
settled_atISO 8601 timestamp
source_currency / source_amount_actualWhat left your custody
target_currency / target_amountWhat the receiver got
fx_rateExecuted rate
counterparty_party_idReceiver institution
counterparty_custodian_party_idReceiver’s custodian
jurisdiction_sender / jurisdiction_receiverFor reporting routing
Status: coming. Interim: the per-intent endpoint returns the same data one order at a time.

​
Filtering

Planned filters across all statement types:
  • Date range — from / to on settled_at
  • Status — SETTLED by default; include FAILED / EXPIRED for operational reviews
  • Counterparty — limit to a specific receiver institution
  • Jurisdiction — limit to a specific reporting regime
  • Currency pair — limit to JPYSC0 → USDCx, etc.

​
Consuming statements

Once statements land, your accounting + compliance systems ingest them via your existing pipelines — whatever you use today to ingest daily settlement files from banks or other counterparties. Most institutions schedule a daily CSV pull into their GL and a monthly JSON dump into their compliance archive. Musubi retains the on-ledger record for 10 years independently of what your archive does; the dual-retention model means a regulator subpoena can be answered from either side. See Audit Trail.

​
Interim: per-intent retrieval

Until batch endpoints ship, settled-order details are retrievable one at a time: 
GET /api/v1/orders/{intent_id}
Returns the full settled FXOrder record — structurally the same content that will appear in batch statements, just retrieved on demand. If your accounting team needs records now, scripting against this endpoint is the path; when batch endpoints ship, switch the scheduled job from a per-intent loop to a single batch call.

​
Next steps