Skip to main content

Overview

The Yala API uses standard ISO codes for currencies and countries:
  • Currency codes: ISO 4217 3-letter codes
  • Country codes: ISO 3166-1 alpha-3 3-letter codes

Common Currency Codes

CurrencyCodeExample Countries
Nigerian NairaNGNNigeria (NGA)
US DollarUSDUnited States (USA), Canada (CAN)
Chinese Yuan (RMB)CNYChina (CHN)
EuroEURGermany (DEU), France (FRA), Spain (ESP)
British PoundGBPUnited Kingdom (GBR)
Indian RupeeINRIndia (IND)
Ghanaian CediGHSGhana (GHA)
South African RandZARSouth Africa (ZAF)
Canadian DollarCADCanada (CAN)
West African CFA FrancXOFSenegal (SEN), Cote d’Ivoire (CIV)
Central African CFA FrancXAFCameroon (CMR), Gabon (GAB)

Common Country Codes

CountryCodePrimary Currency
NigeriaNGANGN
United StatesUSAUSD
ChinaCHNCNY
United KingdomGBRGBP
IndiaINDINR
GhanaGHAGHS
South AfricaZAFZAR
CanadaCANCAD
GermanyDEUEUR
FranceFRAEUR

Discovering Valid Codes via API

Method 1: Use GET /pairs

The GET /pairs endpoint returns enabled currency pairs for your business. This shows which currencies are available:
curl https://gateway.staging.useyala.com/v1/payout-api/payouts/pairs \
  -H "x-api-key: <YOUR_API_KEY>"
Response includes baseCurrency and quoteCurrency codes.

Method 2: Use GET /methods

The GET /methods endpoint requires you to specify a corridor. If you’re unsure which codes to use, try common combinations:
# Example: Check NGN to CNY
curl "https://gateway.staging.useyala.com/v1/payout-api/payouts/methods?sourceCurrency=NGN&destinationCurrency=CNY&destinationCountryCode=CHN" \
  -H "x-api-key: <YOUR_API_KEY>"
If the corridor is not enabled or invalid, you’ll receive an error message indicating which parameter is incorrect.

Official ISO Standards

For complete reference lists:

Best Practices

  1. Validate codes before API calls - Use the reference table above or ISO standards to ensure codes are correct
  2. Use GET /pairs first - Check which currency pairs are enabled for your business before building your UI
  3. Handle errors gracefully - Invalid currency or country codes will return 400 Bad Request with a clear error message
  4. Cache enabled pairs - The list of enabled pairs doesn’t change frequently, so cache the response from GET /pairs
If you’re building a UI, call GET /pairs on page load to populate currency selection dropdowns with only enabled options.