What Does Code 02: Refer to Issuer Special Condition Mean?
The credit card decline code “02: Refer to issuer (special condition)” indicates that the transaction cannot be processed and that the merchant should contact the card issuer for further information. This code generally suggests that there may be a special condition or an issue with the cardholder’s account that needs to be addressed directly by the bank or card issuer. The issuer may need to verify the cardholder’s identity, check for security concerns, or resolve an account status issue before the transaction can be authorized. This code is a protective measure to prevent fraudulent transactions and ensure the security of the cardholder’s account.
Key Takeaways
- Code 02 is an issuer-side decline.
- It is close to Code 01, but the issuer is flagging a special condition.
- The merchant usually cannot override it.
- Ask the customer to call the number on the back of the card or use another payment method.
- If Code 02 appears repeatedly across many customers, review fraud rules, transaction patterns, and processor reporting.
Code 02 is the bank saying, “Stop here. We need to talk to the cardholder.” It is not a clean approval problem and it is not a simple terminal error.
For merchants, the best response is calm, practical, and well documented: do not force the sale, do not guess the reason, and give the customer a clear next step.
What Code 02 Means in Plain English
Every card sale has to pass the issuing bank’s decision layer. That bank looks at the card account, recent activity, risk rules, cardholder controls, and the details of the purchase.
With Decline Code 02, the issuer is not giving the merchant a full explanation. It is saying the transaction has a special condition that must be handled by the issuer and the cardholder.
That condition might be identity verification, unusual account activity, a temporary card block, a travel or location alert, a risk review, or another account-level concern.
Common Reasons Code 02 Happens
Code 02 does not tell the merchant the full bank reason. It gives enough information to act carefully.
- Issuer wants to verify the cardholder’s identity
- Unusual activity or spending pattern
- Large purchase outside the customer’s normal behavior
- Cross-border or travel-related concern
- Temporary account restriction
- Cardholder-set controls or banking-app limits
- Recent address, device, or account change
- Possible fraud alert that needs customer confirmation
- Issuer needs the customer to approve the purchase
- Account status issue that only the bank can explain
The important point: Code 02 is not the same as insufficient funds. It also is not proof of fraud. It means the issuer is holding the decision until the customer resolves the condition.
What the Merchant Should Do
Handle Code 02 like a bank-required pause, not a routine failed payment.
- Do not keep retrying the same card. Repeated attempts may make the payment look riskier.
- Tell the customer the issuer declined the transaction. Keep the message neutral and professional.
- Ask the customer to call the issuing bank. The number on the back of the card is usually the right place to start.
- Offer another payment method. A different card, ACH, wire, or approved alternate method may save the sale.
- Record the decline details. Keep the date, amount, card brand, channel, and response code.
- Escalate patterns. If Code 02 appears often, ask your processor to review authorization data and risk signals.
What Not To Do
Code 02 can be vague, which makes it easy for staff to say the wrong thing at checkout.
- Do not tell the customer they have no money.
- Do not accuse the customer of fraud.
- Do not keep entering the card over and over.
- Do not ask the customer to share private bank details.
- Do not ignore a cluster of Code 02 declines.
- Do not treat Code 02 the same as a gateway rejection.
The bank owns the final reason. The merchant’s job is to keep the customer informed, protect the business, and avoid repeat attempts that add risk.
When Merchants Should Look Deeper
One Code 02 decline may be a normal issuer decision. A pattern is worth investigating.
- High-ticket or unusual order amounts
- International or cross-border payments
- Subscription rebills
- MOTO or manually keyed transactions
- New checkout, gateway, or processor setup
- Many attempts from the same cardholder
- Orders from new devices or unfamiliar IP locations
- A specific issuer, card brand, country, or BIN range
- Sudden traffic spikes or promotional campaigns
- High-risk product categories or delivery delays
Repeated Code 02 declines can point to a mismatch between issuer risk controls and the way the merchant is processing, describing, or routing transactions.
How Durango Merchant Services Can Help
Durango Merchant Services helps merchants read decline codes as business intelligence, not just technical noise.
For high-risk, ecommerce, MOTO, subscription, nutraceutical, travel, large-ticket, and cross-border merchants, Code 02 may signal approval friction, issuer discomfort, weak payment presentation, or transaction patterns that need review.
The fix may involve cleaner descriptors, better fraud controls, more payment options, improved gateway setup, or a processor better suited to your business model.
If Code 02 keeps showing up in your reports, contact Durango Merchant Services. We can help you review the pattern, protect good sales, and reduce avoidable payment friction.
FAQs For Decline Code 02
It means the issuing bank declined the transaction because of a special condition on the card or account. The cardholder should contact the issuer for the specific reason.
No. Code 02 is an issuer-side special-condition decline. It does not automatically mean the customer lacks funds.
Do not keep retrying the same card. Ask the customer to contact their issuer or use another payment method. If the issuer clears the issue, start a clean new attempt.
Investigate when Code 02 appears repeatedly across many customers, specific issuers, countries, card brands, payment channels, or high-ticket orders.