Regeneration of PIN Mailer
Regenerates a PIN mailer for an existing card. A PIN mailer is a physical document sent to the customer containing their card PIN. The addressType specifies which address (PERMANENT or COMMUNICATION) to use for delivery. The homeCurrencyCode is required for 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.
Request Body
application/json
Customer entity identifier who owns the card.
Kit number of the card for which PIN mailer is being regenerated.
Address type for PIN mailer delivery.
"PERMANENT" | "COMMUNICATION"ISO currency code for the home country.
Response Body
application/json
curl -X POST "https://api.dcms.example.com/v1/kit-manager/regeneratePinMailer" \ -H "tenant: ACME_BANK" \ -H "Content-Type: application/json" \ -d '{ "entityId": "676765", "kitNo": "4561789", "addressType": "COMMUNICATION", "homeCurrencyCode": "564" }'{
"result": {
"entityId": "676765",
"kitNo": "4561789",
"addressType": "COMMUNICATION",
"homeCurrencyCode": "564",
"pinRegenerationStatus": true
},
"exception": null,
"pagination": null
}Manage Existing Kits POST
Manages existing card kits by performing lifecycle operations such as BLOCK, LOCK, UNLOCK, REPLACE, and BLOCK_AND_REPLACE. LOCK temporarily disables the card and can be reversed with UNLOCK. BLOCK permanently disables the card. REPLACE issues a new card to replace the existing one. BLOCK_AND_REPLACE blocks the current card and issues a replacement in one operation. For REPLACE and BLOCK_AND_REPLACE operations, the cardType and deliveryAddress fields may be required.
Set PIN POST
Sets the PIN for a card. The PIN must be encrypted using the shared encryption algorithm before calling this API. The encrypted PIN should be generated by first creating a PIN block, then encrypting it. The expiryDate must match the card expiry date in MMYY format.