Paystack Currency Not Supported Error

When you initialize a transaction with a currency your account does not support, Paystack responds with:

HTTP/1.1 400 Bad Request
Content-Type: application/json

{
  "status": false,
  "message": "Currency not supported"
}

You may also see variations like "Currency not supported for this business" or "Invalid currency" if the currency code itself is malformed. The HTTP status is always 400.

This error fires on /transaction/initialize, /charge, and any other endpoint where you specify a currency. It means Paystack recognized your API key and authenticated you, but the currency you requested is not in the list of currencies your account can use.

Paystack supports different currencies depending on the country your business is registered in. As of July 2026:

Business country	Default currency	Additional currencies (may require activation)
Nigeria	NGN	USD, GHS (with approval)
Ghana	GHS	USD (with approval)
South Africa	ZAR	USD (with approval)
Kenya	KES	USD (with approval)

This table represents common configurations. Paystack continues to expand, so check the official documentation for the latest list. Some currencies require additional business verification or a specific account type.

If you are building for multiple African markets, you may need separate Paystack accounts for each country. A Nigerian account cannot charge in KES directly. You would need a Kenyan Paystack account for KES transactions.

1. Your account is not activated for that currency

This is the most common cause. You have a Nigerian Paystack account and you sent currency: "KES". Your account only supports NGN by default. You need either a separate Kenyan account or to contact Paystack about multi-currency support.

2. Wrong country account

You registered your Paystack account in Nigeria but your customers are in Kenya. You send currency: "NGN" but your customers' cards are Kenyan. The transaction might fail not because of the currency error but because of geographic restrictions. Make sure your account country matches your target market.

3. Currency code format is wrong

// WRONG: lowercase
{ currency: "ngn" }

// WRONG: full name
{ currency: "naira" }

// WRONG: symbol
{ currency: "N" }

// WRONG: with extra whitespace
{ currency: " NGN " }

// RIGHT: uppercase ISO 4217
{ currency: "NGN" }

Paystack expects the ISO 4217 three-letter currency code in uppercase. Anything else triggers an error.

4. Currency enabled in test mode but not live mode

You tested your integration in test mode where USD was enabled. You switch to live mode and get "Currency not supported" because your live account has not been approved for USD transactions yet. Test and live currency settings are independent.

5. Omitting currency and expecting Paystack to guess

If you omit the currency field, Paystack uses your account's default currency. If your account default is NGN but you intended to charge in GHS, the amounts will be wrong. Always specify the currency explicitly.

There are two ways to check which currencies your account supports:

1. Paystack dashboard

Log in to your Paystack dashboard. Go to Settings. Look for the Currencies or Payment Channels section. You will see a list of currencies that are enabled for your account. Some may have toggle switches, others may show "Contact support to enable".

2. Test with the API

The quickest way to test is to initialize a small transaction in the currency you want to verify:

// Test if KES is enabled on your account
const response = await fetch('https://api.paystack.co/transaction/initialize', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.PAYSTACK_SECRET_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    email: 'test@example.com',
    amount: 10000,
    currency: 'KES',
  }),
});

const data = await response.json();
console.log(data);
// If KES is not enabled: { status: false, message: "Currency not supported" }
// If KES is enabled: { status: true, data: { authorization_url: "...", ... } }

Run this in test mode with your test secret key. If the currency is supported, you will get an authorization URL. If not, you will get the error message.

Follow this checklist:

1. Confirm your currency code is correct. It must be an uppercase three-letter ISO 4217 code: "NGN", "GHS", "ZAR", "KES", or "USD". Trim whitespace and convert to uppercase in your code.
2. Check your Paystack dashboard for enabled currencies. If the currency you need is not listed, enable it if there is a toggle, or contact Paystack support to request activation.
3. Verify both test and live modes. Enable the currency in both modes if you need it in both.
4. For multi-country support, consider separate accounts. If you need to accept KES and NGN, you may need a Kenyan account for KES and a Nigerian account for NGN. Use the appropriate secret key for each currency.
5. Always specify the currency explicitly. Do not rely on the default. Make your code explicit about which currency it is charging in.

Here is a server-side validation function that catches currency issues before calling Paystack:

const SUPPORTED_CURRENCIES = ['NGN', 'GHS', 'ZAR', 'KES', 'USD'] as const;
type SupportedCurrency = typeof SUPPORTED_CURRENCIES[number];

