Bind SIM (Alternative Method)
Alternative SIM binding method available for specific integration patterns. This performs the same function as the simBindReq and checkSimBindStatus flow but as a single synchronous call. Available for select partner configurations only.
Request Body
application/json
Device and SIM information required for UPI API authentication and tracking
Channel or institution code assigned by M2P during onboarding
Sequence number for request tracking
Response Body
application/json
curl -X POST "https://sandbox-upi-api.m2pfintech.com/upi/v1/wrapper/profile/bindSim" \ -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": "310" }'{
"status": "SUCCESS",
"exception": null,
"seqNo": "310",
"message": "Sim binding success",
"result": {
"id": "c82e4f19-7b3a-4d6e-9f01-ab3456789def",
"mobile": "919876501234"
}
}Add Account POST
Links a bank account to the users UPI profile. The account must have been discovered via accountFetchReq/accountFetchRes or listAccounts first. After adding, the account can be used for UPI transactions. Maximum account limit is configurable per tenant. Re-adding a recently deleted account may have a cooldown period.
Delete Account POST
Removes a linked bank account from the users UPI profile. The primary account cannot be deleted - change the primary account first. Deleting the last remaining account is also handled based on business rules.