Apply For A Card
Applies for a new physical card when no card is available for the customer, or converts an existing virtual card to a physical card. When a kitNo is provided, the existing virtual card is converted to physical. When only entityId is provided without kitNo, a fresh physical card is issued. The deliveryAddress field specifies which address type (PERMANENT or COMMUNICATION) to use for card delivery.
Authorization
tenantAuth The DCMS tenant name for multi-tenant isolation. Every API call must include this header to identify the client organization.
In: header
Header Parameters
The DCMS client or tenant name for multi-tenant isolation.
Request Body
application/json
Customer entity identifier who is applying for the card.
Existing virtual card kit number to convert to physical. Omit for a new card issuance.
Address type to use for card delivery. Can be PERMANENT or COMMUNICATION.
"PERMANENT" | "COMMUNICATION"Response Body
application/json
curl -X POST "https://api.dcms.example.com/v1/kit-manager/applyForCard" \ -H "tenant: ACME_BANK" \ -H "Content-Type: application/json" \ -d '{ "entityId": "req11", "kitNo": "4240171531", "deliveryAddress": "PERMANENT" }'{
"result": {
"entityId": "req11",
"kitInfo": [
{
"accountNo": 8642135,
"bin": "608040",
"cardCategory": "DEBIT",
"cardConversionDate": "2023-12-19 06:42:07",
"cardNumber": "608040XXXXXX5743",
"cardStatus": "INACTIVE",
"cardType": "PHYSICAL",
"createdDate": "2023-12-19T06:41:20.361+00:00",
"encryptedCardNumber": "6855d277be0ad117403c9edd0b54556a531dc5bf07d01e0a532d7131f0782b31",
"entityId": "req11",
"expDate": "2029-07-31T00:00:00.000+00:00",
"kitNo": "4240171531",
"networkType": "RUPAY",
"productId": "2003_PHYSICAL",
"productName": "2003_PHYSICAL"
}
]
},
"exception": null,
"pagination": null
}Update Branch PUT
Updates an existing branch record with the provided details. Only the branchId is mandatory to identify which branch to update. All other fields are optional and will be updated only if provided in the request body. The changer field can be used to record who performed the update for audit purposes.
Fetch Card Details by Card Number V2 POST
Retrieves detailed card and account information using an encrypted card number. The card number must be encrypted using AES-GCM encryption with the shared encryption key. The algorithm uses a 16-byte random IV and 128-bit authentication tag. The encrypted value should be Base64 encoded with the IV prepended to the ciphertext. Returns full card details including account information, card preferences, toggle settings, and the last PIN change date.