Introduction to Tokenisation Event Notifications
Tokenisation Event Notifications allow you to send different types of tokenisation events in near real time using Thredd's Event Delivery Service. In addition to offering a near real-time communication channel, you use Token Event Notifications for self-service, using the REST API to onboard and manage subscriptions to specific events.
The following table decribes each of the events and their respective event code.
| Event Code | Tokenisation Event | Description |
|---|---|---|
| 106 | Tokenisation Authorisation Request (TAR) | Notifications sent using Thredd's Event Delivery Service for new Tokenisation requests (TAR requests). |
| 107 | Tokenisation Activation Code Notification (ACN) | Notifications sent using Thredd's Event Delivery Service for Activation Code delivery (ACN notification). |
| 108 | Tokenisation Activation Code Notification (ACN) | Notifications sent using Thredd's Event Delivery Service to inform the tokenisation completion (TCN notification). |
| 109 | Tokenisation Event Notification (TEN) | Notifications sent using Thredd's Event Delivery Service for token status changes (TEN notification). |
| 110 | Tokenisation status update Failure Notification (TFN) | Notifications sent using Thredd's Event Delivery Service for failed token status changes. |
NoteToken Event Notifications use our Webhook solution. For more information on how to create webhooks events, see Introduction to Webhooks.
Common Fields for Tokenisation Events
A set of common attributes are present on all event types, with some additional attributes per event type. The below table displays information for the common attributes in the context object for tokenisation event notifications.
| Field | Description |
|---|---|
| programManagerId | Program Manager to deliver this event. |
| eventCode | Event code configured on Event Delivery Service (EDS). One of 106, 107, 108, 109 , 110. |
| notificationType | Type of tokenisation event. One of TAR, ACN, TCN, TEN, TFN. |
| creator | Reference to tokenisation service. One of MC-MDES, VISA-VDEP. |
| productId | Thredd Product identifier. |
| correlationId | Service generated unique event identifier. |
| eventVersion | Event version. By default this will be v1. |
| notificationTime | Notification generation timestamp. |
The below table displays information for the common attributes in the payload object for tokenisation event notifications.
| Field | Description |
|---|---|
| publicToken | Card public token associated with a given tokenisation notification. |
| paymentToken | Payment token internal identifier. |
| dpan | Payment token identifier (DPAN). |
| networkTokenReference | Unique Token Reference from the network. |
| provisioningTraceId | Lifecycle identifier to link tokenisation events that are related. |
| tokenisationServiceDateTime | Event generation timestamp (from the tokenisation service). |
| processorDateTime | Event processing timestamp (from Thredd). |
Updated 1 day ago