Initiate an AEPS cash withdrawal.

POST https://pay2new.in/apis/aeps/v1/cashWithdrawal

Headers

Requests require an active partner account, approved KYC, active wallet and API access, an allowlisted source IP, and the relevant service enabled.

Withdrawals above ₹5,000: OTP process

The withdrawal amount must also be a multiple of ₹50. For example, ₹5,000 does not trigger this OTP rule; ₹5,050 and ₹6,000 do.

🚧

Where the customer OTP goes

There is no separate top-level otp field or AEPS OTP-validation request in this Pay2New flow. The OTP is supplied to the RD service before capture. Send the resulting encrypted biometricData together with referenceKey to Cash Withdrawal. Do not reuse a capture obtained before the OTP was included.

RD capture option

Add the otp attribute to your existing RD capture options. This fragment illustrates that attribute only; retain all other device-required capture attributes in the same Opts element.

<Opts otp="CUSTOMER_OTP" />

For the provider's RD instruction and on-us/off-us distinction, see AEPS Transaction OTP. Pay2New normalizes the provider status into status/message; use the Pay2New response fields documented here.

📘

Reference and validity

Use the referenceKey returned for the corresponding transaction and retain the returned validity. Do not hard-code an expiry duration. If the reference is missing, expired, or the response does not clearly identify the next action, resolve that condition before submitting the withdrawal.

JSON request

Usage notes

• The amount must be a multiple of ₹50.
• For amounts above ₹5,000, follow the OTP process above before submitting the withdrawal.
• captureType defaults to FINGER. Include iCount and pCount with the fresh biometric capture.
• If status is 3, confirm the existing transaction’s status before starting another withdrawal.

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.

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: ₹6,000 after the OTP step

📘

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.

{
  "amount": "6000.00",
  "bankiin": "000000",
  "latitude": "18.5204",
  "longitude": "73.8567",
  "customer_mobile": "9000000001",
  "request_id": "EXAMPLE202609260001",
  "product_code": "243",
  "referenceKey": "REFERENCE_KEY_FROM_TRANSACTION_OTP",
  "captureType": "FINGER",
  "ip": "192.0.2.10",
  "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_FROM_OTP_CAPTURE",
    "qScore": "100",
    "nmPoints": "46",
    "rdsVer": "SAMPLE_RD_SERVICE_VERSION"
  }
}

Complete cURL request

curl --request POST \
  --url 'https://pay2new.in/apis/aeps/v1/cashWithdrawal' \
  --header 'secret: YOUR_PAY2NEW_SECRET' \
  --header 'outletId: YOUR_PAY2NEW_OUTLET_ID' \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json' \
  --data '{
  "amount": "6000.00",
  "bankiin": "000000",
  "latitude": "18.5204",
  "longitude": "73.8567",
  "customer_mobile": "9000000001",
  "request_id": "EXAMPLE202609260001",
  "product_code": "243",
  "referenceKey": "REFERENCE_KEY_FROM_TRANSACTION_OTP",
  "captureType": "FINGER",
  "ip": "192.0.2.10",
  "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_FROM_OTP_CAPTURE",
    "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.

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",
  "order_id": "EXAMPLE_ORDER_001",
  "txn_value": "6000.00",
  "balance": "1000.00",
  "request_id": "EXAMPLE202609260001",
  "login_status": 1,
  "bank_reference": "EXAMPLE_BANK_REFERENCE",
  "account_balance": "1000.00",
  "bank_name": "Example Bank"
}

Amount and OTP errors

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": {
    "amount": "Provide a valid value for this field."
  }
}