Analyzing the nature of the notification
The vads_url_check_src field allows to differentiate the notifications based on their triggering event:
- token creation (with or without the subscription of a recurring payment),
- installment payment,
- new notification sent by the merchant via the Expert Back Office
It specifies the applied notification rule:
Value | Applied rule |
---|---|
PAY | The PAY value is sent in the following cases:
|
BO | Execution of the notification via the Expert Back Office (right-click a transaction > Send the Instant Payment Notification). Check whether the vads_recurrence_number field is present:
|
BATCH | The BATCH value is sent in case of an update of a transaction status after its synchronization on the acquirer side. This is the case of payments with redirection to the acquirer. Only if the merchant has configured the rule Instant Payment Notification URL on batch change. |
BATCH_AUTO | The BATCH_AUTO value is sent in the following cases:
The notification is sent with the authorization request for payments with "Waiting for authorization" status. |
REC | The REC value is sent only for recurring payments if the merchant has configured the Instant Payment Notification URL when creating recurring payments rule. See the Installment payment chapter for more information on the sent data. |
MERCH_BO | The MERCH_BO value is sent:
|
RETRY | Automatic retry of the IPN. Check whether the vads_recurrence_number field is present:
|
After checking its value, the script can process differently depending on the nature of the notification.
For example:
If vads_url_check_src is set to PAY or BATCH_AUTO, the script will update the order status, etc.
If vads_url_check_src is set to REC, the script will retrieve the recurring payment reference and will increment the number of the expired installment payments in case the payment has been accepted, etc.
In the context of a recurring payment (from a REGISTER_SUBSCRIBE), the payment gateway notifies the creditor (merchant) when creating each transaction.