Overview of the pan_verification object.
Shown below is a sample pan object.
{
"id": "pan_XAZyW7rLkhQ16bZEM1SRIl4Q2",
"object": "pan_verification",
"pan": "AAAPA0000A",
"name_on_pan": "Anil Reddy",
"status": "success",
"merchant_reference_id": "1000629",
"message": "PAN verified",
"metadata": {
"key_1": "DD",
"key_2": "XOF"
},
"created_at": 1662032873,
"consent": true,
"is_sandbox": false
}
The table below lists the various parameters in the pan object.
| Parameter | Type | Description |
|---|---|---|
| id | string | Unique identifier of the PAN verification request in the ZWITCH database. Example: pan_jNsJ5K9mz8tHXL7XiJbKr241r |
| object | string | API object that is returned. Possible value: pan_verification |
| pan | string | PAN number to be verified. Example: AAAPA0000A |
| name_on_pan | string | PAN holder's name as per the PAN database. Example: Anil Reddy |
| status | string | Possible values:
|
| merchant_reference_id | string | Unique identifier entered when creating the verification request.
Example: 14096850 |
| message | string | Message describing the status of the transaction. Example: Invalid PAN |
| metadata | object | Object of key-value pair that can be used to store additional information about the entity.
Example: "key_1": "We are using Zwitch.” |
| created_at | integer | Unix timestamp when ZWITCH received the request. Example: 1640179951 |
| consent | boolean | Consent of the individual to get their details from the PAN database. |
| is_sandbox | boolean | Mode in which the API was triggered. Possible values:
|