Why whitelist first
Registering an external account is the sensitive step, not paying out to it afterward:- When you authenticate with a Bearer session, registering requires step-up verification (
X-Step-Up-Token). - Once an account is registered and enabled, payouts to it need no per-request OTP — the whitelisting step already proved you control the destination.
- Disabling or deleting an external account immediately stops any future payout (including scheduled automations) from reaching it. Payouts already in flight are unaffected.
Register a destination
Both kinds are registered through the same endpoint,POST /accounts/external-account, distinguished by type:
- Whitelist a crypto account — a wallet address on a specific chain.
- Whitelist a fiat bank account — a bank beneficiary for fiat settlement.
Addressing a destination
Every external account has areference — your own identifier for it — alongside its numeric id. A payout can name the destination by either: destination_account_id or destination_account_reference.
An org can register at most one destination per (reference, chain) pair: registering the same reference again on the same chain returns 409.
Prerequisites
- Authentication (
X-API-KEY, or a Bearer session with step-up) - A supported currency and, for a crypto account, a supported chain (see Networks and Currencies)
Next steps
- Whitelist a Crypto Account
- Whitelist a Fiat Bank Account
- Once registered and enabled, use the account as a payout destination.