| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Submit fresh biometric capture data for UPI ATM KYC.
POST https://pay2new.in/apis/upiAtm/v1/biometricKyc
Headers
| Header | Required | Description |
|---|---|---|
secret | Yes | Your Pay2New API secret. |
outletId | Yes | Pay2New outlet/customer ID returned after successful onboarding; do not send the provider outlet ID. |
Content-Type | Yes | application/json |
Accept | No | Request a JSON response. |
Requests require an active partner account, approved KYC, active wallet and API access, an allowlisted source IP, and the relevant service enabled.
JSON request
| Field | Required | Description |
|---|---|---|
referenceKey | Yes | Reference returned by the preceding status or OTP operation. |
latitude | Yes | Latitude as a decimal value. Accepted as a JSON number or decimal string. |
longitude | Yes | Longitude as a decimal value. Accepted as a JSON number or decimal string. |
request_id | Yes | Your reference for this request. At least 8 characters. |
biometricData | Yes | Fresh biometric capture object from the registered device. Pass the capture fields required by your integration; do not reuse sample or previous capture data. Include aadhaar_number (12 digits) and the fresh registered-device capture fields. Never substitute a sample capture. |
Usage notes
- Use referenceKey from UPI ATM Biometric Kyc Status and submit fresh registered-device data.
- request_id must have at least 8 characters and is echoed as order_id.
- Recheck Biometric Kyc Status to confirm APPROVED and NO-ACTION-REQUIRED.
Biometric request fields
Pass biometricData as a nested JSON object inside the request. Pay2New accepts aadhaar_number and creates the provider’s encryptedAadhaar internally. Keep sessionKey, pidData, rdsId and the other RD field names exactly as shown.
| JSON field | Value / RD mapping |
|---|---|
biometricData.aadhaar_number | Consenting customer/merchant Aadhaar number; exactly 12 digits. |
biometricData.dc | DeviceInfo.dc |
biometricData.ci | Skey.ci |
biometricData.hmac | Hmac element text |
biometricData.dpId | DeviceInfo.dpId |
biometricData.mc | DeviceInfo.mc |
biometricData.pidDataType | Data.type, for example X for XML |
biometricData.sessionKey | Skey element text |
biometricData.mi | DeviceInfo.mi |
biometricData.rdsId | DeviceInfo.rdsId |
biometricData.errCode | Resp.errCode |
biometricData.errInfo | Resp.errInfo |
biometricData.fCount | Resp.fCount |
biometricData.fType | Resp.fType |
biometricData.iCount | Resp.iCount |
biometricData.iType | Resp.iType |
biometricData.pCount | Resp.pCount |
biometricData.pType | Resp.pType |
biometricData.srno | DeviceInfo/additional_info device serial value |
biometricData.sysid | DeviceInfo/additional_info system ID, when supplied |
biometricData.ts | Capture timestamp returned by the RD integration, when supplied |
biometricData.pidData | Data element text (encrypted PID) |
biometricData.qScore | Resp.qScore |
biometricData.nmPoints | Resp.nmPoints |
biometricData.rdsVer | DeviceInfo.rdsVer |
Copy capture values from the RD response without altering their case or encrypted contents. Use the actual capture counts/types; the example is a fingerprint capture. Optional device metadata should reflect what your device supplies.
Format reference: Instantpay biometric request documentation. The request below uses Pay2New’s URL, authentication and field names.
Request example
Complete biometric sample
The sample below includes the full biometric field structure. Replace the illustrative customer/device values and encrypted-data placeholders with the values from a fresh registered-device capture. Keep the field names and their case; capture counts and types must match the actual device response.
All identities and account values below are synthetic. Replace placeholders, including the enabled product code and fresh device capture, before sending a request.
{
"referenceKey": "REFERENCE_FROM_PREVIOUS_RESPONSE",
"latitude": "18.5204",
"longitude": "73.8567",
"request_id": "EXAMPLE202609260001",
"biometricData": {
"aadhaar_number": "999999999999",
"dc": "SAMPLE_REGISTERED_DEVICE_CODE",
"ci": "20261231",
"hmac": "BASE64_ENCRYPTED_PID_HASH",
"dpId": "SAMPLE_DEVICE_PROVIDER_ID",
"mc": "BASE64_DEVICE_CERTIFICATE",
"pidDataType": "X",
"sessionKey": "BASE64_ENCRYPTED_SESSION_KEY",
"mi": "SAMPLE_DEVICE_MODEL",
"rdsId": "SAMPLE_RD_SERVICE_ID",
"errCode": "0",
"errInfo": "",
"fCount": "1",
"fType": "2",
"iCount": "0",
"iType": "",
"pCount": "0",
"pType": "",
"srno": "SAMPLE_DEVICE_SERIAL_NUMBER",
"sysid": "SAMPLE_SYSTEM_ID",
"ts": "2026-09-26T12:00:00+05:30",
"pidData": "BASE64_ENCRYPTED_PID_DATA",
"qScore": "100",
"nmPoints": "46",
"rdsVer": "SAMPLE_RD_SERVICE_VERSION"
}
}
Complete cURL request
curl --request POST \
--url 'https://pay2new.in/apis/upiAtm/v1/biometricKyc' \
--header 'secret: YOUR_PAY2NEW_SECRET' \
--header 'outletId: YOUR_PAY2NEW_OUTLET_ID' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--data '{
"referenceKey": "REFERENCE_FROM_PREVIOUS_RESPONSE",
"latitude": "18.5204",
"longitude": "73.8567",
"request_id": "EXAMPLE202609260001",
"biometricData": {
"aadhaar_number": "999999999999",
"dc": "SAMPLE_REGISTERED_DEVICE_CODE",
"ci": "20261231",
"hmac": "BASE64_ENCRYPTED_PID_HASH",
"dpId": "SAMPLE_DEVICE_PROVIDER_ID",
"mc": "BASE64_DEVICE_CERTIFICATE",
"pidDataType": "X",
"sessionKey": "BASE64_ENCRYPTED_SESSION_KEY",
"mi": "SAMPLE_DEVICE_MODEL",
"rdsId": "SAMPLE_RD_SERVICE_ID",
"errCode": "0",
"errInfo": "",
"fCount": "1",
"fType": "2",
"iCount": "0",
"iType": "",
"pCount": "0",
"pType": "",
"srno": "SAMPLE_DEVICE_SERIAL_NUMBER",
"sysid": "SAMPLE_SYSTEM_ID",
"ts": "2026-09-26T12:00:00+05:30",
"pidData": "BASE64_ENCRYPTED_PID_DATA",
"qScore": "100",
"nmPoints": "46",
"rdsVer": "SAMPLE_RD_SERVICE_VERSION"
}
}'
Response
Application status is returned in the JSON status field. A successful HTTP response alone does not confirm a successful operation.
| Field | Description |
|---|---|
status | integer: application status, not HTTP status |
message | string |
data | empty array |
order_id | string: same value as request_id |
Provider-dependent fields may be absent or null. status: 2 indicates a failure. For transaction endpoints, status: 3 indicates pending or uncertain processing and requires status confirmation.
Illustrative response:
{
"status": 1,
"message": "Success",
"data": [],
"order_id": "EXAMPLE202609260001"
}
Errors
Validation errors can include an errors object keyed by field name. Authentication, outlet, service and other processing errors can return only status and message. Errors are application-level responses; do not rely on an HTTP 400 status.
{
"status": 2,
"message": "Invalid Parameters",
"errors": {
"referenceKey": "Provide a valid value for this field."
}
}