Every product line, from one customer record
Six lines on one platform. Open a balance, collect into it, convert it, spend it and send it, without a second counterparty.
In the order money moves.
Not alphabetical. A customer gets an account, money arrives, it converts, it leaves, it is spent, and stablecoin rails sit under all of it.
- AccountsOne balance per verified customer, with a wallet address and virtual account details.
- CollectionsCard, bank transfer, local payment methods and stablecoin, across supported markets.
- FX and Trade DeskQuotes, spot trades and OTC orders that only a second person can release.
- Payments and payoutsOne transfer endpoint. The destination decides the rail.
- CardsVirtual and physical cards funded from a stablecoin balance.
- Stablecoin railsUSDC and USDT across five public networks, under everything else.
Everything below starts here.
One customer record, created once and verified once. One record is why the six lines below add up to a single integration.
POST /v1/customers
{
"type": "individual",
"first_name": "Ada",
"last_name": "Okoye",
"email": "ada@example.com",
"external_id": "your-own-id"
}What one integration actually buys you.
Three things. They are why these six belong on one page at all.
- One record
A customer is created and verified once. Accounts, cards, collections and payouts all hang off it, so a holder is never onboarded twice.
- One set of controls
Eligibility, signed events, idempotency and approval work the same way on every line, so a compliance review covers the platform once, not once per product.
- One counterparty
One contract, one integration and one place to ask what happened to a payment, across banking rails, payment networks, cards and blockchain networks.