Retry Stuck PENDING Card Orders
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.
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/retry-stuck-pending" \ -H "tenant: ACME_BANK"{
"result": true,
"exception": null,
"pagination": null
}Process a Card Order via CMS POST
Processes a single RECEIVED card order by sending it to the CMS API for card generation. The order will be marked as SUCCESS or FAILED based on the CMS processing result.
Sync PENDING Card Order Statuses from CMS POST
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.