Supported Destinations
Currencies, countries, and payout rails
The Payouts API supports payouts in fiat currencies and stablecoins. The table below maps each supported fiat currency to typical country(ies) and whether bank and/or mobile wallet rails are available.
Destination Overview
Use this as a quick reference for “where can I send?” and which payment method to use:
- Bank: Use Bank Transfers —
paymentMethodId: "banktransfer",recipient.type: "bank_account". - Mobile wallet: Use Mobile Wallet —
paymentMethodId: "mobilemoney",recipient.type: "mobile_money". - Stablecoin: Use Stablecoin Payouts —
paymentMethodId: "crypto",recipient.type: "crypto_wallet".
Destination is determined by the currency in destinationValue.currency and the paymentLocation field (3-letter ISO country code). Fiat payouts use the currencies listed above.
Stablecoin Payouts (Crypto Wallets)
Market-Specific Requirements (Quick Notes)
- Egypt (EGP): Bank payouts require
bankCode; IBAN format is supported. Thesenderobject may be required for bank payouts (see API reference). Wallets useoperator: "fawry". - Ghana (GHS): No additional fields beyond standard bank/mobile wallet requirements; use
operator: "mtn"for MTN wallets. - Kenya (KES): No additional fields beyond standard requirements; M‑Pesa uses
operator: "mpesa". - Tanzania (TZS): No additional fields beyond standard requirements; use
operator: "mtn"oroperator: "airtel"for wallets. - Uganda (UGX): No additional fields beyond standard requirements; use
operator: "mtn"for MTN wallets. - Francophone (XOF/XAF): No additional fields beyond standard requirements; choose the correct operator for the recipient (see Mobile Wallet and the Francophone sandbox guide).
- Stablecoins (USDT/USDC): Use
recipient.type: "crypto_wallet"withaddressandnetwork(ERC20orTRC20).memois optional but required by some wallets.
Next Steps
- Bank Transfers — Required/optional fields for bank payouts
- Mobile Wallet — Required/optional fields and providers
- Getting Started with Payouts — End-to-end workflow