Notifications
Last updated
⌘Ctrlk
Enable Push Updates to automatically receive information about the CMP services without manual checks. Learn more about notifications in the Notification Center.
You can set up a webhook to receive Network Token and Account Updater updates by following the below steps:
Navigate to your Dashboard, and in the left-hand menu under Administration select Organization
On the Organization page, select the Notifications tab
Select Add a Notification, and enter the details for your Webhook as desired
After creation, search and add the desired events from the events list
cmp_au_card.updated
cmp_au_card.expired
cmp_au_card.closed
cmp_au_card.non_participating
cmp_au_card.contact_cardholder_advice
cmp_au_card.unknown
cmp_au_card.enrolled
cmp_au_card.opt_out
cmp_au_card.enrollment_failed
For more information on CMP Account Updater Events, refer to the Account Updater Events section.
cmp_network_token.updated
For more details on CMP Network Tokens Events, refer to the Network Tokens Events section.
Configure the Vaults for which you want to subscribe to these notifications in the modal that appears
Press the Save button in the bottom right corner of the page
You should now start receiving updates for the Network Token and/or Account Updater Vaults for which you have subscribed.
cmp_threeds.device_fingerprint
Configure this event in your notifications on the VGS Dashboard to receive the result of the device fingerprinting step.
This notification indicates whether device fingerprinting was successfully completed (success = true or false) via the Initialize Callback/Notification.
cmp_threeds.challenge_result
Configure this event in your notifications on the VGS Dashboard to receive the final authentication result for the challenge flow.
This notification indicates whether the user successfully completed the challenge or if it was aborted or timed out.
Click here to learn how to set up your notifications.
Each webhook request contains a unique signature within HTTP header “vgs-signature” to verify the request’s VGS origin. More details can be found here.
Last updated