API LibraryIssuance

Approve/Reject Issuance in Bulk

In a bulk corporate issuance, selectively rejects specific beneficiaries by their mobile numbers. All other beneficiaries in the application are automatically approved.

Use Case

Bulk corporate issuance with 100 beneficiaries
Compliance team identifies 5 that should be rejected
Call this endpoint with those 5 mobile numbers
The other 95 are auto-approved

Authorization

bearerAuth tenantId

AuthorizationBearer <token>

JWT Bearer token from the Authentication API

In: header

X-TENANT-ID<token>

Your unique tenant identifier assigned during onboarding

In: header

Path Parameters

applicationNumber*string

Application number of the corporate issuance

Header Parameters

X-TENANT-ID*string

Your unique tenant identifier

Request Body

application/json

Response Body

`application/json`

`application/json`

curl -X POST "https://sandbox-api.m2pprepaid.com/prepaid/middleware/v1/corporate-issuances/reject-beneficiaries/gpr020" \  -H "X-TENANT-ID: ACME_CORP" \  -H "Content-Type: application/json" \  -d '[    "9876543210",    "9876543211"  ]'

{
  "result": {},
  "pagination": {
    "list": true,
    "pageSize": 0,
    "pageNo": 0,
    "totalPages": 0,
    "totalElements": 0
  }
}

Empty

{
  "type": "https://www.m2pfintech.com/problem/problem-with-message",
  "title": "string",
  "status": 0,
  "detail": "string",
  "message": "error.http.400",
  "businessCode": "string",
  "fieldErrors": [
    {
      "field": "string",
      "message": "string"
    }
  ],
  "cause": {},
  "errorCode": "string",
  "errors": [
    "string"
  ],
  "languageCode": "string",
  "localizedMessage": "string",
  "suppressed": [
    {}
  ]
}

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.

Check Card Application Status POST

Checks the overall status of a card issuance application. While the Card Delivery Tracking API focuses on physical delivery, this API provides the broader application status including KYC verification, card printing, and fulfillment stages. ### Application Statuses | Status | Description | |--------|-------------| | `INITIATED` | Application received and being processed | | `KYC_PENDING` | Waiting for KYC verification | | `KYC_APPROVED` | KYC verification completed successfully | | `CARD_PRINTING` | Physical card is being printed | | `READY_FOR_DISPATCH` | Card printed and ready to be shipped | | `DISPATCHED` | Card has been handed over to courier/branch | | `DELIVERED` | Card successfully delivered | | `ACTIVATED` | Card has been activated by the cardholder | | `REJECTED` | Application was rejected | | `FAILED` | Processing failed — contact support |