Decline recovery
Decline recovery interprets exact response codes from the issuing bank to separate temporary blocks from permanent rejections. Merchants implement issuer decline recovery to map specific failure reasons and apply targeted response workflows that salvage valid transactions safely.
- Category
- Recovery
- Capabilities
- 6
- Available on
- All plans
Payment managers reviewing rejected transactions face a complex array of numerical codes returned by the issuing bank. Sorting permanent restrictions from temporary account limitations requires categorising these raw responses to determine whether the merchant should block the transaction entirely or attempt another authorisation request.
Cardflo translates these numerical responses into actionable decline code mapping logic. The platform allows finance teams to assign distinct rules to specific categories, ensuring that generic rejections trigger a different workflow than depleted balance alerts, while connecting operators with acquirer partners capable of handling complex rule structures.
Cardflo's decline recovery system intelligently retries failed transactions and dynamically routes them to optimal acquirer partners, significantly improving success rates. This process converts previously lost sales into successful authorisations, boosting overall payment performance.
Decline recovery overview
Establishing an effective issuer decline recovery strategy demands exact translation of the alphanumeric codes sent back by the issuing institution. Merchants must define whether a code represents a hard refusal, such as a lost or stolen card, or a temporary block like exceeded velocity limits.
This process focuses strictly on the logic that categorises and responds to the issuer's reason for rejection, while relying on payment retry scheduling to handle the optimal timing of subsequent attempts. Separately, technical network downtime is managed through failed payment recovery, and outstanding invoice communication falls under revenue recovery.
By isolating the specific meaning behind each issuer response, operators can configure automated pathways that safely attempt to salvage the transaction. The orchestration platform groups these codes into logical clusters, allowing payment teams to apply targeted workflows that match the exact nature of the initial failure without exceeding scheme limits.
How decline recovery works
Standardising raw issuer responses
When an issuing bank refuses an authorisation request, it returns a specific alphanumeric code through the processing network. The orchestration platform ingests this raw string and maps it against a global dictionary of scheme responses. This normalisation process groups disparate network codes into standardised internal categories, allowing merchants to apply uniform rules regardless of which acquirer partner handled the initial transaction.
Distinguishing hard and soft failures
The internal classification engine separates the standardised codes into definitive categories. Permanent restrictions, such as closed accounts or fraudulent credentials, halt the transaction completely to protect the merchant's standing with card networks. Conversely, soft decline handling identifies temporary constraints like daily velocity limits or missing authentication data, flagging the transaction as eligible for a conditional follow-up workflow.
Triggering the conditional response
Once the failure reason is categorised, the platform executes a predetermined workflow tailored to the specific limitation. If the code requires step-up authentication, the system can prompt the customer to verify the transaction. For transactions encountering do not honour code mitigation protocols, operators can configure the workflow to request an alternative card or halt further attempts, ensuring compliance with network restrictions.
Why decline recovery matters
Scheme penalty avoidance
Continuous attempts to process transactions against permanently closed accounts or reported cards generate unnecessary network fees and risk scheme fines. Effective issuer decline recovery categorises these hard rejections instantly. Finance teams rely on this classification to suppress subsequent processing attempts, preserving merchant account health and maintaining positive standing with their acquirer partners.
Accurate transaction salvage
Treating every refusal identically guarantees lost revenue and frustrated cardholders. By applying specific insufficient funds retry rules, merchants avoid bombarding empty accounts and wait for appropriate conditions. Precise mapping ensures operators only spend processing resources on transactions with a genuine mathematical probability of succeeding on a subsequent attempt.
Regulatory notes for decline recovery
Scheme mandates for permanent closures
Visa and Mastercard maintain strict compliance frameworks detailing how merchants must respond to specific category codes. Scheme rules mandate that transactions returning codes for lost cards, stolen credentials or permanently closed accounts must not be submitted for subsequent authorisation attempts under any circumstances.
Ignoring these mandates exposes the merchant to immediate financial penalties.
Acquirer partners actively monitor their merchant portfolios for compliance with these network suppression rules.
The orchestration platform allows payment teams to automatically block any credential that triggers a permanent rejection code, ensuring complete adherence to network mandates and protecting the operator's merchant identification numbers from excessive retry fines.
Category specific retry limits
Beyond permanent closures, card networks also enforce maximum attempt thresholds for temporary failures over specific rolling windows.
Visa limits the number of times a merchant can retry a transaction that returns an insufficient funds code within a single billing cycle, requiring operators to track attempts against specific credentials.
Finance teams must configure their insufficient funds retry rules to respect these exact network thresholds.
By tracking the specific reason code and the subsequent attempt count, the payment platform prevents the merchant from breaching scheme velocity limits, ensuring that all recovery workflows operate strictly within the permissible bounds of the card networks.
Decline recovery use cases
Wallet deposit limit declines
Digital wallet operators receiving velocity limit or daily deposit ceiling codes risk repeating attempts that issuers have already classified as ineligible. Cardflo maps these responses as hard declines, suppresses prohibited retries and returns a reason category that lets the operator direct the account holder towards another eligible funding instrument.
Luxury purchase decline recovery
Retailers often receive a generic do not honour response where the issuer has not exposed whether the rejection is temporary, fraud-related or permanent. Cardflo normalises acquirer partner responses into conditional decline classes, applies scheme-compliant retry eligibility and prevents ambiguous codes from triggering repeated authorisation attempts without a permitted recovery path.
Insufficient funds response rules
Merchants handling large payment volumes need to distinguish insufficient funds responses from lost card, invalid account and restricted card codes before another authorisation is attempted. Cardflo applies code-specific rules that classify insufficient funds as potentially recoverable while marking prohibited conditions as hard declines, with retry handling constrained by Visa and Mastercard requirements.
Digital service decline mapping
European card payments may return a soft decline when an issuer requires SCA rather than rejecting the underlying account or available funds. Cardflo identifies authentication-required response codes and directs the transaction into a 3DS2 challenge flow, while terminal account, stolen card or invalid credential responses remain blocked from inappropriate resubmission.
Decline recovery by the numbers
This represents the typical percentage of soft declines that can be successfully converted into approvals through automated retry and routing strategies across the payments industry.
Industry benchmarks suggest that implementing robust decline recovery logic can significantly reduce churn caused by failed payments in subscription based business models.
Optimising the recovery layer of the payment stack often results in a measurable increase in total authorisation rates, based on standard global processing data for enterprise merchants.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Decline recovery
- Categorise raw numerical returns into temporary limitations or permanent blocks using automated decline code mapping logic.
- Assign independent workflow triggers to specific refusal reasons to ensure appropriate handling for each transaction attempt.
- Protect merchant identification numbers from scheme penalties by permanently suppressing transactions flagged as lost or stolen.
- Configure specific insufficient funds retry rules that prevent immediate sequential authorisation attempts on depleted accounts.
- Map obscure refusal strings from international acquirer partners into a unified internal classification system.
- Apply soft decline handling logic to trigger strong customer authentication prompts when issuers mandate a challenge.
A short scoping call, then a written plan for your MIDs.
Questions about Decline recovery
How do merchants distinguish between soft and hard issuer declines?
Merchants distinguish these failures by interpreting the exact reason code transmitted by the issuing bank during the authorisation process. Hard failures include specific codes indicating lost cards, stolen credentials or closed accounts, which require the merchant to permanently block the credential.
Soft failures return codes indicating temporary issues such as exceeded velocity limits, missing authentication data or insufficient funds. Cardflo provides the mapping logic necessary to group these raw network responses automatically, allowing the payment operation to execute the correct corresponding response workflow.
What is the correct response for a do not honour decline?
The do not honour code is a generic response from the issuing institution indicating that the transaction cannot proceed, but without specifying the exact underlying cause.
Do not honour code mitigation requires merchants to treat this return cautiously, as immediate sequential retries on this specific code often trigger fraud alerts or scheme penalties.
The orchestration platform allows operators to map this generic response to a distinct workflow that halts automated processing and prompts the customer for an alternative payment method.
How does decline mapping interact with 3D Secure authentication?
Issuers frequently return specific codes indicating that a transaction requires strong customer authentication to proceed. Soft decline handling logic identifies these particular step-up requirements and triggers a response workflow that directs the cardholder through a 3D Secure challenge.
By mapping the exact authentication failure code accurately, the merchant avoids treating an authentication request as a permanent account block, allowing the transaction to continue once the customer successfully verifies their identity with the issuing bank.
Why do card networks penalise excessive authorisation retries?
Visa and Mastercard enforce strict rules regarding how merchants handle permanent failure codes to protect network integrity and reduce processing overhead.
If a merchant ignores a hard rejection code and repeatedly attempts to authorise a lost or stolen card, the networks levy fines and increase processing fees.
Proper issuer decline recovery prevents these penalties by instantly identifying unrecoverable codes and suppressing the credential from any future processing attempts across the merchant's entire acquirer partner network.
Related features.
Related guides.
See how Cardflo compares.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.