foxhound
Sign in

Decline code

Currency Not Supported

Stripe declined this payment because the card cannot be charged in the currency the transaction was submitted in. This is a currency-mismatch problem, not a problem with the card's balance, status, or standing. Stripe's official definition is: "the card doesn't support the specified currency." Some cards, particularly certain prepaid, debit, or region-restricted cards, are only able to process transactions in specific currencies, often just the cardholder's home currency. If a charge is submitted in a currency the card isn't set up to handle, the issuing bank rejects it outright, regardless of available balance or the card's standing.

Back to decline codes
currency_not_supportedNo automatic retry
Draft content: this page's explanatory copy is Pass 3 template writing pending a dedicated content pass. The classification badge above and the recovery behavior described below are live, not draft: both come directly from the recovery engine.

Why it happens

This shows up most often when a business changes its billing currency, expands into a new region, or when a customer's card was issued in a country whose currency differs from the currency the subscription is billed in. It can also appear after a customer's card was reissued (a replacement after expiration or a security event) with a narrower set of supported currencies than the original card had. The card itself may be perfectly valid and funded. It just isn't configured for this particular currency.

How to fix it

Not usefully in the same currency. Retrying the identical charge, in the identical currency, against the identical card will produce the identical decline every time, since nothing about the retry changes the fundamental mismatch. If your billing system supports multiple settlement currencies, the most direct fix is offering the customer a way to pay in a currency their card does support. If you bill in a single currency only, the practical options are asking the customer for a different card that does support your billing currency, since a same-currency retry cannot fix a currency mismatch. This is worth flagging to a human on your team too, since a cluster of this code appearing together can indicate a business is undercharging or overcharging customers by billing in the wrong currency for a given market, not just an issue on any one customer's card.

How Foxhound recovers it

This code has no dedicated bucket in the recovery engine's classification sets, so it fails closed rather than defaulting to a silent retry: no repeat charge runs against a code Foxhound cannot classify. Recovery goes straight to the same email sequence expired cards get, carrying the hosted card-update link, until this code earns its own bucket.

Questions

  • No. It has nothing to do with balance. The card simply isn't configured to process charges in the currency the transaction was submitted in.

  • No, not in the same currency. The mismatch between the card and the billing currency doesn't change with time or repeated attempts.

  • Either bill the customer in a currency their card supports, if your system allows multiple settlement currencies, or ask them for a different card that does support your billing currency.

  • No. Foxhound's classifier has no named case for `currency_not_supported`, so it falls to the unknown bucket, which fails closed rather than retrying: no automatic retry runs, and recovery goes straight to a card-update email instead, a coarse fit for a currency mismatch but one that at least prompts a human look at the account.

  • Worth a look. A cluster can point to a broader currency-support issue in a particular market or a recent card-reissuance pattern among your customer base, not just isolated individual card problems.

See what this looks like on your account

The free audit shows what Stripe already recovered and what is still dying, no signup required.

Run your free audit