Get access

Start onboarding through your Quant contact or [email protected]. State whether you need an evaluation environment or a production integration, and whether Quant or your bank will host it. Access arrangements and any evaluation terms are agreed with that contact; the API does not grant self-service access to a new bank.

From onboarding to a first evaluation

Prepare access and signing with the deployment owner before using the sandbox to judge a payment workflow. The handover gives both the bank's technical and operational teams the information they need.

%%{init: {"theme": "neutral"}}%%
flowchart TB
    Agree["Agree flows, hosting and responsibilities"] --> Environment["Receive assigned environment details"]
    Environment --> Access["Activate people and system access"]
    Access --> Ready["Verify currencies, accounts and signing"]
    Ready --> Test["Exercise the agreed sandbox workflows"]
    Test --> Evidence["Review outcomes and acceptance evidence"]

Access is arranged with your Quant contact. A successful sign-in does not prove that signing, policies or every workflow is ready. Agree dates and any remaining setup with the deployment owner.

Your first sandbox session · Production readiness

Prepare your onboarding information

Provide the information needed to configure the integration:

Your organisation and the people responsible for administration, integration and operations.
The intended deposit/payment flows, assets or currencies, network and custody arrangement.
Your preferred deployment model and the bank's gateway, identity-provider and connectivity requirements.
The test scenarios, approval responsibilities, webhook receiver and evidence required for acceptance.

For a client-hosted deployment, review the infrastructure responsibilities in Deployment model.

Request a sandbox for both teams

Supply each evaluator's full name, work email and role. Identify who will call the API and who will evaluate the Management Panel. Include currencies of interest, your intended deposit/accounting model and any bank-network restrictions, particularly whether you can expose an HTTPS webhook receiver.

Request separate named identities for the submitter and approver where you will test separation of duties. Do not share logins. Agree the provisioning date with your Quant contact; there is no universal lead time published by the API.

Receive the environment configuration

Before the first API call, obtain the assigned gateway URL, tenant identifier, supported API version, first administrator invitation and enabled assets. For backend access, also obtain the identity-provider token endpoint, machine-client credential format and rotation process. Keep credentials in your backend secret manager.

Quant creates the organisation and first administrator during onboarding. The administrator receives an email invitation and completes initial sign-in and password setup. Use POST /api/auth/login, then POST /api/auth/new-password if the response contains NEW_PASSWORD_REQUIRED. The activation flow is POST /api/auth/activate. Follow Authenticate for the exact request bodies and responses.

Onboarding also establishes per-currency custody and token-contract deployment responsibilities. Do not assume a registered customer or successful login proves that a contract or signing key is ready.

Check the evaluation handover pack

Item	What to verify before starting
Environment and version	API gateway, Management Panel address, organisation identifier and supported API version.
Named user invitations	Each person can complete activation and has the intended role.
Machine access	Assigned token endpoint, client authentication method and securely issued credentials; machine access is separate from human sign-in.
Seed inventory	Asset contracts, customers, accounts, wallet addresses and opening balances available to your organisation. Example identifiers in this handbook are illustrative.
Integration materials	API Reference, request examples and Recipes, accessible without a private repository checkout. Ask your contact for any agreed Postman collection.
Controls and event delivery	Enabled policies, independent approvers, custody mode, network and webhook signing configuration.
Reset and support	Agreed operator-assisted reset procedure, support route, operating hours, retention and known limitations.

If your network cannot expose a suitable receiver, ask your Quant contact to agree an evaluation receiver or another supported approach. Do not assume a hosted receiver is included: the customer API does not provision one. Use bounded transaction reads to follow the token quickstart while connectivity is arranged, and test webhook delivery before accepting the full integration.

Configure your organisation

Use the assigned tenant and administrator identity to configure the resources your integration needs:

Setup	API Reference	Guide
Inspect token contracts; deploy where agreed	GET /api/contracts, POST /api/contracts	Instruments and tokenised deposits
Invite named users	POST /api/tenants/{id}/users	Identities and entitlements
Read permissions and define roles	GET /api/permissions, POST /api/tenants/{id}/roles	Roles and access
Configure approval groups	POST /api/tenants/{id}/groups	Build your own approval inbox
Register an event receiver	POST /api/webhooks	Receive your first webhook

Verify your first connection

Make a protected read using GET /api/users/me, then inspect the contract and account resources assigned to your integration. Follow Before you begin, Create a customer and an account and Build your integration.

Agree the onboarding sequence and target dates with your platform contact. The public API does not promise a fixed provisioning lead time. You can review the Guides, source examples and API Reference before credentials are issued; executing requests requires access to an assigned environment.

Complete the onboarding handover

Keep one environment record shared by the integration and operational teams: assigned URLs/version, tenant and asset identifiers, gateway/identity-provider owner, custody and network owner, webhook verification configuration and escalation channel. Store credentials separately in a secret manager. Ask the operator to confirm signing readiness and deployed authentication/permission enforcement rather than treating invitations as proof that every control is enabled.

The bank supplies customer screening, cash-posting rules, references and a receiver; Quant/operator supplies the environment and agreed signing/connectivity configuration. After the first protected read, provision the test asset/account path, then use Production readiness to agree evidence for each enabled workflow.

Follow a Recipe

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

Create a customer and provision an account

Implementation resources

Team members code recipes.

Use Implement a backend client for request handling, durable idempotency and outcome tracking. The developer integration coverage map links every public operation to its API Reference and contract-derived code recipe. Replace example identifiers with values from your assigned environment.