Update a card by ID

Updates card attributes including status, PIN, PIN retry count, and spending rules. PIN changes require the caller to be PCI compliant or to supply a valid Card Access Password (CAP).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
int64
required
int64
required
Body Params

All things that can be updated on a card. Used for PUT to change a card's behaviour

string

Optional,The card access password of the customer. Required if no JWT is provided and want to update card.

string

Allows the update of cardholder name associated with the card

cardRules
object

Optional. If passed then any non null rules will be set on the card

string
enum

Optional: The lifecycle status of the card can only be ACTIVE or INACTIVE e.g. On Pn the card can be on status ACTIVE with hold response code RESTRICTED

Allowed:
limitConfiguration
array of objects
limitConfiguration
string
length between 4 and 4

The initial or updated PIN to set on the card. Dont pass this parameter to leave PIN as-is

string
length between 1 and 32

Optional. The PINBlock encrypted under Terminal PIN Key (TPK). The PINBlock would be translated to ZPK Encryption for transportation

string
enum

Optional. The PINBlock format for the PINBlock encrypted under TPK

Allowed:
int32

Pass as 0 to reset the incorrect pin retry counter to 0. Any other value is ignored

string

Allows the update of card program name associated with the card

string
enum

If changed the status of card than must need to specify the reason

string

Allows the update of sov name for cards migrated to Eclipse as SOV

string
enum

Optional. If passed then the status will be changed. For detailed status change rules refer to the API spec documentation

boolean

Optionally disable syncing card with remote by default its synced

int64

Allows the update of userId associated with the card

virtualCardIdentifier
object

If it is provided then it must be an identifier for an unused virtual card

Responses

400

Bad Request

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json