Platform architecture

Quant Flow helps your bank issue, move and redeem tokens representing deposits held by the bank. It also supports reserving funds, configured payment controls and automated payment workflows.

Your bank's core banking system remains the main record of the cash deposit. Quant Flow records the token side of the arrangement. Your bank keeps those records reconciled and remains responsible for customer checks and the cash postings.

A deposit moving through Quant Flow

Consider a customer who wants to use 100.00 GBP of an existing bank deposit as tokens. The amounts are illustrative.

1. Your bank confirms the deposit and sets aside its backing under the agreed accounting model.
2. The bank requests the issue of 100.00 GBP in tokens to the customer's token account. This is called minting.
3. Quant Flow follows the configured controls, obtains signing through the custody service and submits the token movement to the permissioned network.
4. Once settlement is confirmed, the bank checks the token balance and reconciles it with the deposit records.
5. When the customer redeems, the bank first confirms that the tokens have been removed. This is called burning. It then completes the corresponding cash posting.

A request can be accepted while work is still pending. An approval also does not establish settlement. Operations teams need the confirmed token outcome before completing the workflow's corresponding bank-side step.

%%{init: {"theme": "neutral"}}%%
flowchart TB
    Bank["Bank: check deposit and prepare instruction"] --> Flow["Quant Flow: receive instruction"]
    Flow --> Controls["Apply enabled policy and approval controls"]
    Controls --> Custody["Configured custody: authorise signing"]
    Custody --> Network["Permissioned network: settle token movement"]
    Network --> Outcome["Quant Flow: report the outcome"]
    Outcome --> Reconcile["Bank: confirm and reconcile records"]

Read Issuance and settlement legs for the cash and token sequence, and Issue and redeem for the implementation steps.

The parties

Bank staff can administer access, policies and approval groups through the Management Panel where it is available. Bank systems use the published API. The platform can be Quant-hosted or run in your own infrastructure; the customer API is the same in both. See Choose your integration model and Deployment model.

The book of record

Your bank retains the customer identity, deposit records and customer due diligence in its own systems. Quant Flow stores the customer and account references the bank supplies and reads settled token balances from the token contract.

The bank performs its customer and anti-money-laundering checks before submitting instructions. The current customer API has no built-in connection that performs those checks in the bank's screening system, and no endpoint that posts the cash leg to core banking. Your bank's integration supplies those connections.

For a mirror arrangement, reconciliation matches the customer's token and deposit positions. For an omnibus arrangement, it also covers the pooled backing and customer entitlements. Agree the model with your accounting and deployment owners before interpreting the balances.

Platform services

Controls and operational limits

The bank chooses its business rules and authorised approvers. Quant Flow evaluates configured policies when enforcement is enabled. Policy evaluation is disabled in the shipped settlement configuration, so creating a policy alone does not establish that instructions will be checked. Verify enforcement during the evaluation.

Custody approval is a separate control over signing. An instruction can pass a business policy and still wait for, or fail, signing. Use different named identities for submission and approval and test the separation of duties in your environment.

Confirmed token movements cannot be reversed on the network. A correction requires a new authorised instruction. A missing notification or delayed response needs investigation before resubmission, since the original instruction may already have settled.

The current customer API supports account controls, token operations and documented contract deployment. Wider contract administration, infrastructure recovery and whole-environment resets require the agreed operator process. See Limitations, Maintenance and recovery and Resetting your tenant.

Quant Flow reference architecture

The original architecture view places Quant Flow alongside bank applications, custody and ledger networks. Deployment configuration determines which connections are available. It does not establish that a core-banking or screening connector is supplied with the customer API.

For architects and engineers

Technical architecture retains the detailed service responsibilities, diagrams, transaction states and worked request/response examples. Use Build your integration for the implementation sequence, Recipes for code walkthroughs and the API Reference for request fields and potential responses.

View in API Reference

• Submit a token operation
• Read its outcome
• Read an account balance

API Reference

Related pages

• Your first sandbox session
• Choose your integration model
• Issuance and settlement legs
• Daily operations and monitoring
• Technical architecture