支付重試排程
支付重試排程自動重新提交失敗的交易。 此功能允許商戶根據拒絕代碼、交易歷史記錄和客戶區段配置特定的重試邏輯。
它旨在在無需人工干預的情況下恢復收入，提高經常性支付和訂閱的整體交易成功率。
- 類別
- 復原
- 功能數
- 10
- 適用於
- 所有方案
概覽
Payment retry scheduling sits within the recovery layer of the payment stack, specifically addressing soft declines for Merchant Initiated Transactions (MIT).
Unlike hard declines caused by lost cards or closed accounts, soft declines often result from temporary issues such as insufficient funds, technical timeouts, or general bank errors.
By applying logic to these failures, a merchant can resubmit authorisation requests at intervals most likely to coincide with account funding or system stability.
This process typically involves a combination of fixed-interval schedules and dynamic logic that considers the specific decline reason code provided by the issuer. For businesses operating subscription models or recurring billing, this automation minimises the administrative burden of manual outreach while reducing passive churn.
The mechanic relies on mapping response codes to specific retry paths, ensuring that further attempts do not violate card scheme rules or trigger excessive fee penalties from the acquirer.
運作方式
Initial Response Code Analysis
When an authorisation request fails, the system parses the specific response code from the issuer. It distinguishes between hard declines, which require no further action, and soft declines that are eligible for recovery.
This step ensures the merchant remains compliant with scheme rules regarding prohibited retry attempts on specific refusal categories.
Logic Application and Scheduling
The system applies a predefined or dynamic schedule based on the failure reason. For insufficient funds (NSF) declines, the retry might be paused until typical salary dates.
For technical errors, a short-term retry within minutes or hours is often prioritised to capture the transaction during a period of stability.
Request Re-submission via Gateway
The scheduled request is sent back to the acquirer at the designated time, often utilising stored credentials and specific indicators to denote a subsequent attempt.
This process maintains the link to the original transaction attempt where necessary, ensuring the payment flow complies with SCA and PSD2 requirements for MITs.
Outcome Monitoring and Settlement
If the retry is successful, the transaction proceeds to capture and settlement. The result is documented in the recovery logs to assess the efficiency of the timing logic.
If the retry fails, the system either moves to the next scheduled attempt or terminates the cycle as a final decline.
為何重要
Reduction in Passive Churn
Passive churn occurs when a customer has no intention of cancelling a service, but their payment fails due to avoidable technical or financial factors. Automated scheduling addresses these failures in the background.
By recovering these transactions, merchants maintain continuity of service for the cardholder, preventing the friction of manual re-entry and reducing the likelihood of the customer abandoning the subscription due to a service interruption.
Optimised Operational Efficiency
Manual dunning and customer service outreach for failed payments are resource-intensive tasks. Implementing a systematic retry framework reduces the volume of tickets handled by support teams.
By automating the recovery process at the gateway or orchestration level, businesses can focus on growth while the infrastructure handles the complexities of bank response codes and scheme-compliant interval management for recurring billing cycles.
應用案例
Subscription-Based SaaS Platforms
SaaS providers use retry scheduling to handle monthly renewals. If an authorisation fails at midnight on the first of the month, the system ensures subsequent attempts occur when banking systems are most responsive.
Utility and Telecom Billing
For essential services where service disconnection is a risk, retrying payments across a 14-day window following a soft decline ensures revenue capture while avoiding the legal complexities of debt collection.
Digital Content and Media
Streaming services utilise aggressive but compliant retry logic in the first 48 hours following a failure to ensure uninterrupted access to content for high-volume, low-value monthly transactions.
數據概覽
This range reflects typical industry outcomes for recovering soft declines in the subscription sector through automated logic rather than manual outreach.
Expected decrease in total churn for recurring revenue businesses when implementing systematic recovery for secondary and tertiary payment attempts.
The majority of successful recoveries typically occur within this timeframe following the initial decline, according to standard payment processing benchmarks.
相關術語
Talk to our team about a live rollout on your acquiring stack.
What you get with 支付重試排程
- 根據預定義規則自動重新提交失敗的交易。
- 針對不同拒絕類型的可自訂重試間隔和頻率。
- 從過去交易結果中學習的演算法排程。
- 與各種收單機構整合以優化重試路徑。
- 關於重試成功率和恢復收入的詳細報告。
- 防止因可預防的支付失敗而導致客戶流失。
- Utilises stored payment credentials securely via tokenisation for all subsequent Merchant Initiated Transactions.
- Provides granular reporting on recovery rates organised by decline type and specific retry attempt number.
- Maintains compliance with PSD2 and SCA requirements by correctly flagging recurring transaction recovery attempts.
- Reduces the need for immediate dunning emails, favouring silent recovery to maintain customer experience.
A short scoping call, then a written plan for your MIDs.
Questions about 支付重試排程
支付重試排程如何提高收入？
透過自動重新嘗試失敗的支付，系統會捕獲原本會損失的收入。 它針對軟性拒絕和暫時性問題，確保更多的交易在沒有客戶直接參與的情況下成功處理。
我可以為不同的客戶群組自訂重試邏輯嗎？
是的，Cardflo 允許精細自訂重試排程。 您可以為不同的客戶區段、產品類型或訂閱計劃定義不同的規則，根據特定的業務需求和風險概況優化恢復工作。
重試排程解決了哪些類型的拒絕？
支付重試排程主要解決因資金不足、技術錯誤或發卡行端問題等暫時性問題引起的軟性拒絕。 指示永久性問題的硬性拒絕通常不會透過此自動流程重試。
Does retrying a payment affect my authorisation rate metrics?
Initial attempts that fail will negatively impact your raw authorisation rate. However, successful retries improve your net recovery rate and overall revenue.
Most sophisticated payment analytics separate the 'first-time pass rate' from the 'final success rate' after retries. By analysing these separately, merchants can understand whether their initial authorisation issues are due to poor traffic quality or temporary technical hurdles that the scheduling logic is successfully mitigating.
How many times should a failed payment be retried before giving up?
Industry standards generally suggest a maximum of four to six attempts over a period of 15 to 30 days, depending on the MCC and the nature of the product.
The first few retries usually occur within the first 72 hours of the failure, as this is when recovery probability is highest.
Beyond 30 days, the likelihood of success for a soft decline drops significantly, and the risk of a dispute or chargeback if the cardholder has forgotten the subscription increases.
What role does the decline code play in timing the retry?
The decline code is the primary data point for scheduling. For example, a '51: Insufficient Funds' code suggests a retry should be timed near common paydays, such as the 1st or the 15th of the month, or every Friday.
A '05: Do Not Honour' or '96: System Malfunction' might suggest a technical glitch at the issuer, warranting a much faster retry, perhaps within hours, to catch the system after a reboot or sync.