Key concepts
cardscapability — buying with a card deposit requires the user to have thecardscapability enabled.tradescapability — any buy or sell that involves converting one asset to another requires thetradescapability. UK retail users face a 24-hour post-onboarding cooldown before trading is available.card-withdrawalscapability — selling to a card via OCT requires thecard-withdrawalscapability.- 3DS authorization — card deposits may require user authorization via a 3DS challenge. When they do, the transaction response includes a
confirmationUrl— redirect the user there to complete it. octSupport— selling to a card requires the destination external account to haveoctSupport: "supported". Verify this when linking the payout card.
Supported methods
| Direction | Source / destination | Notes |
|---|---|---|
| Buy | Card | May require 3DS authorization |
| Buy | Bank account | SEPA / FPS / ACH / FedNow / wire — see bank-transfer deposit guides for rail-specific setup |
| Buy | APMs | Apple Pay, Google Pay, PayPal, and Venmo — via the Payment Widget |
| Sell | Card (OCT) | Requires octSupport: "supported" on the external account |
| Sell | Bank account | SEPA / FPS / ACH / FedNow — see bank-transfer withdrawal guides for rail-specific setup |
| Sell | APMs | Apple Pay, Google Pay, PayPal, and Venmo — via the Payment Widget |
Testing in sandbox
Use test card numbers to simulate card deposits and payouts in the sandbox. Crypto deposits can be triggered via the simulate crypto deposit endpoint.Start building
Buy via API
Buy crypto for users from a fiat payment method — card and bank — in a single transaction.
Sell via API
Sell crypto and pay out to a fiat destination — card and bank — in a single transaction.