Recurring Billing includes these additional features.

System Retry

When a payment fails due to an internal error, the system retries the payment until the error is resolved.

When a payment fails due to an external error (such as a declined card), the system retries the payment based on the billing frequency before changing the subscription status to suspended.

If the response contains a "Do Not Retry" reason code, the subscription is immediately suspended without retries.

The maximum number of retries is 5. During the retry period, the subscription status changes to Delinquent.

The retry schedule varies by billing frequency:

For a custom billing frequency, the system uses Daily retry logic first, then Weekly retry logic every 2 weeks.

Customer Notifications

sends email notifications to customers for these events:

• Prepayment notification
• Successful payment notification
• Failed payment notification

Notifications are sent from a email address.

You can disable customer notifications in the .

Email templates use these variables:

• ${paymentDate}: the date the payment is processed.
• ${subscriptionId}: the subscription ID.
• ${subscriptionName}: the subscription name.
• ${billingAmount}: the billing amount.
• ${currency}: the currency.
• ${setupFee}: the set-up fee.
• ${transactionId}: the transaction ID.
• ${merchantName}: the merchant name.

Decision Manager Integration

Recurring billing transactions are considered low risk and are not submitted to Decision Manager for fraud screening.