A decline is a negative answer to an authorization request: the merchant asks the card issuer through its acquiring bank whether an amount can be held, and the issuer says no. The decision takes seconds and comes back as a response code, not as an explanation. Below is how that chain works and which checks to run, from the most common causes to the rare ones.
How a decline happens
Five checks in order of frequency
Who actually declined the payment
Four parties take part in an authorization: the merchant's site and its fraud screening, the payment gateway, the acquiring bank and the card issuer. A refusal can come from any of them, and the on-screen message is usually identical. If the request never reached the bank — the form rejected the details, the merchant's risk rules fired, a geo filter blocked it — the issuer never sees that attempt at all. If it did reach the bank, the issuer forms the answer: it sees the balance, the limits and the transaction parameters. Knowing where the chain broke saves time, because some causes sit with the card and others entirely with the merchant.
What «card declined» actually means
The generic phrase usually stands for code 05 (Do not honor) — a catch-all issuer refusal that reveals no reason. It is uninformative by design: networks do not pass the issuer's reasoning to the merchant, so that response codes cannot be used to probe for parameters that go through. Some codes do speak: 51 (insufficient funds), 54 (expired card), 14 (invalid number), 57 (transaction not permitted for this card), 65 (activity limit exceeded). If the merchant shows a code, start there. If it shows only generic text, work through the checks below.
Step 1. Available balance and holds
A prepaid card authorizes a transaction when the available balance covers the full requested amount. The headroom is not only for the price: a cross-border or conversion fee may sit on top, and some merchants run a verification authorization when a card is added — a small hold that is released later but reduces the available balance until then. Abandoned attempts leave holds too, reserving the amount until the authorization expires. Check not «how much is on the card» but «how much is available right now», and keep headroom above the checkout total.
Step 2. Card details and billing profile
Mismatched data is the second most common cause. Verify the number, expiry month and year, CVC, cardholder name and billing address: they must match the card's own record, not your home address or the delivery address. Formatting matters as well — postcode, country and state are entered exactly as they are held for the card. Many merchants check the address through AVS and decline on a mismatch. Browser autofill tends to hurt here rather than help, because it inserts a previous profile.
Step 3. 3-D Secure confirmation
When a transaction goes through 3-D Secure, the confirmation step is part of the authorization. An unfinished challenge — the window was closed, the session timed out, the one-time code never arrived — ends the transaction as a refusal even when the funds are fine. In the EEA and the UK strong customer authentication is required by regulation, so cards in EUR and GBP meet this step more often. Make sure the pop-up is not blocked by the browser and that you can reach the confirmation channel for that card.
Step 4. Currency and cross-border fees
If the checkout currency differs from the card currency, the authorization amount is converted at the payment network's rate, and the issuer may add a conversion fee or a cross-border fee. The request that reaches the issuer is therefore larger than the price on the page — and with an exact balance it hits the ceiling. A separate case is DCC, where the merchant offers to charge in your card's currency at its own rate. Match the card currency to the checkout currency in advance: cards are issued in USD, EUR and GBP on a single USD balance.
Step 5. Merchant category and card rules
Every merchant carries a category code (MCC), and a card product may treat categories differently: some are processed under different rules, others are not supported at all. That answer is about a class of transactions rather than one shop, which is why the same merchant can behave differently across regions. Velocity rules belong here too: a burst of rapid attempts raises the risk score and makes the next refusal more likely.
What to do after a decline
Do not retry the payment back to back: every attempt leaves a trace in risk scoring and may leave a hold behind. Fix the discrepancy first — top the card up with headroom, correct the billing profile, complete the confirmation — and only then retry. If the refusal happens while adding a card and no response code is shown, a small-amount transaction is a useful probe: it separates an available-balance problem from a details problem. The issuer's reason is never disclosed to the merchant, so the working method is to close off the checkable causes one by one.
Frequently asked questions
Why does the merchant not tell me the real reason?
Code 05 (Do not honor) withholds the reason deliberately: networks do not pass the issuer's decision details to the merchant, so responses cannot be used to probe for parameters that pass. The merchant sees exactly the same uninformative answer you do.
There is money on the card, so why does the payment fail?
A balance matching the price does not guarantee authorization: holds from earlier attempts, a verification authorization at card linking, conversion and cross-border fees all reduce the available balance. Look at the available amount and keep headroom above the checkout total.
How many times can I retry a payment?
Retrying makes sense only after you change something: topping the card up, correcting the billing address, completing the confirmation step. A run of identical attempts raises the transaction's risk score and leaves holds behind, so it works against you.
Does a decline depend on the card BIN?
The BIN identifies the issuer, the network, the card type and its region — part of the data an authorization decision is based on. That is why different BINs are chosen for different tasks, but the outcome of a given transaction also depends on the amount, the currency, the merchant category and the merchant's own rules.
How quickly is a hold from a failed attempt released?
A hold stays until it is cleared or until the authorization expires — a rule set by the issuer and the network, with the period depending on the transaction type. Until then the reserved amount reduces the available balance, so a card needs headroom after a series of attempts.