Pilot environment: testnet, simulated yield, mocked fiat rails — read the disclosure

Accounts and payments for your clients. Yield on the fiat they hold. One API.

Banking as a service: register your end customers as sub-clients, open accounts and IBANs, take money in, move it or convert it, and pay a registered destination.

Yield as a service: place fiat you hold into a TCB curated vault, and read the position back per sub-account.

QuickstartHow it works
Bank transferWallet
Bankingaccounts, IBANs, money in and out
Crypto addressUSDC in
Accounts and IBANsone IBAN per accountfiatTradingPOST/conversionscryptobetween any two accounts: fiat or crypto, either wayTransfersPOST/transfersbetween accounts inside your tree
Sub-clients/sub-clientssame accounts and featuresAnother TCB clientstays inside TCBDestination/beneficiariesIBAN or account numberholder nameregistered before you pay it
Bank accountWallet
POST/depositsPOST/withdrawals
Yieldfiat placed in a curated vault
Curated vaultone per currencyVault positionshares · one priceVault sub-accountspartition your positiontcb:defaultgrowth-fundtreasury-01settled · reserved · available
Your policieson every movementApproval rules, built fromAPPLIES TOpayoutssettlementstransferstradesvault depositsvault withdrawalsnew or edited destinationsWHENamount above or up toone movement or a rolling totalper person or organisation-wideper currency or equivalentassetnetworknew or repeat destinationyour own accountsanother TCB clientoutside the bankstarted by roleon behalf of a sub-clientTHENno approval neededone or more approvalsapprover rolesnamed approverssender confirms with 2FAblock with a reasonAccessroles and seatsscoped API keysidempotency keys
Records and reportingof every movementStatementsJSON or CSVDocumentsPDFExportsCSVSigned webhooksevery eventAudit trailwho did what

money movingstructureplanned, not live

How it works

Banking as a service

  1. 01Open accounts and issue IBANs, one per currency. POST /accounts
  2. 02Money arrives, to an IBAN or as crypto at a TCB-issued address. POST /crypto-deposit-addresses
  3. 03Register a destination, then pay it. POST /payouts
  4. 04Move, trade and settle inside TCB, instantly. POST /transfers POST /conversions POST /settlements
  5. 05Add sub-clients, your end customers, with the same accounts and features. POST /sub-clients
  6. 06Be told when it settles, signed events, no polling. POST /webhooks

Yield as a service

  1. 01Place fiat from an account you control into a curated vault. POST /deposits
  2. 02Share price rises; your share count never changes. GET /positions
  3. 03Partition your position by fund, strategy or product. POST /sub-accounts
  4. 04Withdraw back to a fiat account. POST /withdrawals

Controls and records

  1. 01Set your approval rules: for payouts, settlements, transfers, trades and more; approvals, 2FA or a block.
  2. 02Give every person and key only what they need: roles and seats, scoped API keys.
  3. 03Prove every movement: statements, documents and exports, signed events, audit trail. GET /statements POST /webhooks

Understand the model

Sub-clients

Register each end customer under your root. TCB records the identity you supply and screens it.

Accounts and IBANs

Fiat accounts in one currency each, owned by you or by a sub-client. Every account has an IBAN.

Destinations and payouts

Register where a payment is going ahead of sending it, then pay it from an account you control.

Vault positions

A deposit buys shares in a vault. Read what each sub-account holds at any time.

Webhooks

A signed event when a movement is held, released, settled, failed or returned, so you do not poll for it.

Where to start

Quickstart

Your first authenticated call, then test money end to end.

Concepts

Banking as a service and yield as a service — the model behind every call.

Guides

Task by task: sub-clients, accounts, crypto deposits, conversions, destinations, payouts, and vault deposits.

Webhooks

Signed events, verification, retries and secret rotation.

API reference

Every endpoint, generated from the specification you integrate against.

Errors

The error envelope, the status table and what to do about each code.

Need a key?

Keys are issued during onboarding. Write to partners@threecomma.group.

What the API covers today, and what follows: Roadmap.