Automatic retry in case of failure

Automatic retry does not apply to notifications manually triggered via the Merchant Back Office.

The merchant can enable a mechanism that allows the payment gateway to automatically return notifications when the merchant website is temporarily unavailable. This mechanism allows up to 4 attempts to be made.

A notification will be considered as failed if the HTTP code returned by the merchant site is not on the following list: 200, 201, 202, 203, 204, 205, 206, 301, 302, 303, 307, 308.

Call attempts are scheduled at fixed intervals every 15 minutes (00, 15, 30, 45).

After each failed attempt, a notification e-mail is sent to the e-mail address specified in the configuration of the notification rule in question.

In this case, the subject of the e-mail contains the number corresponding to the notification retry attempt. It is presented as attempt # followed by the attempt number.

Example of an e-mail subject following a first notification failure at the end of payment:

[MODE TEST] My Shop - Tr. ref. 067925 / FAILURE during the call to your IPN URL [unsuccessful attempt #1]

Example of an e-mail subject following a second failure:

[MODE TEST] My Shop - Tr. ref. 067925 / FAILURE during the call to your IPN URL [unsuccessful attempt #2]

Example of an e-mail subject following a third failure:

[MODE TEST] My Shop - Tr. ref. 067925 / FAILURE during the call to your IPN URL [unsuccessful attempt #3]

Example of an e-mail subject following the last failure:
```
[MODE TEST] My Shop - Tr. ref. 067925 / FAILURE during the call to your IPN URL [unsuccessful attempt #last]
```
To notify the merchant website of the last notification attempt, the e-mail subject will contain the mention attempt #last.

These e-mails contain:

The encountered problem;
Parts of analysis depending on the error;
Its consequences;
Instructions for manually triggering the notification from the Merchant Back Office.

After the fourth attempt, it is still possible to retry the IPN URL manually via your Merchant Back Office.

Note that during the automatic retry, any manual call to the IPN URL will affect the number of automatic attempts:

A successful manual call will stop the automatic retry;
A failed manual call will have no impact on the current automatic retry.

During the automatic retry, certain details are not stored in the database or are modified.

Examples of fields not available/not registered in the database in API Form format :

Field name	Description
vads_page_action	Completed operation
vads_payment_config	Payment type (immediate or installment).
vads_action_mode	Acquisition mode for payment method data.

Examples of fields sent with different values in API Form format :

Field name	New value
vads_url_check_src	Always set to RETRY in case of automatic retry.
vads_trans_status	The transaction status may vary between the initial call and the automatic retry (cancellation by the merchant, transaction capture at the bank, etc.).
vads_hash	The value of this field is regenerated with each call.
signature	The signature value depends on the different statuses that may vary between the initial call and the automatic retry.

Examples of fields sent with different values in API Form format :

Field name	New value
transactions.detailedStatus	The transaction status may vary between the initial call and the automatic retry (cancellation by the merchant, transaction capture at the bank, etc.).
kr-hash	The value of this field is regenerated with each call.

Categories

Tags

Automatic retry in case of failure