Skip to main content
PATCH
Update card
Changes apply to every authorization from the moment the request succeeds, and the card keeps its number and history. If any part of the request is invalid, the whole request is rejected and the card stays as it was. You can only update cards your platform issued: a card issued by the entity’s staff in the Lemma app returns a 404. A canceled card returns a 409. Send one update to a card at a time. Each update starts from the card’s current controls, so two sent at once can overwrite each other.

Headers

string
required
A key that prevents applying the same update twice if the request is retried. Reusing a key on the same card returns the card’s current state instead of updating it again; reusing it on a different card returns a 422. See Idempotency.

Path parameters

string
required
The card’s unique identifier.

Request body

Set status, authorization_controls, or both. A body with neither returns a 400.
enum
Freezes or unfreezes the card. Omit it to keep the card’s current status. canceled is not accepted; use Cancel a card instead.
object
The controls to change. Omit it to keep every control. When sent, it must set usage, merchant_category_code, or both, and the one you omit keeps its current value.

Response

Returns the updated card object.
string
Unique identifier for the card, prefixed with card_.
string
ISO 8601 timestamp of when the card was created.
string
The ID of the entity that owns this card.
string
The bank account this card draws from.
string
The human-readable label for this card.
string
The last 4 digits of the card number.
enum
The card’s status.
object
Every control restricting how this card can be used, including the ones Lemma applies to every card it issues.