Activation Code Notification Events
Activation Code Notification events are sent from the network scheme through a REST API invocation for VDEP (VDEP Provisioning API) and through an ISO message for MDES. The event contains the OTP code required for client verification. In addition to the common attributes, this event must include the following in the payload object:
Field | Description |
---|---|
otpValue | The One-Time Passcode value. |
otpReason | The OTP reason: PAYMENT, TOKEN_DEVICE_BINDING, CARDHOLDER_STEPUP, TRUSTED_LISTING_ENROLLMENT. |
otpExpirationDate | The OTP expiration timestamp. |
activationMethod | The consumer’s activation method preference. |
deviceInfo | The device for the tokenisation request. Data structure to include one or more attributes from: deviceName, deviceID, deviceType, deviceNumber |
See the below example of a Activation Code Notification:
{
"context": {
"programManagerId": 1,
"eventCode": 107,
"notificationType": "ACN",
"creator": "MC-MDES",
"productId" : 124,
"correlationId": "111111111112",
"eventVersion": "v1",
"notificationTime": "2024-10-29T03: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",
"otpValue": "123456",
"otpReason": "TOKEN_DEVICE_BINDING",
"otpExpirationDate": "2024-10-29 15:46:30.000",
"activationMethod": "6",
"deviceInfo": {
"deviceId": "01234B234C1230011230054848300695D86E17C703548A4A",
"deviceType": "W"
}
},
"messageHeaders": {
"schemaId": 1
}
}
Updated 1 day ago