post https://uat-accounts.payu.in/api/v3/merchants/kyc_document/aadhaar_xml_offline
The Aadhar XML Offline API allows merchants to submit Aadhaar XML files (obtained from DigiLocker or UIDAI) for KYC verification purposes.
Environment
Test | https://uat-accounts.payu.in |
Production | https://accounts.payu.in |
Request parameters
Authorization header
Authorization Bearer token must be generated using **Aadaar OTP Generation API ** with the scope as . For more information, refer to Aadhaar OTP Generation API.
Body parameters
Parameter | Description | Example |
---|---|---|
aadhaar_share_code
| The share code provided when downloading the Aadhaar XML file | 3456 |
merchant_id
| Unique identifier for the merchant | 8390925 |
aadhaar_file
| The XML file downloaded from DigiLocker or UIDAI website | [FILE] |
Sample request
curl --location 'https://partner.payu.in/api/v3/merchants/kyc_document/aadhaar_xml_offline' \
--header 'Authorization: Bearer 1e3ca62936ab9565d88cca21ffa1a8f614340cb94f1b7f15bef62193931b916c' \
--form 'aadhaar_share_code="3456"' \
--form 'merchant_id="8390925"' \
--form 'aadhaar_file=@"/path/to/your/aadhaar_xml_file.xml"'
Sample response
Success scenario
{
"status": "success",
"code": 200,
"message": "Aadhaar XML processed successfully",
"data": {
"reference_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"verification_status": "completed",
"merchant_id": "8390925",
"timestamp": "2023-05-27T10:15:30Z"
}
}
Failure scenarios
- Invalid share code
{
"status": "error",
"code": 400,
"message": "Invalid share code",
"data": null
}
- Invalid XML file
{
"status": "error",
"code": 400,
"message": "Invalid XML file",
"data": null
}
- Unauthorized access
{
"status": "error",
"code": 401,
"message": "Unauthorized access",
"data": null
}