Skip to main content

Notifications

In addition to the API response and the callback to redirectUrl, Revup reports merchants of any changes in the transactions through notifications.

Each merchant must provide Revup with a static notification URL where any notification message will be sent by default. Alternatively, you can also provide this value within the payment order if you wish to have a different notification URL for some specific cases. Learn more in the notification documentation.

Revup sends notifications for synchronous and asynchronous payments (like 3DS transactions) and includes information about the operation (e.g., ID, current status, etc.). It is critical for asynchronous transactions that might be initially in a non-final condition (in_process or waiting_user_interaction), as notifications will inform you about their final status.

Callback vs Notification​

It is critical to understand that callback and notification are two different things:

Callback​

  • The callback: holds a list of performed transactions (containing just one element or two if a fallback MID is enabled) in which Revup specifies every available detail for each transaction. It is sent directly by Revup to redirectUrl.

Notifications​

  • Notifications: report status changes in transactions. The PSPs send them, and Revup transforms them into standard format before directing them to the notification URL.