Skip to main content

Search

Français

> Instant Payment Notification URL call

The notification URL is the URL of a dedicated page on your merchant website. The payment gateway calls it automatically when specific events occur. With each call, the payment gateway transmits transaction details to the merchant website. It is called instant notification (or IPN as in Instant Payment Notification).

The table below lists existing URL names and the events that trigger them.

Instant Payment Notification URL at the end of the payment (enabled by default)

Triggering event(s):

  • Payment accepted
  • Payment refused
  • Creation of a recurring payment
  • Token creation
  • Token update

Condition(s):

Source of the event is on the list:
  • PAYMENT
  • VOICE_ORDER
  • KRYPTON

Example(s) of use cases:

  • You want to be notified about the transaction status at the end of the payment.

    This notification is required to communicate the result of the payment request in case of failure.

Activation/deactivation of the rule
  • All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.

    This action will trigger/stop the notification.

Instant Payment Notification URL when creating a recurring payment (Disableddisabled by default)

Triggering event(s):

  • New installment of a recurring payment.
  • Each new payment attempt, after refusal of a recurring payment due date.

Condition(s):

  • None.
Example(s) of use cases:
  • You want to be notified in case of a failure upon each subscription installment.
Activation/deactivation of the rule
  • All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.

    This action will trigger/stop the notification.

Instant Payment Notification URL on batch authorization (disabled by default)

 batch processing is the execution of repetitive tasks containing large volumes of data.

Triggering event(s):

  • Transaction authorized by automatic batch authorization.
  • Transaction refused by automatic batch authorization.
Condition(s):
  • Event source equals to BATCH_AUTO.
Example(s) of use cases:
  • You want to be notified in case of a failure upon each installment.

Activation/deactivation of the rule
  • All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.

    This action will trigger/stop the notification.

Instant Payment Notification URL on batch change (disabled by default)

Triggering event(s):

  • Transaction modified by the merchant or by the acquirer.
  • Transaction validated by the merchant.

Condition(s):

  • Event source equals to BATCH.
Example(s) of use cases:
  • You want to be notified when a transaction expires.

    This is the case of transactions created in manual validation mode and that have not been validated in time by the merchant.

  • You want to be notified in case of a failure about the final transaction status for certain payment methods.
    • This is the case (for those who offer PayPal) when a transaction that has been blocked due to suspected fraud is finally accepted or refused.

Activation/deactivation of the rule
  • All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.

    This action will trigger/stop the notification.

Instant Payment Notification URL on cancellation (disabled by default)

Triggering event(s):

  • Payment abandoned by the buyer.

Condition(s):

  • None.
Example(s) of use cases:
  • You want to be notified if a payment is abandoned or cancelled by the buyer.
Activation/deactivation of the rule
  • All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.

    This action will trigger/stop the notification.

Instant Payment Notification URL on an operation coming from the Back Office (disabled by default)

Triggering event(s):

  • Creation of a manual payment (accepted or rejected)
  • Transaction update
  • Transaction duplication
  • Transaction refund
  • Transaction cancellation
  • Transaction validation
  • Token creation
  • Token update

Condition(s):

  • Source of the event is on the MERCHANT_BO list.
Example(s) of use cases:
  • You want to be notified in case of a failure in the following cases:
    • When a transaction is refunded via the Back Office.
    • When a transaction is modified via the Back Office.

Activation/deactivation of the rule
  • All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.

    This action will trigger/stop the notification.

Notification URL following a payment awaiting confirmation from the external gateway (disabled by default)

Triggering event(s):

  • Pending payment waiting for a confirmation of the external platform.

Condition(s):

  • None.
Activation/deactivation of the rule
  • All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.

    This action will trigger/stop the notification.

Related articles