Account model

OMS supports flexible custody models. Pick the model that fits your product; quotes, transactions, compliance, and on-ramps and off-ramps work the same across all three.

Model	Key custody	Built for
Custodial	OMS holds the keys	Regulated fintech, neobanks, and remittance products
Non-custodial	The user holds the keys	Consumer apps where users control their own funds
Agentic	The agent holds scoped keys	Autonomous agents with policy-based spending limits

A single product can combine them: custodial for fiat flows and compliance, non-custodial for user-controlled onchain assets, agentic for autonomous payments. The rest of this page covers the custodial model. For non-custodial and agentic wallets, see OMS Wallet. In the custodial model, value lives in two places: crypto wallets and fiat wallets, both held by OMS for a customer. Everything else in the account model either brings money into those balances (virtual accounts, deposit addresses, cash-ins) or names where money goes outside OMS (external accounts).

Crypto wallets

A crypto wallet is the primary balance store. OMS manages the private keys, so there is no end-user signing and no wallet SDK to integrate. Every operation is a server-to-server API call.

{
  "id": "wlt_5h4jzzpr9xre3bamd9ca7qyghn",
  "type": "walletCrypto",
  "customer": { "id": "cst_vfa0nxw6zvyws9g237jrxn4y7k" },
  "status": "active",
  "asset": "usdc",
  "network": "polygon",
  "address": "0x7b3a9f2c4d1ea8bf6390ce5d2b7fa104c8e3d9b1",
  "balances": [
    { "asset": "usdc", "network": "polygon", "balance": "125.000000", "estimatedValueUsd": "125.00" }
  ],
  "routing": { "claimStatus": "unclaimed" },
  "provider": "...",
  "metadata": {},
  "createdAt": "2026-10-20T14:00:00.000Z",
  "updatedAt": "2026-10-20T14:00:05.000Z"
}

Each crypto wallet holds one asset on one network. address is its onchain deposit address and appears once the custody provider issues it. routing reports whether a virtual account or deposit address delivers into the wallet. A wallet’s status is pending, active, frozen, suspended, or closed. A new wallet reads pending until its address is ready, then active. Creating a wallet: POST /wallets with type: "custodial", the customerId, and details: { network, asset }. The customer needs an active cryptoCustody endorsement. OMS answers 201 with the wallet when it is ready, or 202 with a Location header pointing at GET /wallets/operations/{operationId} while provisioning finishes. Listing and reading: GET /wallets?customerId=... lists a customer’s wallets. GET /wallets/{walletId} returns one wallet with its balances[]. Funding: Send crypto to the wallet’s address, or route deposits into it from a virtual account, deposit address, or cash-in. Multiple wallets: A customer can hold a wallet for each asset and network it needs, for example usdc on polygon and usdc on base. Which pairs your project can create depends on its configuration; GET /networks reports them.

Fiat wallets

A fiat wallet (walletFiat) holds a USD balance at a partner bank on an internal ledger. It has no network and no onchain address. Create one with POST /wallets and type: "fiat". Virtual accounts and deposit addresses can deliver into it, and a quote with a walletFiat source pays out of it. See Fiat wallets.

Virtual accounts

A bank account number assigned to a customer. Each deposit creates a transaction that delivers the funds to the virtual account’s destination: a stablecoin into a crypto wallet or registered external wallet (fiatAccountToCrypto), or USD to a registered bank account or the customer’s fiat wallet (fiatAccountToFiatAccount).

Virtual account
├── id: "va_..."
├── customer: { id: "cst_..." }
├── status: "active"
├── destination: { type, id, asset, ... }      (where each deposit goes)
└── depositInstructions: {
      bankUs: [ { bankName, accountNumber, routingNumber, supportedSources, ... } ]
    }

Show the customer the depositInstructions once they appear. See Virtual accounts.

Deposit addresses

A reusable onchain address assigned to a customer, for “accept any amount from any sender” flows. Each deposit creates a transaction that delivers the funds to the deposit address’s destination: fiat to a registered bank account or the customer’s fiat wallet (cryptoToFiatAccount), or crypto to an OMS wallet or registered external wallet (cryptoToCrypto).

Deposit address
├── id: "da_..."
├── customer: { id: "cst_..." }
├── status: "active"
├── destination: { type, id, asset, ... }
└── depositInstructions: { asset: "usdc", network: "polygon", address: "0x..." }

Deposit addresses are permanent and must be enabled for your project. See Deposit addresses.

External accounts

Bank accounts, debit cards, and external wallets outside OMS. They are references, not balances: OMS never holds funds in an external account. Every external account ID uses the ext_ prefix; type identifies the instrument:

`type`	Instrument
`bankUs`	US bank account (ACH, same-day ACH, wire, and instant payments where available)
`bankIban`	IBAN bank account (SWIFT)
`bankCanada`	Canadian bank account
`card`	Debit card
`walletExternal`	External wallet

Banks and external wallets are destinations. A debit card can be a quote source or destination. A quote can also deliver to a raw onchain address by passing blockchainAddress on a walletExternal destination instead of an ext_ ID. See External accounts to register them and Debit cards for cards.

Overview

Introduction

Fundamentals

Crypto wallets

Fiat wallets

Virtual accounts

Deposit addresses

External accounts

​Crypto wallets

​Fiat wallets

​Virtual accounts

​Deposit addresses

​External accounts

Crypto wallets

Fiat wallets

Virtual accounts

Deposit addresses

External accounts