Upload Card Order File
Uploads a card order file in TXT format for processing. The file will be validated, stored, and prepared for card order creation. Use this API before calling the card-order/withFile endpoint. The file is uploaded as multipart form data.
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
multipart/form-data
The card order file in TXT format to upload.
Response Body
application/json
application/json
curl -X POST "https://api.dcms.example.com/v1/card-order/uploadFile" \ -H "tenant: ACME_BANK"{
"result": {
"fileName": "Insta_PGK_Format_With_check_File.txt",
"status": "success"
},
"exception": null,
"pagination": null
}{
"result": null,
"exception": {
"errorCode": "ORD002",
"shortMessage": "File upload failed",
"detailMessage": "The uploaded file is invalid or has incorrect format",
"httpStatus": "BAD_REQUEST",
"fieldError": [
"Invalid file format"
],
"languageCode": "en"
},
"pagination": null
}Update Card Order Status from CMS POST
Calls the CMS (Card Management System) status API for a given card order and updates the local order status accordingly. CMS returns statuses such as PENDING, PROCESSED, or FAILED. This is used to synchronize the local order status with the CMS processing status.
Fetch NCMC Preference POST
Retrieves the current NCMC preference settings for a specific card including auto-reload configuration, associated account number, and audit timestamps.