Currency Mismatch Decline
A currency mismatch decline occurs when the transaction currency is not supported by the cardholder's account or the issuing bank doesn't allow transactions in that currency. This is less common than other decline types but particularly relevant for SaaS businesses with international customers. The card itself may be perfectly valid, but the bank won't process a charge in a currency it doesn't handle. Recovery requires either adjusting the charge currency or having the customer provide an alternative payment method.
Affected Percentage
~2% of all declines
Recovery Rate
60-70% with outreach
Recommended Action
Do not retry
Common Causes
Card doesn't support the charge currency
Some debit cards and prepaid cards are restricted to the issuing country's currency. A USD charge on a card that only supports EUR will be declined.
Bank blocks foreign currency transactions
Certain banks, particularly in emerging markets, block foreign currency charges by default. The customer may need to enable international transactions with their bank.
Multi-currency processing not enabled
Your payment processor account may not be configured for multi-currency processing, causing all charges to be sent in your base currency regardless of the customer's location.
Incorrect currency code in transaction
A technical error where the wrong ISO 4217 currency code is sent with the transaction (e.g., sending GPB instead of GBP).
Recommended Retry Strategy
Timing
Do not retry in the same currency. Either convert to the customer's local currency and retry, or contact the customer to provide an alternative payment method.
Max Retries
1 retry in corrected currency, otherwise outreach
Reasoning
Retrying the same charge in the same unsupported currency will always fail. The solution is to change the currency (if your system supports it) or get the customer to use a card that accepts the transaction currency.
Best Practices
- 1
Implement multi-currency pricing that charges customers in their local currency, reducing mismatch issues.
- 2
Detect the customer's card country from BIN data and route to the appropriate currency before the first charge.
- 3
If a currency mismatch occurs, email the customer explaining the issue and offer to charge in their local currency or accept an alternative payment method.
- 4
Support alternative payment methods popular in international markets (SEPA for Europe, PIX for Brazil, UPI for India) as fallbacks.
- 5
Review your payment processor's currency support list and ensure it covers all your customer geographies.
How Rezoki Handles This Automatically
Rezoki detects currency mismatch declines and cross-references the customer's card BIN data with the charged currency. If the workspace supports multi-currency billing, Rezoki automatically retries the charge in the customer's likely local currency. If multi-currency isn't available, Rezoki sends a targeted email explaining the issue in clear terms and offering alternative payment options. For markets where currency restrictions are common, Rezoki proactively recommends enabling local payment methods to prevent these declines in the first place.