Kit Activation
Activates a card kit that is in INACTIVE or ASSIGNED status. Once activated, the card becomes ready for use in transactions. Both entityId and kitNo are required to identify the specific card to activate.
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 owns the card.
Kit number of the card to activate.
Response Body
application/json
application/json
curl -X POST "https://api.dcms.example.com/v1/kit-manager/kitActivation" \ -H "tenant: ACME_BANK" \ -H "Content-Type: application/json" \ -d '{ "entityId": "req7", "kitNo": "4240171508" }'{
"result": "success",
"exception": null,
"pagination": null
}{
"result": null,
"exception": {
"errorCode": "MCC007",
"shortMessage": "valid kit not found",
"detailMessage": "No valid kit found for the given kit number and entity ID",
"httpStatus": "BAD_REQUEST",
"fieldError": [
"Invalid Kit No"
],
"languageCode": "en"
},
"pagination": null
}Get CVV POST
Retrieves the CVV (Card Verification Value) for a card identified by its kit number. The response includes the CVV value and its expiry time in seconds. The CVV is time-limited and must be used before the expiryCvv time elapses. This is typically used for virtual card transactions where the customer needs to view the CVV.
Kit Tracking POST
Tracks the delivery status of a card kit that was issued. Returns detailed shipment tracking information from the delivery service provider including origin, destination, expected delivery date, current status, and a full scan history showing each transit point the shipment has passed through.