Sync PENDING Card Order Statuses from CMS
Fetches all orders that are in PENDING status, calls the CMS status API for each, and updates the local status. This is a bulk synchronization endpoint used to keep local order statuses in sync with CMS processing. CMS returns PENDING, PROCESSED, or FAILED for each order.
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.
Response Body
application/json
curl -X POST "https://api.dcms.example.com/v1/card-order/sync-pending-status" \ -H "tenant: ACME_BANK"{
"result": true,
"exception": null,
"pagination": null
}Retry Stuck PENDING Card Orders POST
Fetches all orders that have been in PENDING status beyond a configurable time threshold and retries placing them via CMS. This is a recovery mechanism for orders that may have gotten stuck during processing.
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.