Bind a card to its verification and issuer master keys and return its codes once
/cards/{id}/personalizationVerified bank staff with cards:read observe the registry; opening a ceremony, entering a component, personalising a card and unlocking a PIN take the narrow cards:security:write and a step-up in the last five minutes, never cards:write. Approving another member of staff's ceremony adds cards:security:approve. The maker never approves their own ceremony and never enters a component. Both HSM adapters are simulators and are refused in prod. The CVV, CVV2 and iCVV are returned once and never stored.
Path parameters
idstringRequiredHeaders
Idempotency-KeystringRequiredSend on every write that creates or changes money or state; a replay with the same key returns the original result with 200.
Body parameters
cvk_key_idstringRequiredimk_key_idstringOptionalpan_sequencestringOptionalReturns
200 OK
bindingobjectRequiredCardSecurityBinding is what personalisation fixed for one card.
8 child attributes
card_idstringRequiredExample card_2tVh8nqLxq4GbDe0K1F6S9zRcWm
cvk_key_idstringRequiredimk_key_idstringOptionallast_atcintegerRequiredpan_sequencestringRequiredpersonalized_atstring · date-timeRequiredpersonalized_bystringRequiredupdated_atstring · date-timeRequiredcvvstringOptionalcvv2stringOptionalicvvstringOptionalErrors
Every error is a problem document with a stable code. See Errors.
400401403404409412413422424429500503