function validateCurrency(currency: string): SupportedCurrency {
  const normalized = currency.trim().toUpperCase();

  if (!SUPPORTED_CURRENCIES.includes(normalized as SupportedCurrency)) {
    throw new Error(
      `Currency "${currency}" is not supported. Supported currencies: ${SUPPORTED_CURRENCIES.join(', ')}`
    );
  }

  return normalized as SupportedCurrency;
}

// Map each currency to its Paystack secret key (for multi-country setups)
const PAYSTACK_KEYS: Record = {
  NGN: process.env.PAYSTACK_SECRET_KEY_NG!,
  KES: process.env.PAYSTACK_SECRET_KEY_KE!,
  GHS: process.env.PAYSTACK_SECRET_KEY_GH!,
  ZAR: process.env.PAYSTACK_SECRET_KEY_ZA!,
};

function getPaystackKeyForCurrency(currency: SupportedCurrency): string {
  const key = PAYSTACK_KEYS[currency];
  if (!key) {
    throw new Error(`No Paystack key configured for currency ${currency}`);
  }
  return key;
}

If your application serves customers in multiple countries, you need a pattern for selecting the right currency and Paystack account. Here is a clean approach:

interface PaymentConfig {
  secretKey: string;
  currency: string;
  minimumAmount: number; // in minor units
}

const PAYMENT_CONFIGS: Record = {
  NG: {
    secretKey: process.env.PAYSTACK_SECRET_KEY_NG!,
    currency: 'NGN',
    minimumAmount: 10000,
  },
  KE: {
    secretKey: process.env.PAYSTACK_SECRET_KEY_KE!,
    currency: 'KES',
    minimumAmount: 100,
  },
  GH: {
    secretKey: process.env.PAYSTACK_SECRET_KEY_GH!,
    currency: 'GHS',
    minimumAmount: 100,
  },
  ZA: {
    secretKey: process.env.PAYSTACK_SECRET_KEY_ZA!,
    currency: 'ZAR',
    minimumAmount: 100,
  },
};

async function initializePayment(
  email: string,
  amountInMinorUnit: number,
  countryCode: string
) {
  const config = PAYMENT_CONFIGS[countryCode];

  if (!config) {
    throw new Error(`Payments not available in country: ${countryCode}`);
  }

  if (amountInMinorUnit < config.minimumAmount) {
    throw new Error(
      'Amount below minimum for ' + config.currency + '. ' +
      'Minimum: ' + (config.minimumAmount / 100) + ' ' + config.currency
    );
  }

  const response = await fetch('https://api.paystack.co/transaction/initialize', {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${config.secretKey}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      email,
      amount: amountInMinorUnit,
      currency: config.currency,
    }),
  });

  return response.json();
}

The country code can come from the user's profile, their IP address (via a geolocation service), or a manual selection on your checkout page. Use whatever makes sense for your product.

USD is a special case. Most Paystack accounts do not have USD enabled by default. To accept USD:

1. Your business must be fully verified on Paystack (KYC complete)
2. Contact Paystack support and request USD currency activation
3. Paystack may require additional documentation depending on your business type
4. Once approved, USD will appear as an available currency in your dashboard

When you charge in USD, Paystack handles the conversion and settles to your local account in your default currency. The settlement amount will reflect the exchange rate at the time of settlement, not at the time of charge. This means there is exchange rate risk between the charge and settlement dates.

If you are accepting USD from international customers, make sure your checkout clearly displays prices in USD and confirms the currency before the customer pays. Accidentally charging someone in NGN when they expected USD (or vice versa) is a quick way to get chargebacks.

After fixing the error:

1. Test with your default currency. Initialize a transaction with your account's primary currency (e.g., NGN for Nigerian accounts). Confirm it succeeds.
2. Test with a non-default currency you have enabled. If you enabled USD, initialize a transaction with currency: "USD". Confirm it succeeds.
3. Test with a currency you have NOT enabled. Send a currency your account does not support. Confirm you get the "Currency not supported" error. Verify your server-side validation catches it before the API call.
4. Test with malformed currency codes. Send lowercase "ngn", send "Naira", send an empty string. Confirm your validation normalizes or rejects these.
5. Test both test and live modes. Verify the currencies are enabled in both environments.
6. For multi-account setups, verify key routing. Confirm that KES transactions use the Kenyan account key and NGN transactions use the Nigerian account key.

For related amount errors, see Paystack Amount Too Low Error and Paystack Invalid Amount Error and Kobo Confusion. For the complete error reference, see Paystack Errors and Troubleshooting: The Complete Reference.