Tokenization Initiation
The first message CLOWD9 receives from the network is a request to verify whether the PAN is active and eligible for tokenization.
CLOWD9 responds directly to the network with the result of this eligibility check.
Event: check_eligibility
This event is triggered at the beginning of the tokenization process to determine whether a DPAN can be issued for the provided PAN.
Request
Field | Description | Format |
---|---|---|
event_type | Identifies the activity | UUID |
created_datetime | The date and time of the request | String |
token_info | Object | |
dpan_id | The Identifier associated to the DPAN | UUID |
card_id | The Identifier associated to the Card | UUID |
token_reference_id | Unique ID for the token associated with the PAN | String |
pan_reference_id | Network generated Identifier | String |
client_id | The Identifier associated to the Client | UUID |
customer_id | The Identifier associated to the Customer | UUID |
network | Identifies the Network associated with the Wallet Provider | String |
status | The current status of the DPAN | String |
previous_status | The previous status of the DPAN if applicable | String |
Example
Example 2 - DPAN Check Eligibility
{
"created_datetime": "1754313047",
"event_type": "check_eligibility",
"token_info": {
"card_id": "47277b0d-2aa6-48ab-a2f5-7a5dababf2f8",
"client_id": "82d890aa-f083-4359-a1c8-5cd483ba40e8",
"network": "visa",
"pan_reference_id": "V-3025197339880335891989",
"previous_status": "",
"status": "",
"token_reference_id": "DNITHE302521033484727131"
}
}
Response
If the request is successfully received and processed, respond with:
HTTP/1.1 200 OK
No response body is required.
Updated about 1 month ago