Retry Configuration

The Payment Service uses the properties described here to determine when and how to retry payment authorizations for system-initiated auto-recharges.

Note: You should not edit the mtx_config.xml file.

The following retry properties are defined in the mtx_config.xml file. Values shown here are the default values.

The maximum time (in minutes) to wait for a system-initiated payment operation to complete.
```
<payment_sys_init_timeout_in_minutes>120</payment_sys_init_timeout_in_minutes>
```
The maximum number of times to retry a payment operation. This setting applies only to operations that can be retried. The maximum refers to the total of retries resulting from transient failures and retries resulting from timeouts. After the 48th failed retry, the status is failed.
```
<maximum_payment_operation_retries>48</maximum_payment_operation_retries>
```
The time (in minutes) to wait after a transient system failure in a payment authorization operation. Transient system failures are failures that can be retried that do not require user intervention to correct. For example, a timeout or the payment gateway is busy.
```
<payment_sys_init_authorize_system_failure_retry_delay_in_minutes>60</payment_sys_init_authorize_system_failure_retry_delay_in_minutes>
```
The time (in minutes) to wait after a transient user failure in a payment authorization operation. Transient user failures are failures that can be retried that usually require user intervention to correct. For example, updating the expiration date or making a payment to free up enough available balance.
```
<payment_sys_init_authorize_user_failure_retry_delay_in_minutes>480</payment_sys_init_authorize_user_failure_retry_delay_in_minutes>
```
A Boolean value that indicates if payment authorization operations should be retried even if the payment method has changed since the last payment authorization operation. This only applies when payment authorization retries are supported, the previous authorization fails with a transient error, and there are retries still available. A value of 1 represents true, 0 represents false (default).
```
<payment_authorize_retry_even_if_payment_method_changed>0</payment_authorize_retry_even_if_payment_method_changed>
```
Note: You can configure this property during engine configuration. The default value is n (0). The create_config.info question is:
```
Should system-initiated payment authorization request failures be retried if payment method change (y/n)?
```