Pending Collect Request Count
Returns the count of pending collect requests for the user. Use this to show a badge or notification count for pending collect requests that need the users attention (approve or decline).
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/transaction/pendingCollectRequest/count" \ -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": "604" }'{
"status": "SUCCESS",
"exception": null,
"seqNo": "604",
"result": {
"count": 3
}
}Fetch Transactions (Filtered) POST
Fetches UPI transactions with optional filters including date range, transaction type, status, and VPA. Supports pagination via offset and pageNo query parameters. More flexible than fetchRecentTransactions for reporting and search use cases.
Block or Unblock VPA for Collect Requests POST
Blocks or unblocks a specific VPA from sending collect requests to the user. When a VPA is blocked, any collect requests from that VPA will be automatically rejected. Supported actions are BLOCK and UNBLOCK.