Currency not supported — The card can't pay in the charged currency.
Customer's card is regional and your charge is in a currency the issuer doesn't process.
| Retry strategy | Don't retry |
|---|---|
| Customer-facing action | Offer an alternative payment method |
| Recovery rate (retry only) | ~5% |
| Recovery rate (with customer flow) | ~40% |
Retries won't fix currency mismatch. Offer the customer a regional payment method (e.g. SEPA, iDEAL, or local cards via a Stripe Connect account).
The recommended Stripe Customer Portal session for the recovery flow:
session = stripe.billing_portal.Session.create(
customer=customer_id,
return_url="https://yourapp.com/billing/thanks",
flow_data={"type": "payment_method_update"},
)
update_link = session.url
currency_not_supported is one of dozens of decline codes Stripe returns; recovery rates vary by code by 5x or more. The recovery-rate reference covers the full set; the card-update flow article covers the customer-facing side; dunning emails covers how to write the messages.
DunningKit's open-source CLI parses your Stripe failed-charges CSV and gives you the breakdown by code, with recoverable-revenue estimates. pip install dunningkit.