Welcome to Quant Flow Platform

Quant Flow supports your bank's tokenised-deposit service, from account setup and token movements to payment controls and daily operation. The Guides explain the product and the bank's responsibilities. Engineers can follow the linked implementation guides and code walkthroughs when they are ready to connect systems.

Who this is for

Bank teams evaluating, implementing or operating Quant Flow: product, treasury, finance, operations, risk and compliance, as well as architects and engineers. Start with the business flow and your team's responsibilities. Request details and code are available through the implementation guides, Recipes and API Reference.

What Quant Flow Platform does

Quant Flow Platform helps your bank issue and manage tokenised deposits and programmable payments. Your core banking system remains the book of record. The platform issues, moves and holds tokens that represent deposits your bank has already booked, and returns the outcome of each operation to your systems.

The customer-facing services work together as follows:

Capability	What it does	Where it is described
Treasury (Token Engine)	Deploys token contracts, registers customers and accounts, mints, burns, transfers, locks, releases and cancels tokens, and reports balances.	Instruments and tokenised deposits, Operations and their lifecycle
Policy Engine	When enabled for the operation type, checks your organisation's policy, allows or refuses the instruction, or holds it for named approvers. Records the decision.	Policy, approvals and audit
PayScript	Runs scripts you import as automations, started on demand or by a trigger, that submit token operations through the same checks.	Programmable payments

Supporting these are identity and access control (users, roles, permissions and approval groups), an activity log for audit evidence, signed webhooks that report outcomes to your systems, and reporting views.

The platform runs either Quant-hosted or in your own infrastructure, with the same API in both. Tokens are issued on a private, permissioned ledger network, and the platform holds no blockchain private keys: signing is done by an external custody service. See Deployment model and Supported networks.

Pick your path

Build the bank's connection

Engineers should follow Build your integration, Before you begin and the Quickstart. Use Recipes for JavaScript and Python walkthroughs, and the API endpoint directory for the full current customer API. Technical topics include authentication, idempotency and retries, errors, webhooks and pagination and filtering.

For a custom approval screen, follow Build your own approval inbox. For automation implementation, follow Write and run an automation.

A banking example

A customer has 100.00 GBP in a deposit your bank has booked. Under the agreed accounting model, the bank sets aside the backing and asks Quant Flow to issue the equivalent tokens. After confirmation, the customer can hold or transfer those tokens. On redemption, the bank confirms that the tokens have been removed before paying the corresponding cash amount.

Your bank owns the deposit terms, customer checks and cash postings. Quant Flow manages the token instruction and reports its outcome. Issuance and settlement legs explains the sequence and how the two sets of records stay reconciled. The amount is illustrative.

The customer journey

The bank prepares the deposit and accounts, then follows each token instruction through to its outcome. Its cash records and the token records stay reconciled throughout the service.

%%{init: {"theme": "neutral"}}%%
flowchart TB
    Prepare["Agree the deposit model and access"] --> Ready["Prepare currency and token accounts"]
    Ready --> Issue["Issue tokens against booked deposits"]
    Issue --> Use["Hold, transfer or reserve tokens"]
    Use --> Redeem["Confirm redemption, then pay cash"]
    Redeem --> Records["Reconcile and retain evidence"]

Each movement follows its own configured controls and settlement path. The diagram does not combine the bank's cash posting and token settlement into one atomic transaction.

Issue and redeem · Transfers and locks · Reconciliation

Explore the platform services

Treasury integration: contracts, account provisioning, token supply, transfers, locks and reconciliation.
Notifications integration: signed events, receiver verification, delivery history and recovery.
Identity and access: user and machine identities, permissions and approval groups.
Policy and approvals: configured controls and independent decisions.
PayScript: scripts, triggers and automation management.
Audit and evidence and issuer reporting: activity records, reporting boundaries and evidence.

Platform architecture explains how the bank, Quant Flow, custody and the token network work together. Technical architecture describes the individual settlement services. Start an evaluation with Your first sandbox session.

