asset and a network; fiat sides carry an asset (usd or cad) and a rail-specific network. On a transaction, bank instruments carry no rail: each transfer reports the rail its money moved on.
Crypto assets and networks
OMS custodial wallets and on-chain instruments hold stablecoins:
A crypto instrument pairs the asset with a
network. The network on every crypto request field is a closed set:
Send
network values in lowercase. Typed clients generated from the OMS schema validate against these exact values. Availability of an asset on a given network is a separate check: usdc is available on ethereum, base, solana, and tron; usdt is available on ethereum and tron.
Each crypto side also resolves a blockchainAsset object that carries the on-chain identity: the wire-level protocol (evm, svm, sui, or tvm), the chainId, and the tokenId.
Polygon is the recommended network for most use cases: sub-2-second finality, fractions-of-a-cent transaction cost, and native USDC (no bridging or wrapping).
Fiat rails
On a quote, fiat instruments are identified by atype and carry a rail-specific network:
rtp is selectable on quotes and Deposit Address destinations where the receiving bank participates; it is not supported as a Virtual Account destination rail.
For a card buy, the quote’s destination controls where the crypto lands. A walletExternal destination delivers to that on-chain address; any other crypto destination delivers to the customer’s OMS-custodied wallet on the destination chain. A card sell always settles into the customer’s walletCrypto.
Which rails a customer can use depends on the endorsements granted to that customer (basic, cryptoCustody, and usd). Endorsements are granted after verification and delivered via webhook. See Entities and relationships for the endorsement model.
Exchange rates and FX
USD and its stablecoins convert by issuer redemption: USD to USDC or USDT is redeemed 1:1 with the issuer, so there is no market, exchange, or central-bank reference rate and no FX spread. What a quote locks is the fee schedule, not a fluctuating rate. The quote’spricing object expresses this:
pricing.source.amountandpricing.destination.amount: the gross the customer pays and the amount delivered, each padded to its asset’s precision.pricing.exchangeRate: units of the destination asset per unit of the source asset. Present only together with a destination amount.pricing.fixedAmountSide: which side of the trade the amount was specified on.expiresAt: when the locked pricing expires.
pricing.fees lists each OMS, developer, and gas fee as its own entry with type, amount, asset, and side. The source net is source.amount minus fees on the source; the destination gross is destination.amount plus fees on the destination.
Settlement times
Typical production times from initiating a payment to the confirmation event. Inbound confirmations fire when the bank confirms receipt; the same timing applies to payouts.
Amounts above bank-internal thresholds can trigger a compliance review before release: a hold, not a rejection. Execution is never force-split across payments.
Cash networks
OMS supports cash deposits and withdrawals through a partner retail network. A cash-in generates a code the customer presents at a retail location; OMS monitors for the deposit and auto-creates acashToCrypto transaction when cash is received. Cash payouts (cryptoToCash) are delivered as a pickup: the amount must be a multiple of 20.00, up to a maximum of 400.00 per transaction.
Query available locations with GET /cash-locations, passing the provider, the customer’s latitude and longitude, and a flow of cash_in or cash_out. See the Cash-ins and cash-outs page for the full flow.
Network reference endpoint
GET /networks returns the live catalog of networks OMS routes on, with each network’s asset list, on-chain identity, and which OMS resources can use it in which direction. The response derives from the current routing configuration, so it always reflects what the running API accepts. The endpoint takes no query parameters and does not paginate; the catalog is configuration-bounded.
network token you send in request network fields, a category (crypto, fiatAccount, or cash), and a type (blockchain, bankRail, card, or physical). Blockchain networks add chainId (omitted for non-EVM), networkFamily (evm, solana, or tron), and one assets entry per active pair. assets[].contractAddress is omitted for a native asset; assets[].decimals is absent when the onchain scale is unknown for that pair.
supportedBy states, per OMS resource type, whether that network is usable as a source, as a destination, or both. externalAccount is asymmetric: the values are the external-account arm names that can attach on that side (for example, walletExternal for crypto destinations); an empty array means the arm is not selectable on that side.
supportedBy.wallet is populated on every network where OMS can hold value for your project. It covers both the networks OMS directly serves and networks reachable through the custodial-wallet pair configuration (narrowed to the vendors your project is routed on). When the property is absent, wallet custody on that network is not established for your project; treat absence as unknown, not as false.
Fiat availability is scoped to the caller’s project. Rails your project does not have enabled are reported as unavailable on your response even when they are enabled globally.
Consume this endpoint at the boundary of your integration to drive picker UIs and configuration checks. The tables earlier on this page summarize the same catalog at doc-writing time.