A client tries to fund an account with a card that works everywhere else. The checkout returns a failure. They try again, twice, then message support saying the platform is broken. Somewhere behind that screen an issuing bank in another country made a decision in under two seconds and returned a code that the client will never see and that support usually cannot interpret.
Almost every payment failure falls into one of three places: the issuer refused it, the acquirer or gateway refused it before it left, or the transaction never reached a decision because something in the chain timed out. Those three have completely different remedies.
Soft, hard, and the one that pretends to be neither
A hard decline is final. The card number is wrong, the account is closed, the card is reported lost or stolen, the card has expired. Retrying accomplishes nothing except adding a failed attempt to a ratio that acquirers watch, and repeated attempts against a stolen card look exactly like card testing.
A soft decline is a refusal to approve this attempt. Insufficient funds, a velocity limit hit, an issuer system unavailable, a temporary fraud hold. Try again later, with the emphasis on later.
Then there is do not honour, the code that dominates every merchant's decline report and explains nothing. It is the issuer's polite refusal, and it can sit on top of a fraud score, a country restriction, a merchant category block or a hold nobody outside the bank can see. Treating it as a technical fault wastes support hours. The only path that reliably works is the customer calling their own bank.
| Response | What the issuer means | What to do |
|---|---|---|
| Do not honour | Refused, reason not disclosed | One retry at most, then ask the client to call their bank |
| Insufficient funds | Balance or credit limit will not cover it | Retry after a delay, or offer a smaller amount |
| Transaction not permitted to cardholder | The card or account is blocked for this type of purchase | Offer a different rail, the card will not work for this category |
| Exceeds withdrawal limit or frequency | Per transaction, daily or count limit reached | Retry tomorrow or split the deposit |
| Issuer unavailable, system error | Nothing was decided | Retry shortly, this one is genuinely temporary |
| Soft decline, authentication required | The issuer wants the cardholder challenged | Resubmit through 3D Secure, do not treat it as a refusal |
That last row costs firms more revenue than any other, because a soft decline for authentication is not a refusal at all. The issuer is asking for a challenge. Payment stacks that treat it as a failed payment and show an error page throw away transactions the bank was willing to approve. The handling is part of the wider 3D Secure 2 flow.
Why trading firms get declined more than shops do
Two structural reasons, neither of which is about the individual client. The first is the merchant category code. Financial services and quasi-cash categories carry stricter treatment inside issuer risk models, and some banks block them outright for consumer cards. A deposit to a trading account is closer, in the issuer's classification, to buying foreign currency than to buying a jacket, and it can even be treated as a cash advance by the cardholder's own bank with its own fee.
The second is the transaction profile. Cross border, higher than average ticket size, sometimes a first transaction from a new customer at an unfamiliar merchant. That combination scores badly wherever fraud models are strict, which is one of the reasons acquirers put trading firms in the high risk merchant bucket in the first place.
A decline rate is a portfolio number, not a customer number. Segment it by issuer country, card brand, amount band and device before drawing conclusions. One issuing bank in one country will often account for a third of a firm's failures, and that is a routing problem with a fix.
The fixes that move the number
Local acquiring is the strongest lever. Issuers approve domestic transactions at a higher rate than cross border ones, so acquiring in the client's region converts a foreign transaction into a local one and the card mismatch effects described in the piece on BIN country mismatches largely disappear.
Data quality is next and costs nothing. Send the full address, a valid email, the correct currency and complete authentication data. Many declines are risk scores nudged over a threshold by a missing field.
Then routing. If a firm has more than one acquirer, failed transactions can be reattempted through a different one, subject to the retry rules above. This is where a decline report earns its keep, since the routing rule should be built from the segments that actually fail rather than from a vendor's default. The full picture of what drives acceptance is in the guide to payment approval rates.
Finally, alternatives. When a category block is the cause, no amount of retrying helps, because the client's bank has decided that this type of merchant is not eligible for that card. Bank transfer, local payment methods and e-wallets recover clients that cards never will, and offering them at the moment of failure recovers far more than an email sent the next day.
What support should say
Not that the payment failed for technical reasons, because that is usually untrue and it sends the client back to retry the same card. Tell them what the response indicated in plain language, offer a specific alternative, and make it clear the firm never sees why their bank refused. On subscription style renewals the same principle applies, with the added discipline of the retry schedule set out in the guide to recurring billing.
Log the code, the acquirer, the BIN, the amount and the outcome on every attempt. Without that record the monthly decline conversation with a provider is an exchange of opinions. With it, you can point at one issuer, one country, one amount band, and ask a question that has an answer.
"Support will tell you the payment page is broken. The logs will tell you one bank in one country refuses your merchant category. Those are not the same problem and only one of them is fixable by you."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Hard declines must never be retried, soft declines can be retried on a schedule spread over days.
- An authentication soft decline is a request for a challenge, not a refusal, and is often mishandled.
- Merchant category treatment and cross border profile explain most of a trading firm's decline gap.
- Segment declines by issuer country and amount band before changing anything in the stack.
Frequently Asked Questions
What does the do not honour decline actually mean?
It is the issuer's generic refusal. The bank has decided not to approve the transaction and is not obliged to say why, so it covers everything from a fraud model score to a country block to a temporary hold on the account. The only reliable resolution is for the cardholder to contact their own bank.
How many times should a declined payment be retried?
It depends on the code. Hard declines such as an invalid card number, a closed account or a stolen card should never be retried, because the answer will not change and excessive retries count against the merchant. Soft declines such as insufficient funds or an issuer timeout can be retried a small number of times, spaced over days rather than minutes.
Why do brokers and trading firms see more declines than other merchants?
Partly the merchant category code, since financial and quasi-cash categories attract stricter issuer treatment and are sometimes blocked outright by the cardholder's bank. Partly the transaction profile: cross border, higher average value and funding rather than purchase, which is exactly the pattern fraud models are tuned to distrust.