Treasury integration

Treasury is Quant Flow's Token Engine. It manages the token accounts and instructions behind your bank's tokenised-deposit service: issue tokens, move them, redeem them or reserve funds for later use.

The bank remains responsible for the deposit and cash ledger. Treasury coordinates the token movement and reports the outcome so the bank can keep the two records reconciled.

The bank's treasury workflow

1. Prepare the currency, customer and token account. Wait until the account is ready before using it.
2. For issuance, establish the cash backing before requesting tokens. For redemption, confirm token removal before completing the cash payment.
3. Follow the instruction through the enabled policy and signing controls to settlement. An accepted request or an approval is still an intermediate step.
4. Compare confirmed movements and token balances with the bank's records. Assign an owner to delayed, failed or uncertain instructions.

Choose the business action

Cancellation here concerns a lock. It is not a way to undo a settled transfer or cancel any pending instruction. Transfers, locks and releases explains the differences.

Who is responsible

The bank defines the product, performs customer checks and controls cash postings. Quant Flow manages token resources, coordinates the configured custody and network path and reports progress. The deployment operator prepares custody and network readiness and helps investigate platform-side exceptions.

Account freeze and unfreeze are separate controls. Wider contract administration, such as a token-wide pause or a contract upgrade, follows the agreed operator process rather than a customer HTTP operation.

For the implementation team

Treasury is Quant Flow's Token Engine and the customer entry point for tokenised-deposit operations. It owns the contract, customer and account registries and tracks each submitted instruction. Your core banking ledger remains the cash book of record.

What your bank builds

Your adapter maps bank references to Quant Flow resources, screens the intended activity, persists each instruction before sending it, follows its outcome and reconciles that outcome with the bank's own ledger. Keep amounts as decimal strings and preserve the original idempotency key and body through recovery.

Quant Flow orchestrates account provisioning, token transaction preparation, configured custody signing and network execution. You integrate through Treasury's published endpoints; you do not construct raw ledger transactions or call the internal signing and tracking services.

Provision the asset and account path

1. Obtain the assigned network, custody authority and supported asset configuration during onboarding.
2. Inspect contracts. Where your role and deployment allow it, deploy an asset contract, then wait for its confirmed active status. An accepted deployment is not ready for use.
3. Register the customer using your bank's stable reference.
4. Register the account for that customer and asset. Account provisioning is asynchronous; read its status until it is active before submitting token operations.
5. Read the opening balance and compare it with the approved fixture inventory.

Follow Create a customer and an account for request and response examples, including pending and failed provisioning.

Select the token operation

Account freeze/unfreeze uses the separate account controls endpoint. General token-wide pause, contract upgrades and role grants are not customer HTTP operations in this reference.

Follow acceptance through settlement

%%{init: {"theme": "neutral"}}%%
sequenceDiagram
    participant B as Bank adapter
    participant T as Treasury
    participant P as Configured policy and custody
    participant N as Token network
    participant W as Notifications
    B->>B: Persist intent, body and original key
    B->>T: Submit token operation
    T-->>B: Accepted, transactionId and current state
    T->>P: Apply enabled controls and prepare signing
    P->>N: Execute authorised token operation
    N-->>T: Settlement outcome
    T->>W: Business outcome
    W-->>B: Signed notification
    B->>T: Read current transaction and balances
    B->>B: Reconcile cash and token evidence

A submission accepted with 202 can still be pending, rejected or fail later. Only a confirmed outcome establishes that the token operation settled. Follow Operations and their lifecycle and keep bounded polling available alongside signed webhooks.

Worked example: verify a position

This is an illustrative contract response, not a live result. Replace the account and host with your assigned sandbox values.

GET /api/accounts/ACC-0001/balances HTTP/1.1
Host: api.qfp.quantnetwork.net
Authorization: Bearer <access token>
API-Version: 1.0.0

HTTP/1.1 200 OK
Content-Type: application/json

{
  "accountRef": "ACC-0001",
  "customerRef": "CUST-0001",
  "assetId": "GBP",
  "total": "1250.00",
  "available": "1210.00",
  "locked": "40.00",
  "asOf": "2026-08-13T11:58:04.114Z"
}

View in API Reference

• Get an account's balances · GET
• Read the instruction outcome · GET

Balance reads show settled contract positions at the time of the read. They cannot explain every pending instruction on their own. Reconcile the transaction identifier, terminal state, ledger evidence and bank posting reference together.

Investigate incomplete work

For a failed account provisioning or an overdue token instruction, retain the original request, response, identifiers and timestamps. Inspect the resource and outstanding breaks, then follow Handle failures. A polling timeout is an investigation trigger, not proof of failure. Preserve the original key after a lost response; never send a replacement payment simply because the first response was missing.

Policy enforcement and custody mode depend on the assigned environment. Confirm them before using the sandbox to assess approval controls or production readiness. Current issuer dashboard and reserve figures are static and are not settlement evidence.

API Reference

Related pages

• Platform architecture
• Build your integration
• Reconcile against your core banking
• Maintenance and recovery