Analyzing the nature of the notification
During a notification, the vads_url_check_src field allows to differentiate the notifications based on their triggering event:
- creation of a transaction
- new notification sent by the merchant via the Expert Back Office.
It specifies the applied notification rule.
Values associated with the vads_url_check_src field:
Value | Description |
---|---|
PAY | Payment creation by form. Value sent in the following cases:
|
BO | Execution of the notification URL via the Expert Back Office. (right-click a transaction > Send the Instant Payment Notification). |
BATCH_AUTO | Value sent as part of an authorization request for a payment that was awaiting authorization. Not applicable for one-off direct debit on SEPA. |
BATCH | Value sent in case of an update of a transaction status after its synchronization on the acquirer side. Only if the merchant has configured the “Instant Payment Notification URL on batch change” rule. |
DCF | Value sent following a transaction from the data collection form. |
MERCH_BO | Value sent following a transaction carried out via the Expert Back Office if the merchant has configured the notification rule: “Instant Payment Notification URL on an operation coming from the Back Office”. |
PAYMENT_ORDER | Value sent following a transaction originating from a payment order (e-mail, payment URL or SMS). |
REC | Value is sent only for recurring payments if the merchant has configured the “Instant Payment Notification URL when creating recurring payments” rule. Not applicable for one-off direct debit with SEPA. |
RETRY | Automatic retry of the IPN. |
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.