Soft Decline

A soft decline is a refusal of a card authorization for a reason that is temporary or can be fixed, so the same card may be approved later or on a second attempt with more information. Insufficient funds, an issuer's system being briefly unavailable, a card hitting a daily spending limit and a request for stronger authentication are the usual causes. The issuing bank signals this with a response code in its reply to the authorization request.

"Soft decline" is an industry working term rather than a code defined by the networks, and it is used in contrast with a hard decline, where the card will not be approved however often the merchant tries. The split matters because it decides what the merchant should do next: retry, ask for authentication or a different card, or stop. Both are kinds of payment decline, and the networks' own decline categories map onto the same idea.

Imagine knocking on a friend's door and hearing "not now, come back in an hour" or "who is it? Show me your face at the window". That is a soft decline. The answer is no for the moment, but there is a way to get a yes: wait, or prove who you are.

A hard decline is more like finding the house empty and sold. Knocking again will not help. For a shop taking card payments, telling these apart is useful. A soft decline on a subscription renewal may clear if the shop tries again after payday. A soft decline asking for identity checks clears once the shopper confirms on their banking app. Knocking at the wrong time, or too often, just annoys the household.

Issuers reply using response codes based on the ISO 8583 message standard, and networks add their own. Codes treated as soft include:

• Insufficient funds (51). The account or credit line cannot cover the amount right now. Retrying after a few days, or for a smaller amount where permitted, often succeeds.
• Issuer or switch unavailable (91, 96). A technical failure at the issuer or along the route. A retry minutes later, or through another route with payment failover, usually works.
• Exceeds limit (61, 65). A daily amount or frequency limit has been reached. In Europe, Mastercard also uses code 65 to request strong authentication.
• Authentication required (Visa 1A). Under strong customer authentication rules, the issuer refuses a payment sent without authentication and asks for it to be resubmitted after 3-D Secure.
• Do not honour (05). A generic refusal with no stated reason. It is often treated as soft, though some issuers use it for refusals that are effectively final.

Because soft declines invite a second attempt, the networks limit how often merchants may retry, to stop automated systems hammering issuers. Visa groups decline codes into categories, from "issuer will never approve" to "issuer cannot approve at this time" and data-quality problems, and charges fees for retrying beyond set limits. Acquirer notices state that from May 2025 Visa allows up to 20 reattempts for the same card and merchant within a rolling 30 days, up from 15. Mastercard returns merchant advice codes alongside many declines, telling the merchant whether and when to retry, and charges for attempts that ignore a "do not try again" advice. These limits change, so merchants should check the current figures with their acquirer.

Smart retry logic tries to recover soft declines without breaching these limits. Typical tactics are:

• Timing. Retrying insufficient-funds declines around common paydays rather than immediately.
• Better data. Resubmitting with full address data, correct merchant initiated transaction flags or a network token instead of the card number.
• Step-up. Sending the cardholder through authentication for authentication-required declines, which turns the payment into a customer initiated transaction.
• Customer contact. Asking the customer to update the card or choose another method when retries fail, a process subscription businesses call dunning.

For recurring payments, soft declines are the main cause of "involuntary churn", where customers lose service without meaning to cancel. Because a renewal is a card-on-file transaction with no customer present, the merchant cannot simply ask the shopper to try again, and recovery depends on retry logic and reminders. Recovery rates for soft declines are much higher than for hard declines, which is why billing platforms measure them separately and treat payment retry as a revenue tool.

The soft-or-hard label is a simplification. Issuers do not use codes consistently, and the same code can mean different things across banks and countries. Generic codes hide the real reason, sometimes on purpose, since issuers do not want to tell a fraudster exactly why a card was refused. A run of soft declines across many cards can also be a sign of card testing, in which case retrying makes the problem worse. Merchants and their payment processors therefore combine decline codes with their own fraud signals before deciding to retry.

• Visa
• Mastercard
• International Organization for Standardization (ISO)