On This Page

{#jumplink-list}  
[Markdown](/content/cybsdeveloper2021/amer/en/docs/cybs/en-us/recurring-billing/developer/all/rest/recurring-billing-dev/recur-bill-addl-feat/recur-bill-sys-retry.md)

System Retry Logic {#recur-bill-sys-retry}
==========================================

`Cybersource` automatically retries failed recurring payments based on the type of decline received from the service. The service retries the internal and external payment declines.  
If the Recurring Billing service encounters an internal processing error without sending the request out to the banking network, the service retries the payment until the error is resolved.  
If the recurring billing service encounters an external processing error when the request is sent out to the banking network, `Cybersource` retries the payment before changing the subscription status to suspended.  
If the issuer provides a reason code like "Do Not Retry", `Cybersource` stops all retry attempts. `Cybersource` immediately updates the subscription status to suspended.  
The maximum number of retries is five times and is based on the billing frequency. During the retry period, `Cybersource` changes the subscription status to delinquent.  
This example shows the system retry logic based on the billing frequency:

* **Daily**: retry 1 hour later, 1 time
* **Monthly**: retry every 2 days, 5 times
* **Weekly**: retry every 1 day, 3 times
* **Yearly**: retry every 15 days, 3 times  
  For a recurring payment that has a custom billing frequency, the Recurring Billing service retries a failed payment based on the billing frequency. As an example, suppose a payment fails for a recurring billing on a 14-day cycle. The recurring billing service uses the Daily retry logic and every 2 weeks uses the Weekly retry logic, even if the duration is the same.

