📘

Before you call this API

Send your issued secret header and Content-Type: application/json. Your source IP must be registered on the partner account, and the account, KYC, wallet, API access, and DigiLocker service must be active. The body ip field does not replace the source-IP check.

Checks whether the supplied mobile number is associated with a DigiLocker account. Use the result to select signin or signup when creating the consent URL.

POST https://pay2new.in/apis/v1/verification/digilocker/verifyAccount

Request fields

cURL example

curl --request POST \
  --url 'https://pay2new.in/apis/v1/verification/digilocker/verifyAccount' \
  --header 'secret: <YOUR_PAY2NEW_SECRET>' \
  --header 'Content-Type: application/json' \
  --data '{
    "mobile_number": "9999999999",
    "latitude": "19.0760",
    "longitude": "72.8777",
    "ip": "203.0.113.10",
    "request_id": "DLACC202608260001"
  }'

Success response example

{
  "status": 1,
  "message": "Success",
  "operator_reference": 12345678,
  "data": {
    "verification_id": "DLV202608260001",
    "mobile_number": "9999999999",
    "status": "ACCOUNT_EXISTS",
    "digilocker_id": "8aa626bf-34aa-5ffc-a123-f69207e129a7"
  }
}

🚧

Check the application result

Always inspect JSON status, message, and any errors object. A successful HTTP response does not establish verification completion. Invalid JSON, invalid parameters, authentication failure, or unavailable service can return status: 2. For field validation errors, errors maps field names to messages.

See the Verification Integration Guide for the full consent journey, status handling, and examples.