Interoperability

Integrating within the supported settlement boundary

This handbook covers Quant Flow tokenised-deposit operations in your assigned environment. Your bank connects its core banking or payments hub through the gateway, submits token instructions, and reconciles confirmed outcomes. Platform architecture shows that boundary.

A transfer between token accounts is not evidence of a cross-bank cash payment, an FX conversion or securities delivery-versus-payment. Agree any wider settlement arrangement separately before treating it as an available customer journey.

What your adapter connects

1. Map your bank's customer and account references to the registered Quant Flow resources.
2. Confirm the asset contract, account status, network and custody authority for the operation.
3. Persist the business instruction and its idempotency key, then submit the supported mint, burn, transfer or lock operation.
4. Track the transaction to its terminal outcome using reads and verified notifications.
5. Reconcile that outcome with your cash ledger and retain the evidence.

Quant Flow handles token execution and its reported outcome. Your bank owns screening, cash postings, business authorisation and reconciliation. A wider network connection or a planned connector does not add a public endpoint to this API.

API Reference

Related pages

• Choose your integration model
• Issuance and the settlement legs
• Transfers, locks and releases
• Reconcile against your core banking
• Limitations