Nouvelles tentatives de refus souples
Les nouvelles tentatives de refus souples ciblent spécifiquement les échecs de paiement temporaires qui peuvent être résolus en retentant la transaction. Cette fonctionnalité de Cardflo identifie intelligemment les refus souples et les resoumet automatiquement selon des calendriers adaptés.
Elle augmente considérablement les taux d'approbation en traitant les problèmes transitoires sans intervention du client, réduisant ainsi le désabonnement involontaire.
- Catégorie
- Récupération
- Capacités
- 10
- Disponible sur
- Tous les plans
L'aperçu
Soft decline retries operate within the payment orchestration layer to rescue transactions that failed due to temporary issues rather than permanent account closures or insufficient funds.
Unlike a hard decline, which indicates a final rejection from the issuer, a soft decline signifies that the authorisation failed because of a transient error such as a processor timeout, system maintenance at the acquirer, or a temporary card limit restriction.
Within the payments stack, this function sits between the gateway response and the final settlement status. By analysing the raw response codes provided by the schemes and issuers, the system identifies whether a retry is permissible under scheme rules.
This mechanism is particularly critical for Merchant Initiated Transactions where the customer is not present to provide an alternative payment method.
Automating this process ensures that the capture is attempted again at an optimal time, which minimises manual intervention and helps maintain continuous service for subscription-based business models.
Comment ça marche
Identification of Response Codes
The system parses the decline codes returned by the issuer via the acquirer.
It distinguishes between hard declines, such as stolen cards or closed accounts, and soft declines like technical errors or suspected fraudulent activity that may be cleared upon a subsequent attempt with updated parameters or different timing.
Application of Scheme Rules
Before scheduling a retry, the logic verifies compliance with Visa and Mastercard scheme rules regarding retry frequency and volume.
This prevents excessive attempts that could lead to fines or the flagging of the Merchant Identification Number by the card schemes, ensuring all recovery efforts remain within authorised bounds.
Algorithmic Scheduling and Intervals
The transaction is queued for resubmission based on the specific refusal reason.
For example, a system timeout might trigger an immediate retry within seconds, whereas a soft decline related to daily spend limits might be scheduled for the following morning to align with the reset of the account balance.
Secondary Authorisation Execution
The system automatically resubmits the authorisation request using the original tokenised credentials and transaction metadata.
This often involves specific flags to indicate a Merchant Initiated Transaction, ensuring the issuer recognises the retry as a legitimate continuation of an existing billing relationship rather than a new, suspicious request.
Pourquoi c'est important
Reduction in Involuntary Churn
Involuntary churn occurs when a customer's subscription is cancelled due to technical payment failures rather than an intent to leave. By automating the recovery of soft declines, businesses can preserve the customer lifecycle without requiring the user to update their payment details.
This maintains stable revenue streams and reduces the high cost associated with re-acquiring lost customers who may not return after a service interruption.
Optimised Authorisation Rates
Authorisation rates are a primary key performance indicator for digital merchants. Soft decline retries provide a secondary layer of capture that addresses the natural volatility of global banking systems.
By intelligently timing these attempts, merchants can capture revenue that would otherwise be lost to transient infrastructure issues, directly improving the bottom line and increasing the overall efficiency of the payment processing workflow.
Cas d'usage
Subscription Billing Cycles
Recurring service providers use retries to handle month-end processing spikes where issuer systems may experience temporary latency or account limits are reached before payday.
Cross-Border E-commerce
Merchants selling into international markets use retries to manage time-zone related outages and varying stability levels across diverse global acquirer networks.
High-Volume Digital Goods
Platforms with high transaction counts use automated logic to filter out temporary technical errors from genuine fraud, ensuring legitimate buyers are not permanently blocked.
SaaS Renewal Sequences
Software companies use multi-day retry schedules to capture funds during the grace period of a license renewal before access to the platform is suspended.
En chiffres
This represents the typical percentage of soft declines successfully captured through automated retry logic across the payments industry.
Merchants utilising intelligent retry schedules often see a three-fold decrease in subscription failures compared to those with static retry rules.
An industry-standard range for the overall increase in successful authorisations after implementing soft decline management across a global MID.
Termes associés
Talk to our team about a live rollout on your acquiring stack.
What you get with Nouvelles tentatives de refus souples
- Identification et catégorisation automatiques des codes de refus souples.
- Algorithmes de nouvelle tentative intelligents basés sur les taux de réussite historiques.
- Tentatives et intervalles de nouvelle tentative configurables par type de refus.
- Routage dynamique des nouvelles tentatives vers des acquéreurs ou MIDs alternatifs.
- Analyse en temps réel de la performance des nouvelles tentatives de refus souples.
- Réduction du désabonnement des clients en résolvant les problèmes de paiement temporaires.
- Customisable thresholds for the number of retry attempts permitted before a final decline status.
- Support for smart-routing retries through alternative acquirers to bypass local processing outages.
- Preservation of original transaction metadata to maintain 3DS and SCA compliance during secondary attempts.
- Reduction in manual customer support tickets related to failed payments and account access issues.
A short scoping call, then a written plan for your MIDs.
Questions about Nouvelles tentatives de refus souples
Qu'est-ce qu'un refus souple et comment Cardflo le gère-t-il ?
Un refus souple est un échec de paiement temporaire, souvent dû à des fonds insuffisants, des problèmes techniques ou des erreurs du système de l'émetteur. Cardflo les identifie automatiquement et retente intelligemment la transaction aux moments optimaux, augmentant ainsi les chances d'approbation.
Comment le routage dynamique profite-t-il aux nouvelles tentatives de refus souples ?
Le routage dynamique permet à Cardflo de resoumettre une transaction refusée de manière souple via un acquéreur ou un MID différent si la tentative initiale échoue.
Cela augmente la probabilité d'approbation en tirant parti de diverses connexions réseau et en réduisant les points de défaillance uniques.
Puis-je voir quels refus souples ont été récupérés avec succès ?
Oui, Cardflo fournit des rapports détaillés et des analyses sur toutes les tentatives de nouvelle tentative.
Les commerçants peuvent surveiller les taux de réussite des nouvelles tentatives de refus souples, identifier les causes courantes des échecs temporaires et comprendre les revenus récupérés grâce à ces efforts.
Which decline codes are most commonly associated with successful soft decline retries?
Commonly retriable codes include '05: Do Not Honour' (which can be a catch-all but often recovers), '19: Re-enter Transaction', '65: Exceeds Withdrawal Frequency', and '91: Issuer or Switch Inoperative'.
Codes related to system errors or temporary freezes often see high success rates on the second or third attempt. Conversely, codes like '14: Invalid Card Number' or '41: Lost Card' are hard declines and must be filtered out of any automated retry logic.
Can retrying a transaction through a different acquirer improve success rates?
Yes, this is a core component of payment orchestration. If a soft decline is triggered by a technical failure or a regional outage at one acquirer, routing the retry through a second acquirer can bypass the local infrastructure issue.
This is particularly effective for cross-border payments where an issuer might be more likely to authorise a transaction coming through a local domestic acquirer rather than an international one, depending on the risk profile of the transaction.
How does SCA and PSD2 impact the ability to perform soft decline retries?
Under PSD2 in Europe, most transactions require Strong Customer Authentication. However, retries are usually categorised as Merchant Initiated Transactions (MITs) if they are part of a recurring series or follow an initial authenticated transaction.
As long as the first transaction was correctly authenticated and the subsequent retry is flagged with the correct scheme indicators and the original transaction ID, it can usually proceed without a new SCA challenge, assuming the issuer accepts the MIT exemption.
Prêt à accélérer ?
Parlez-nous de votre activité. Nous vous mettrons en relation avec les bons partenaires acquéreurs et la bonne route, généralement en moins d'une semaine.