Skip to main content
Before you start: the OMS API is in early access. Every endpoint, including the ones in this guide, requires an early-access API key. Request access before you begin.

​
How it works

A sender deposits fiat in their local currency via card, ACH, or cash. OMS converts to USDC on Polygon, settles in under two seconds, then converts back to fiat and delivers to the recipient’s bank account, mobile wallet, or cash pickup location. In OMS terms this is a chain of transactions across two parties. The sender funds USDC into an OMS wallet (a cashToCrypto cash-in, a fiatAccountToCrypto bank deposit, or pull-from-card). You then pay out from that wallet to the recipient: cryptoToFiatAccount for a bank account or cryptoToCash for a cash pickup. The recipient is registered once as a counterparty (POST /counterparties) that owns a bank external account (POST /external-accounts with owner kind counterparty); the payout quote references that account by its ext_ ID, and OMS records each side’s identity on the transaction’s party object.
Remittance flow
1Sender→OMSDeposit fiat via card, ACH, or cash
2OMSConverts fiat to USDC (cashToCrypto / fiatAccountToCrypto)
3PolygonSettles USDC onchain (~2s finality)
4OMSConverts USDC to recipient currency (cryptoToFiatAccount / cryptoToCash)
5OMS→RecipientDelivers local fiat via bank, mobile wallet, or cash pickup
Fiat-to-fiat settlement that takes 2-5 days through correspondent banking completes in under two minutes using Polygon as the settlement layer.

​
What is available today

The building blocks are part of the canonical API. The sender side uses the cash-in flow or a virtual-account bank deposit; the recipient side uses a POST /quotes and POST /transactions payout (cryptoToFiatAccount to a bank, cryptoToCash to a cash pickup), executed by referencing the quote with quoteId. Corridor rates are locked at quote time in the quote’s pricing (exchangeRate and effectiveRate), and compliance and KYC are handled by OMS at every step. Recipient counterparties and their bank accounts are registered with POST /counterparties and POST /external-accounts; cash pickup is enabled per project through early access. Global remittance is enabled per project through early access; contact us before you build against it.

​
Planned capabilities

  • Card on the sender side
  • Additional multi-currency corridors
Global remittance is under active development and available through early access. Contact us to enable it for your project.

Register interest

Share your use case and we’ll reach out when global remittance is available.