Payment Notification (callback_notification)

The notification callback is utilised when we need to notify your system, but without the customer being present.

Unlike the OK, Fail and Open callbacks, any output returned by the notification callback is discarded, as this happens without the customer being a part of the payment flow. This callback allows you to update your own system and e.g. allows you to email the user.

The following scenarios can trigger the notification callback:

  • A payment cannot be completed immediately. In such cases, the result is posted to the open page (callback_open), and when the request is later processed, a notification is sent to the notification page (callback_notification). An example of this is PayPal doing a fraud check, or Klarna performing an asynchronous credit check.
  • A customer leaves the payment flow, and the OK page or open pages are never called. An example of this iDEAL payments, where the customer may not return from the bank, whereby us not being able to trigger the Callback OK.
  • For some payment methods we will always trigger the notification callback, also if the Callback OK is triggered. An example of this is MobilePay.
  • A chargeback occurs. These will have a status of "ChargebackEvent". This is mainly used if you want to automate the handling of chargebacks.
    These callbacks can be configured in the Merchant Information Interface.
  • The status parameter is missing "ChargebackEvent" (only relevant for notification callbacks).

The parameters for the notification page are identical to those for the callback_ok or callback_fail pages, depending on whether the payment request was successful, or failed.