Tokenisation Event Notification Events

Tokenisation Event Notification (TEN) events are either:

generated by a network scheme and processed by the message processor.
generated internally by the VDEP/MDES lifecycle APIs and communicated with the network.

This notification is used to communicate token status changes. In addition to the common attributes, this event must include the following in the payload object:

Field	Description
eventReason	Tokenisation event reason for why the Tokenisation event was triggered.
messageReasonCode	Reason code associated with a given event reason when applicable.
eventRequestor	Indicator of which entity requested the event.
processorTokenStatus	Issuer processor (Thredd) token internal status.
tokenisationServiceTokenStatus	Tokenisation Service token status (VDEP/MDES).

See the below example of a Tokenisation Event Notification:

{
  "context": {
    "notificationId": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
    "eventCode": 109,
    "eventVersion": "v1",
    "notificationTime": "2024-01-24T23:20:28Z"
  },
  "payload": {
    "publicToken": "123456789",
    "productId": "124",
    "paymentToken": "987654321",
    "dpan": "5168563000002547",
    "networkTokenReference": "67024958022",
    "provisioningTraceId": "VIS1-20210318-381077544887139",
    "tokenisationServiceDateTime": "2024-10-29T15:16:30Z",
    "processorDateTime": "2024-10-29T15:16:50Z",
    "eventReason": "8",
    "messageReasonCode": "02",
    "eventRequestor": " ",
    "processorTokenStatus": "ACTIVE",
    "tokenisationServiceTokenStatus": "ACTIVE"
  }
}

Updated 17 days ago