Users can create customer unique token for saving Credit/Debit cards
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Request Model
The request is a POST request with the following parameters:
| Input Parameter | Type | Length | Description |
|---|---|---|---|
| customerUniqueToken | integer, mandatory | 8 (minimum) to 18 (maximum) | Pass the customer's unique token here |
customerUniqueToken FormationThe customerUniqueToken is used as the primary identifier to retrieve a customer’s saved credit cards. To protect sensitive financial data, you must ensure this token is non-predictable.
Format: Must be a numeric string between 8 and 18 digits (8 digits is highly preffered in order to enable KFAST for saving KNET cards).
Strict Requirement: Do not use a standalone phone number. Phone numbers are public-facing and easily guessable, which creates a high security risk.
Implementation Strategy: We strongly recommend concatenating your internal System User ID with the customer's phone number.
Objective: This composite approach ensures the token is unique to your system and impossible for unauthorized parties to guess or enumerate.
{
"customerUniqueToken":9904917379121
}Response Model
Customer unique token created successfully
{
"status": true,
"message": "Customer unique token created successfully",
"data": {
"customerUniqueToken": 9904917379121
}
}