Customer Verification Options
During the DPAY Tokenization stage, your Customer maybe required to provide additional verification before the request can be completed. This is know as the Yellow Path.
The Options supported are:
One Time Passcode (OTP)
CLOWD9 will communicate to the Network to confirm the OTP is the preferred method of authentication. The Network will generate the OTP and provide this to CLOWD9.
CLOWD9 will communicate this to you via a web hook to send to your Customer:
OTP
Field | Description | Format |
---|---|---|
client_id | The Identifier associated to Client | UUID |
customer_id | The Identifier associated to the Customer | UUID |
card_id | The Identifier associated to the Card | UUID |
dpan_id | The dpan_id associated with the authentication request | UUID |
device_id | The ID associated with the device | string |
device_language_code | 3 character language code. Default is eng | string |
?? Link ?? Can we link this to the previous Approve Provisioning Request sent by Web hook in case the Customer has tired multiple times? | string | |
otp | Value of the OTP | string |
datetime | The Date and Time associated with the authentication request | integer |
Example:
"client_id": "958e5955-1ebb-4f70-8179-5fe60bdf8382",
"customer_id": "89d02c52-f371-4106-8807-e3325774bd3b",
"card_id": "92d3824f-d3bd-4226-8e60-58ee2c9b39a4",
"dpan_id": "4e047e68-d507-4c67-871e-500a7f557098"
"device_id": "1d1eb44e-f90b-4eff-8ea8-c0a2b1a3ac7d",
"device_language_code": "eng",
"otp": "829384",
"datetime":1738322465 ,
You will be required to response with the following
Example Response
"SUCCESS"
Updated 5 days ago