| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Validate the OTP for an Aadhaar verification request. Use the order_id and ref_id returned by the initiation API.
Endpoint
POST https://pay2new.in/apis/v1/verification/aadhaarValidate
Headers
| Header | Required | Value / description |
|---|---|---|
secret | Yes | Your Pay2New API secret. Keep it on your server. |
Content-Type | Yes for JSON requests | application/json |
Accept | Optional | application/json |
Authentication
Use an active Pay2New partner account with verified KYC, an active wallet and API access. Send requests from your registered IP address. Enable the relevant service where applicable; offer services may also require an active plan.
Request body
| Field | Type | Required | Description |
|---|---|---|---|
ref_id | string | Yes | ref_id returned by Aadhaar Verification initiation. |
otp | string | Yes | Numeric OTP supplied by the customer. |
order_id | string | Yes | order_id returned by Aadhaar Verification initiation. |
request_id | string | Yes | Unique client reference for this request. Store it for reconciliation and support. Minimum 8 characters. |
Request example
Illustrative values
All identifiers, identity data, amounts and IP addresses in these examples are synthetic. Replace the secret, product/customer references and sample inputs with the values for your integration before sending a request.
curl --request POST \
--url 'https://pay2new.in/apis/v1/verification/aadhaarValidate' \
--header 'secret: <YOUR_PAY2NEW_SECRET>' \
--header 'Content-Type: application/json' \
--data '{
"ref_id": "EXAMPLE_AADHAAR_REFERENCE",
"otp": "123456",
"order_id": "P2N_EXAMPLE_AADHAAR",
"request_id": "EXAMPLE202609260001"
}'
Response fields
| Field | Type | Description |
|---|---|---|
status | integer | 1: successful operation; 2: failed/rejected operation; 3: pending or indeterminate where returned. |
message | string | Human-readable result or error message. |
order_id | string | Pay2New transaction/order reference. Store it for reconciliation. |
request_id | string | Client request reference associated with the operation. |
data | object / array | Service/provider response data. Available keys depend on the selected product and verification source; allow missing or null optional fields. |
Response example
{
"status": 1,
"message": "Transaction Successful!",
"order_id": "P2N_EXAMPLE_VALIDATION",
"request_id": "EXAMPLE202609260002",
"data": {}
}
Integration notes
This call uses the initiation order_id as input and returns a new validation order_id. Store the new value for reconciliation. ip is not a required input for this endpoint.
Errors
Application failures return status: 2 and a message. Invalid fields can also be identified in an errors object. Authentication, IP registration, service access and product availability can prevent processing. Other response fields may be absent when processing fails before a transaction is created. Evaluate the JSON result even when the HTTP request completes successfully. Preserve your request and order references when an outcome is pending or indeterminate.
{
"status": 2,
"message": "Invalid Parameters",
"errors": {
"ref_id": "Illustrative field validation message"
}
}