Payonclick Developer Docs
v1

Aadhaar OTP (above ₹5,000)

POST https://payonclick.in/ext/v1/aeps/otp
Requires aeps Signed request Counts toward your 60 req/min

NPCI-mandated customer OTP for a CW or AP above ₹5,000 — before capture


Body Params

NameTypeDescription
merchant_ref required string The outlet
service required string CW or AP
aadhaar required string Customer’s 12-digit Aadhaar
bank_iin required string From GET /banks
amount required number Must be above ₹5,000
customer_mobile required string Customer’s 10-digit mobile
latitude required number Outlet GPS latitude
longitude required number Outlet GPS longitude

Responses

StatusDescription
200 OK NPCI-mandated customer OTP for a CW or AP above ₹5,000 — before capture — see the example on the right.
4xx / 5xx { "success": false, "error": { "code": "…", "message": "…" } } — every code is listed under Error Codes.
🔏
This call must be signed

POST carries an X-Signature header over POST\n/ext/v1/aeps/otp\n{TIMESTAMP}\n{BODY_SHA256}. The samples on the right compute it for you; the rules are in Request Signing.

📘
Good to know

The OTP goes to the mobile registered with the customer’s Aadhaar. Put it into the capture’s PidOptions (pid_options_with_otp, otp="…") — it travels sealed inside the PID block and is never sent to us — then send otp_reference with the transaction. Amounts of ₹5,000 or less need no OTP.