Revoke a card

A POST request sent to revoke a card.
If a cardholder declares their card missing or stolen, or if fraudulent actions are verified,
you have the option to invalidate the card, ensuring it is permanently locked, and automatically reject any forthcoming transactions.

⚠️

Caution

Invalidating a card is irreversible. Once done, the card cannot be re-enabled.

Path Params
string
required

A Card identifier. Begins with 'crd-' followed by a v4 UUID

Body Params

Card object revoke information.

string
required

The reason why the card is revoked.

Responses

400

The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

401

Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.

403

The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.

422

The request was well-formed but was unable to be followed due to semantic errors.

429

The user has sent too many requests in a given amount of time ("rate limiting").

500

The server has encountered a situation it does not know how to handle.

Language
Choose an example:
application/json