Supported Destinations
Currencies, countries, and payout rails
The Payouts API supports payouts in fiat currencies. The table below maps each supported currency to typical country(ies) and whether bank and/or mobile wallet rails are available. A dash means no bank rail is listed for that destination. Availability depends on what is enabled for your account.
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". - Cash pickup:
paymentMethodId: "cash",recipient.type: "cash"— available on select corridors, arranged per account. - Institution wallet:
paymentMethodId: "institutionwallet",recipient.type: "institution_wallet"— a wallet held at a financial institution; arranged per account. The destination table above covers the bank and mobile-money rails.
Destination is determined by the currency in destinationValue.currency and the paymentLocation field (3-letter ISO country code).
Every payout also requires a sender object — fullName, identity, and identityNumber at minimum; some destinations require additional sender fields (called out per market below).
Market-Specific Requirements (Quick Notes)
- Egypt (EGP): Bank payouts require
bankCode; IBAN is supported. Additional sender fields are typically needed (address, date of birth, nationality). Wallets useoperator: "fawry". See Egypt for bank codes, sender fields, formats, and status behaviour. - Ethiopia (ETB): No additional fields beyond standard requirements. Wallets use
operator: "telebirr","mpesa"(Safaricom Ethiopia),"cbebirr"or"yaya"; Coopay E-Birr and AwashBirr cannot receive payouts. For bank payouts,bankCodeis the code returned byGET /v1/payout/banks?country=ETH. There is no account-name check before sending, so a well-formed but wrong number is not caught up front: it may fail when the transfer is processed or reach another valid account. Confirm recipient details before sending. - Ghana (GHS): No additional fields beyond standard bank/mobile wallet requirements; use
operator: "mtn","telecel", or"airteltigo"for the recipient’s wallet. - Kenya (KES): Additional sender fields are required (phone number, nationality, date of birth, purpose/source of funds, relationship). M-Pesa uses
operator: "mpesa". See Kenya for sender fields and examples. - Tanzania (TZS): No additional fields beyond standard requirements; use
operator: "mtn"oroperator: "airtel"for wallets. For bank payouts,bankCodemust be the recipient bank’s SWIFT/BIC code (8 or 11 characters, e.g.CORUTZTZfor CRDB) — numeric or branch-style codes are rejected. UseGET /v1/payout/banks?country=TZAto list banks with their BICs. - Uganda (UGX): No additional fields beyond standard requirements; use
operator: "mtn"or"airtel"for the recipient’s wallet. - Francophone (XOF/XAF): Cameroon payouts require sender
phoneNumber,country,sourceOfFundsandgender. Togo T-Money payouts (operator: "togocell") require senderphoneNumberandcountry. Other XOF and XAF destinations need no fields beyond the standard requirements. Choose the correct operator for the recipient (see Mobile Wallet, West Africa and Central Africa).
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