m2pfintech
API LibraryUnknown

Request a physical card for an entity

Initiates a physical card issuance request for the specified entity. Optionally accepts address override, alias name, delivery type, plastic code, and branch ID. The controller is in credit-clms (CardConfigController).

POST
/Yappay/business-entity-manager/requestPhysicalCard

Header Parameters

TENANT*string

Tenant identifier for multi-tenancy routing

Request Body

application/json

entityId*string

The entity (account) ID for which the physical card is requested

kitNo?string

Kit number of the virtual card to convert to physical

plasticCode?string

Plastic code for card design; falls back to default if not provided

aliasName?string

Alias name to emboss on the card

fourthLine?string

Fourth line text on the card

branchId?string

Branch identifier for card delivery

addressCategory?string

Category of address to use for card delivery

Value in"PERMANENT" | "DELIVERY" | "COMMUNICATION" | "NRERELATIVE" | "CORPORATE" | "REGISTERED_ADDRESS" | "BRANCH_ADDRESS" | "BILLING_ADDRESS" | "BULK"
deliveryType?string

Delivery type for the physical card

Value in"RUSH" | "NORMAL" | "BULK"
addressDto?

Address override containing a list of AddressInfoDto objects

Response Body

application/json

application/json

application/json

application/json

curl -X POST "https://uat-m2p-ccms.m2pfintech.com/Yappay/business-entity-manager/requestPhysicalCard" \  -H "TENANT: string" \  -H "Content-Type: application/json" \  -d '{    "entityId": "CUST123456"  }'
{
  "status": 200,
  "result": true,
  "message": "Success"
}
{
  "status": 400,
  "message": "Invalid request parameters",
  "timestamp": "2019-08-24T14:15:22Z"
}
{
  "status": 400,
  "message": "Invalid request parameters",
  "timestamp": "2019-08-24T14:15:22Z"
}
{
  "status": 400,
  "message": "Invalid request parameters",
  "timestamp": "2019-08-24T14:15:22Z"
}

Preview outstanding balance before account closure (v2) POST

Validates and returns a preview of the outstanding balance and charges that would apply if the account were to be closed. Version 2 includes additional validation checks before returning the closure preview.

Fetch due amount via BBPS POST

Fetches outstanding due amount for a customer identified by their contact number and card number, intended for BBPS (Bharat Bill Payment System) integrations. Returns customer name alongside the standard due response.