Overview of the vpa_verification object.
Shown below is a sample object for the vpa_verification object.
{
"id": "accver_mtBP3HwL4JE6Ywl2oL2wiun09",
"object": "vpa_verification",
"vpa": "anil.reddy@example",
"merchant_reference_id": "1409614085",
"name_as_per_bank": "Anil Reddy",
"status": "success",
"message": "VPA is available for transaction",
"bank_ifsc_code": "ICIC0000296",
"bank_account_type": "savings",
"created_at": 1644843861,
"is_sandbox": true,
"metadata": {
"key_1": "DD",
"key_2": "XOF"
}
}
The table below lists the various objects in the vpa_verification object.
| Parameter | Type | Description |
|---|---|---|
| id | string | Unique identifier of the account verification transaction in the ZWITCH database. Example: accver_Qs93rRv6Vq4EIVzKurII849yj |
| object | string | API object that is returned. Possible value: vpa_verification |
| vpa | string | The Virtual Payment Address (VPA) handle (UPI ID) you want to verify. Example: anil.reddy@example |
| name_as_per_bank | string | Account holder's name as per bank records. Example: Anil Reddy |
| status | string | Status of the account verification transaction. Possible values:
|
| message | string | Message about the account verification transaction. Example: VPA is available for transaction |
| bank_ifsc_code | string | Account holder's IFSC Example: ICIC0000296 |
| bank_account_type | string | Account holder's bank type. Possible values:
|
| merchant_reference_id | string | Unique identifier entered when creating the verification request.
Example: 1409614085 |
| created_at | integer | Unix timestamp when the account validation request was received by ZWITCH. Example: 1640179951 |
| is_sandbox | boolean | The mode in which the API was triggered. Possible values:
|
| metadata | object | Object of key-value pair that can be used to store additional information about the entity.
"key_1": "DD" |