Approve/Reject Forex Issuance
Approves or rejects a pending forex card issuance request. Works identically to the wallet issuance state transition endpoint.
Authorization
bearerAuth tenantId JWT Bearer token from the Authentication API
In: header
Your unique tenant identifier assigned during onboarding
In: header
Header Parameters
Your unique tenant identifier
Request Body
application/json
Required. Unique ID of the record to transition
1 <= lengthRequired. Target status
"APPROVED" | "REJECTED"Required. User performing the action
1 <= lengthState code
Description of the action
Reasons for the decision
Response Body
application/json
application/json
curl -X POST "https://sandbox-api.m2pprepaid.com/prepaid/middleware/v1/forex/issuance/state-transition" \ -H "X-TENANT-ID: ACME_CORP" \ -H "Content-Type: application/json" \ -d '{ "id": "69020e047cf39e1b08090490", "toStatus": "APPROVED", "userId": "CHECKER_001", "stateDescription": "Documents verified" }'{
"result": {},
"pagination": {
"list": true,
"pageSize": 0,
"pageNo": 0,
"totalPages": 0,
"totalElements": 0
}
}{
"type": "https://www.m2pfintech.com/problem/problem-with-message",
"title": "Your issuance was declined as you have exceeded the monthly purchaser permissible number",
"status": 409,
"detail": "Your issuance was declined as you have exceeded the monthly purchaser permissible number",
"message": "error.business",
"businessCode": "PP_CORP_181"
}Fetch Issuances by Criteria POST
Advanced search endpoint that lets the portal filter issuances by any combination of status, hierarchy, and a dynamic field/value pair (e.g., search by `applicationNumber`, `mobile`, `pan`, etc.). ### Use Cases - Search issuances by customer PAN or mobile number - Filter all `FAILED` issuances within a specific branch - Build the "search" feature in the issuance management dashboard ### `type` (DataType) Values `STRING` | `INTEGER` | `BIGDECIMAL` | `BOOLEAN` | `DATE` | `ENCRYPTED` ### Server Use the **corporate** server URLs for this endpoint.
Issue Add-on Card POST
Issues a new add-on (supplementary) card linked to an existing primary card account. Add-on cards share the same account and balance as the parent card. ### Use Cases - Corporate employee card with supplementary card for spouse - Parent card with add-on for family member - Replacement card with different embossing ### Prerequisites - Parent card must be `ACTIVE` - Add-on card feature must be enabled for the hierarchy - Must not exceed configured add-on card limit ### Server Use the **corporate** server URLs for this endpoint.
