What Are Card Decline Codes?
Whenever a customer’s card payment is declined, the issuing bank or network provides a decline code. Think of it as a reason code—a short message that explains why the transaction didn’t work.
There are three main categories:
- ISO Standard Codes – universal, long-standing codes used by banks worldwide.
- Handling Errors – merchant-friendly explanations and error messages that Dibsy provides.
- Network Codes – detailed issuer/network responses (common in bank transfers or mandates).
ISO Decline Codes: The Classics
ISO codes are numeric, usually 2-digit, and still widely used. Here are some of the most common ones:
| Code | Meaning | What it means for merchants |
|---|---|---|
| 05 | Do not honor | Bank blocked the transaction—customer must call their bank |
| 51 | Insufficient funds | Customer’s balance is too low |
| 54 | Expired card | Card has expired—ask for updated card |
| 57 | Transaction not permitted | Card blocked for this type of payment |
| 62 | Restricted card | Region or merchant restriction applies |
| 65 | Exceeds withdrawal limit | Daily or monthly card limit reached |
In Qatar, codes like 57 (not permitted) or 62 (restricted) often occur if a local card isn’t enabled for eCommerce or international use.
Handling Errors (Dibsy Version)
When processing payments, several errors can occur that are outside of your or Dibsy's control. For example, the customer may have insufficient funds in their card, or the issuing bank may decline the transaction.
In order to provide a great user experience, handling errors is extremely important. If a transaction fails, you must handle it gracefully by informing the customer of the error so they can correct the problem and complete the checkout.
Here’s a list of failure reasons and recommended failure messages you can display:
| Failure Reason | Failure Message |
|---|---|
| unknown_reason | The card has been declined for an unknown reason. Please try a different card or another payment method. |
| naps_card_not_permitted | The NAPS card is not permitted for this type of transaction. Please use the “Debit card” option. |
| invalid_cvv | The CVV provided does not match the information on file with the cardholder's bank. Please try again or contact your bank. |
| ip_not_permitted | The transaction was made while connected to a VPN, using a proxy, or from an unusual IP address. Please turn off proxies and try again. |
| refused_by_issuer | The customer's card issuing bank has declined the transaction. Please use a different card or another payment method. |
| insufficient_funds | There is an insufficient balance in your bank account. Please use a different card or another payment method. |
| card_expired | The card is expired. Please use a different card or another payment method. |
| invalid_card_number | The customer's card issuing bank is unable to validate the card number. Please try a different card or another payment method. |
| possible_fraud | The card issuer indicated a security issue with this card (suspected fraud or stolen). If you believe this to be an error, please contact your bank. |
| card_declined | The card has exceeded the withdrawal limit. Please use a different card or another payment method. |
| authentication_failed | The card authentication has failed. Please check your card details and try again. |
These error messages allow merchants to provide clear, actionable feedback instead of a confusing “payment failed.”
Network Decline Codes
- R01 – Insufficient funds
- R02 – Account closed
- R03 / R04 – Invalid account details
- R16 – Account frozen
- R20 – Bank blocked the account
As Qatar moves toward open banking and direct bank transfers, these codes will become more relevant.
Why Decline Codes Matter in Qatar
- Lost Revenue – Failed payments mean fewer completed sales.
- Customer Frustration – Shoppers may abandon purchases.
- Operational Overhead – More support requests, more time lost.
In Qatar specifically:
- QAR Support – Some international cards don’t support QAR payments.
- 3D Secure Enforcement – Authentication is stricter than in some regions.
- Local Issuer Rules – Banks may decline transactions until the customer approves them.
How Dibsy Helps Reduce Declines
- ✅ Local Settlement in QAR – Direct settlement into local bank accounts.
- ✅ 3D Secure 2 Support – Seamless authentication for Qatar banks.
- ✅ Clearer Messaging – Merchant-friendly decline explanations.
- ✅ Local Support – On-the-ground assistance to resolve bank issues quickly.
Want to see how this ties into overall compliance? Read our Guide on PCI DSS in Qatar.
Best Practices for Merchants
- Show Clear Messages – Tell customers why the payment failed.
- Retry Smartly – Some declines are temporary (“soft declines”).
- Offer Alternatives – Add Apple Pay, Google Pay, and bank transfers. See: Why Apple Pay Is Dominating in Qatar.
- Educate Customers – Many don’t know their cards need activation for eCommerce.
- Use Dibsy’s Dashboard – Spot decline patterns and take action.
FAQs: Decline Codes in Qatar
1. Why do I keep seeing “Do Not Honor” in Qatar?
This is a common decline when banks don’t share the real reason. The customer must contact their bank. Encourage them to try another card or payment method in the meantime.
2. Can expired cards still be retried?
No. If you see card_expired or ISO 54, the customer needs to update their card details.
3. Why does “Authentication Failed” happen so often here?
Because Qatari banks enforce 3D Secure for security. It’s a good thing—it protects both merchants and customers.
4. What does “Currency Not Supported” mean?
Some cards can’t process QAR transactions. Offering multi-currency support or alternative payment methods (Apple Pay, Google Pay) helps.
5. Are declines higher in Qatar than elsewhere?
They can be. Factors like 3D Secure enforcement, card restrictions, and limited international enablement make declines more common—but with Dibsy, you can reduce them significantly.
For more troubleshooting tips, check out our Guide to Chargebacks in Qatar.
Final Thoughts
Card declines are part of payments everywhere, but Qatar has its own challenges: currency restrictions, bank rules, and authentication requirements.
By understanding decline codes—and working with a local partner like Dibsy—you can turn failed payments into completed sales, reduce friction for your customers, and grow with confidence.
Because your business deserves to focus on growth, not error codes.
👉 Ready to reduce declines and increase successful transactions? Talk to Dibsy today.
.webp){kind=spacer}
