Request Mobile Registration
Initiates mobile number registration with the UPI platform via NPCI. This is the formal registration of the mobile number on UPI rails. Used during initial onboarding after SIM binding is complete. The registration is processed through NPCI and upon success, the user is registered on the UPI network.
Request Body
application/json
Device and SIM information required for UPI API authentication and tracking
Response Body
application/json
curl -X POST "https://sandbox-upi-api.m2pfintech.com/upi/v1/wrapper/profile/reqregmob" \ -H "Content-Type: application/json" \ -d '{ "deviceInfo": { "deviceId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "simId": "8991101200003204510", "deviceType": "MOB", "os": "Android", "telecom": "Airtel", "geoCode": "13.0827,80.2707", "appId": "v2.0", "ipAddress": "192.168.1.50", "location": "Mumbai", "mobile": "919876501234" }, "channelCode": "HDFC0001234", "seqNo": "902" }'{
"status": "SUCCESS",
"exception": null,
"seqNo": "902",
"callbackRef": null,
"message": "Mobile registered successfully",
"result": {
"refNumber": "REF12345",
"mobile": "919876501234"
}
}Get User Profile POST
Retrieves the complete user profile including personal details, linked VPAs, linked bank accounts, merchant information, delegate details, and feature flags. This is the primary API to get the current state of the user in the M2P UPI platform.
Validate Address Format POST
Validates the format of a VPA or UPI address. Checks if the address follows the correct format rules including character restrictions, length constraints, and handle validity. Use this for client-side validation before making API calls.
