Why a Card Payment Gets Declined: Soft vs Hard Declines

A card payment gets declined when the customer's bank, or another party in the payment chain, refuses to approve it. A decline is either soft or hard. A soft decline is temporary, so a retry may work. A hard decline will not change, so the customer needs another card or another way to pay.
- Soft decline: a temporary refusal. The same card may be approved later.
- Hard decline: a permanent refusal for that card in that situation. Retrying does not help.
- Decline code: a short code returned with the refusal. It is the best clue to which kind you are dealing with.
This guide is the written companion to our short video on the same topic.
What is a soft decline?
A soft decline is a refusal that may not last. The bank has not said the card is unusable. It has said "not this time". Common soft causes are a temporary problem at the bank, a payment that needs an extra identity check, or a limit that has been reached for now.
A retry can make sense for a soft decline, but do not retry in a tight loop. Repeated attempts can look suspicious to a bank and can annoy the customer. Check your provider's guidance on how many retries are allowed and how far apart they should be.
What is a hard decline?
A hard decline means the bank will not approve this card for this payment, and asking again will not change the answer. Typical causes are a card that is closed or reported lost, or details that cannot be right.
For a hard decline, the practical step is to ask the customer for another card or another payment method. A clear message at checkout, such as "please try a different card", saves a support conversation.
How do you tell a soft decline from a hard one?
Read the decline code. Your payment provider returns a code or a short reason with the refusal, and its documentation says which codes are temporary and which are permanent. The exact codes differ between providers, so use your provider's list rather than a generic one.
Log the code with every failed payment. Over time this shows you whether declines are mostly temporary or permanent, and whether a particular step in your checkout is causing them. Our payment integration testing checklist includes testing declines and failures before you go live.
Where does a decline happen in the payment chain?
A decline can come from the customer's bank or from another party that checks the payment. To see the full path of a payment, read how a card payment moves. A decline happens at the authorization step, before any money is captured, which is explained in authorization, capture and settlement.
Some payments are declined only because the bank asked for an extra identity check that did not complete. Our guide to 3-D Secure explains that step.
What should a merchant show the customer after a decline?
Show a plain, calm message that says what to do next. Do not blame the customer, and do not repeat the bank's internal wording. Offer a clear way to try again or to use another method, and keep the cart so nothing has to be re-entered.
A decline is not a chargeback. A chargeback starts later, when a customer disputes a payment that was approved. See what a chargeback is and how it works.
FAQ
What is the difference between a soft and a hard decline?
A soft decline is temporary, so the same card may be approved later or after a small change. A hard decline is permanent for that card in that situation, so the customer needs another card or another way to pay.
Should I retry a declined payment?
Only for a soft decline, and not in a tight loop. Follow your provider's retry guidance, and do not retry a hard decline.
Where do I find the decline code?
Your payment provider returns it with the failed payment. Check your provider's dashboard or API response, and store the code with the order so you can review patterns later.
Is a decline the same as a chargeback?
No. A decline happens before a payment is approved. A chargeback happens afterwards, when a customer disputes an approved payment.
Can EPaySe tell me why a specific payment was declined?
EPaySe is a payment gateway in development for high-risk and regulated businesses, reviewed and approved case by case. What is available to a merchant depends on the review and the setup.
Related Articles

What Is a Rolling Reserve? How Held Funds Work for Merchants
A rolling reserve is a share of a merchant's sales that a payment provider may hold back and release later. See how it works and what to check in your terms.

Payment Webhooks Explained: Why Your Order Says Pending
A payment webhook is a message your payment provider sends to your server when something happens. Learn why orders stay pending and how to confirm a payment safely.

Idempotency Keys: How to Prevent Double Charges
An idempotency key lets a payment system recognise a repeated request as the same attempt. Learn how it helps prevent double charges when a customer taps pay twice.

Payment Gateway vs Processor vs Acquirer: Who Does What
A payment gateway, a processor and an acquirer each handle a different step of a card payment. See who does what, in plain words, and why the roles are sometimes bundled.