Get card list for a customer
Retrieves all cards associated with a customer identified by customerId. Returns card details including kit number, BIN, card type, card status, card registration status, expiry date, network type, product code, and card category. The controller is in credit-clms (CardConfigController).
Header Parameters
Tenant identifier for multi-tenancy routing
Request Body
application/json
The customer ID (account ID) for whom the card list is fetched
Response Body
application/json
application/json
application/json
application/json
curl -X POST "https://uat-m2p-ccms.m2pfintech.com/Yappay/business-entity-manager/getCardList" \ -H "TENANT: string" \ -H "Content-Type: application/json" \ -d '{ "customerId": "CUST123456" }'{
"status": 200,
"result": {
"aliasName": "string",
"blockCode": [
"string"
],
"dob": "01011990",
"name": "string",
"entityId": "string",
"cardList": [
{
"kitNo": "string",
"bin": "string",
"cardType": "string",
"cardStatus": "string",
"cardRegistrationStatus": "string",
"expiryDate": "12/27",
"networkType": "string",
"productCode": "string",
"cardCategory": "string"
}
]
},
"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"
}Fetch a transaction by its transaction ID GET
Retrieves a single transaction record identified by the given txnId path parameter. NOTE: This endpoint path was not found in the available source code of credit-clms, credit-customer-service, or credit-service. It may exist in a service not present in this codebase snapshot.
Get card list (v3) for a customer POST
Retrieves the list of cards associated with a customer (v3 variant). NOTE: This endpoint path was not found in the available source code of credit-clms, credit-customer-service, or credit-service. It may exist in a service not present in this codebase snapshot or may be a planned/upcoming endpoint. Based on the v1 getCardList pattern, it accepts a customerId and returns card list data.