How operations reach settlement

Quant Flow first accepts the instruction, then carries out the configured checks and settlement. A request can be waiting for approval, processing or unresolved before a final outcome is available. Acceptance alone does not mean the tokens moved.

Balances change when the token operation settles. Your bank's connected systems read the outcome or receive a notification and use it to complete the relevant booking and reconciliation steps. Operations teams investigate delays and failures before deciding whether another instruction is appropriate.

Policy enforcement must be enabled for the intended operation types in your environment. It is disabled in the shipped settlement configuration. Confirm this during onboarding, and use Operations and their lifecycle for the detailed states.

Get access

Access is arranged with Quant Network. There is no self-service sign-up. See Get access to request credentials.

Take the integration into production

Production readiness: configuration, workflow tests and acceptance evidence.
Daily operations and monitoring: pending instructions, deliveries, approvals and reconciliation.
Maintenance and recovery: preserve work across a change and verify outcomes before resuming.
Access changes and offboarding: retire access and connections without losing obligations or evidence.

For developers building an integration

Follow Build your integration from environment setup through settlement and reconciliation. Then use Implement a backend client for JavaScript request handling and the developer integration coverage map for all operation recipes, request examples, potential responses and API Reference links.

Protected requests go to your assigned gateway with a bearer token. Customer and account workflows use the organisation in that token. Bootstrap authentication and shared catalogues have different access rules; see Authentication and the endpoint reference.

A write returns as soon as it is accepted. Settlement happens afterwards. For a token operation, a 202 Accepted means the request was well formed and the accounts it names are usable. The operation follows the configured policy and settlement path, may wait for approval, and settles on the network. Policy evaluation is disabled in the shipped configuration; confirm its enablement and judged operation types for your environment. Balances change only when it settles. Your integration learns the outcome by reading the operation back or by receiving a webhook.

This is the most important behaviour to design for. Operations and their lifecycle describes every state.

Find the feature you are integrating

Start with the business flow, then use its implementation guide and endpoint. You can integrate token operations first and add automation later.

Your application needs to	Understand	Implement
Connect a bank backend and identify its callers	Authentication, Roles and access	Authenticate, backend client
Set up a currency, customer and token account	Instruments, Customers and accounts	Provision a customer and account
Issue or redeem a tokenised deposit	Issue and redeem	Submit a token operation, track its outcome
Pay another account or earmark funds	Transfers, locks and releases	Make a transfer, transaction recipes
Apply business controls and human sign-off	Policy, approvals and audit	Author a policy, build an approval inbox
Run recurring or conditional payment logic	Programmable payments	Write and run an automation
Restrict an account during a compliance review	Account controls	Freeze or unfreeze
Update positions and recover missed outcomes	Balances, Webhooks	Reconcile with core banking, handle failures
Produce activity evidence and operational views	Audit and evidence, Operator dashboard	Audit search, dashboard summary

The coverage map connects the full external API to these guides and code recipes. Read Limitations before selecting capabilities: dashboard and reserve figures include placeholder data, and not every contract-level function has a customer HTTP endpoint.

Worked example

The shortest useful exchange is reading an account's balance. The figures come from the token contract at the time of the request and include settled operations only.

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"
}

Read balances walks through this call and its errors. Open GET /api/accounts/{accountRef}/balances for the full schema, generated code samples and Try It console. Use credentials and an account reference from your own environment when trying the request.

View in API Reference

Get an account's balances · GET

Errors and edge cases

Every error returns a JSON body with timestamp, status, error and message. See Errors.
A missing, expired or malformed token returns 401. See Authentication.
Some capabilities are not yet available to client applications. Limitations lists them.

Follow a Recipe

Step through the code in JavaScript or Python, inspect illustrative responses, and open the connected endpoint schemas.

Connect and read a balance

API Reference

Open an endpoint for request fields, response examples and the interactive API console.

Operation	Method
Get an account's balances	`GET`