You can provide a different endpoint for the Program' Notifications and each Merchant's Notifications. Please coordinate with your Technical Rollout Manager.
Callbacks
Last changes: 10-19-2023
This section covers how webhooks are used to notify about events that happen in an E-wallet Program. Some events, like disputed charges or account status changes, are not the result of a direct API request. Webhooks solve these problems by letting you provide a URL to which we will send a notification anytime such an event happens.
The "Notification Target URL" will recive a JSON payload depending on the notification type. Based on your integration requirements the individual notifications have to be turned on. Please contact Customer Support or your administrator to check your individual integration use case.
Any of the below authentication methods can be selected for the corresponding program:
Authentication Type | Behavior |
No Authentication | No authentication information is sent in the requests to the "Notification Target URL". |
Basic Authentication | The authentication is done by specifying a Username and Password under the |
OAuth Authentication | The Authentication URL along with the Username and Password must be specified. |
There are 2 distinct notification types
- Program Specific Notifications - sending more detailed transaction information regarding the entire program, in addition to user management, compliance and others.
- Merchant Specific Notifications - only sending transaction related information regarding a specific merchant. They can be configured for each individual merchant.