Token Authorisation Request Events

Token authorisation request events are sent from the network scheme and are processed by the message processor. The events represent a request for tokenising a card. In addition to the common attributes, an event must include the following in the payload object:

Field	Description
responseCode	Identifies the action taken by Thredd for the tokenisation request: 00 - Approve, 85 - Approve with Authentication, 05 - Decline.
requestSource	Identifies provisioning request source: KEY_ENTERED, ON_FILE, MOBILE_BANKING_APP, TOKEN, CHIP_DIP, CONTACTLESS_TAP.
tokenRequestorId	Unique ID to the initiator of the token request.
orangeFlowIndicator	Identifies if a given authorisation request is flagged as high fraud risk by Apple (Orange Flow) and needs to be authorised through a fraud prevention call centre.

See the below example of a Tokenisation Authorisation Request Notification:

{
  "context": {
    "programManagerId": 1,
    "eventCode": 106,
    "notificationType": "TAR",
    "creator": "MC-MDES",
    "productId" : 124,
    "correlationId": "111111111111",
    "eventVersion": "v1",
    "notificationTime": "2024-10-24T03:20:28Z",
  },
  "payload": 
   {
      "publicToken": "123456789",
      "paymentToken": "987654321",
      "dpan": "5168563000002547",
      "networkTokenReference": "67024958022",
      "provisioningTraceId": "VIS1-20210318-381077544887139",
      "tokenisationServiceDateTime": "2024-10-29 15:16:30.000",
      "processorDateTime": "2024-10-29 15:16:50.000",
      "responseCode": "85",
      "requestSource": "MOBILE_BANKING_APP",
      "tokenRequestorId": "1234",
      "orangeFlowIndicator": true
   },
  "messageHeaders": {
    "schemaId": 1
  }
}

Updated 1 day ago