Cascading within retry

Immediate cascading is not enabled.

If the first payment transaction fails, the payment will be automatically retried with the next available payment method in the priority list, following the manual or scheduled retry cycle until the payment is processed. A new payment will be created for each retry.

For a use case example, see Example 1: Cascading within retry.

Immediate cascading

Immediate cascading is enabled.

If the first payment transaction invoked by the payment run fails, the payment is immediately retried with the next available payment method in the priority list. The process continues until either the payment is processed or all payment methods in the priority list are used once.

If all payment methods in the priority list have been used once but the payment has not been processed, immediate in-transaction retries will be invoked again during the subsequent manual or scheduled retry cycle.

For a use case example, see Example 2: Immediate cascading.

By using the immediate cascading mode, the same payment is used in the retries for a payment run. During the retries, the payment reference information, typically the payment number, is sent to the gateway. However, some gateways do not allow duplicate payment references, resulting in errors if the same payment number is sent multiple times. If your gateway provider restricts duplicate payment references, it is recommended to disable the immediate cascading mode. Instead, use the cascading within retry mode, which creates a new payment for each retry.