Confirm the mobile-number change using OTPs for the existing and new mobile numbers.

POST https://pay2new.in/apis/v1/onboard/customer/validateMobile

Headers

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

JSON request

Usage notes

• Requires an enabled AEPS service. Submit both six-digit OTPs.

Request example

All identities and account values below are synthetic. Replace placeholders, including the enabled product code and fresh device capture, before sending a request.

{
  "existing_mobile": "9000000001",
  "new_mobile": "9000000002",
  "existing_mobile_otp": "123456",
  "new_mobile_otp": "654321"
}

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": null
}

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