---
title: "Update card information"
method: PATCH
path: "/wallet/v2/cards/{cardId}"
tags: ["Cards"]
---

# Update card information

`PATCH /wallet/v2/cards/{cardId}`

Update card information - `name`, `transaction_limit`, `printed_name`, `contactless_enabled`, `abu_enabled`, or `metadata`.<br>

This endpoint generates a [Card updated](https://developers.pismo.io/events/docs/cards-update-1) event.

**Note:** This endpoint takes an account token - an access token encoded with a Pismo account ID.

## Path parameters

- `cardId` string, required

## Headers

- `x-customer-id` integer, required

## Request body

- UpdateCard — Card update request object
  - `name` string — Card alias name for a `VIRTUAL` card. This field is **REQUIRED** to be unique for each `VIRTUAL` card a customer owns. No matter what is passed for a `PLASTIC` card, the value is always `PLASTIC`.
  - `printed_name` string — Printed name on physical card
  - `transaction_limit` string — Optional for virtual cards. Maximum amount allowed per transaction. Set up to the approved limit. If not set, account limit is used.
  - `contactless_enabled` boolean — For physical cards. Is card enabled for contactless transactions? With contactless transactions, you hold or tap the card on contactless-enabled card reader to complete a transaction. This requires that both the card and the terminal have Near Field Communication (NFC) technology. Most embossers can create plastic contactless cards. Default is `true`.
  - `abu_enabled` boolean — To delete a card from the ABU database, submit Mastercard ABU reason code `O` (optout), and Mastercard will delete the card and all previous references to the card data chain. This prevents further merchant notifications. Removing a card from the ABU database using reason code O (Optout) does not result in associated MDES tokens being deleted. Mastercard maintains an audit trail for all deleted cards. Set this field to `false`to optout.
  - `metadata` string — Any data object with key/value pairs. No limit on length. **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](https://developers.pismo.io/pismo-docs/reference/get-started-with-pismo-apis#metadata).

## Response `200`

Card update response object

- UpdateCardResponse — Response body for card update request
  - `id` integer — Card ID
  - `status` 'ACTIVE' | 'SUSPENDED' | 'PENDING' — Card status
  - `printed_name` string — Printed name on physical card
  - `name` string — Card alias name for a `VIRTUAL` card. This field is **REQUIRED** to be unique for each `VIRTUAL` card a customer owns. No matter what is passed for a `PLASTIC` card, the value is always `PLASTIC`.
  - `type` 'PLASTIC' | 'VIRTUAL' | 'RECURRING' | 'TEMPORARY' — Card type
  - `issuing_date` string — Date/time when card was issued in RFC3339 format, i.e., 2019-07-03T17:23:18Z
  - `transaction_limit` string — Optional for virtual cards. Maximum amount allowed per transaction. Set up to the approved limit. If not set, account limit is used.
  - `tracking` string — File sent to embosser tracking ID
  - `contactless_enabled` boolean — For physical cards. Is card enabled for contactless transactions? With contactless transactions, you hold or tap the card on contactless-enabled card reader to complete a transaction. This requires that both the card and the terminal have Near Field Communication (NFC) technology. Most embossers can create plastic contactless cards. Default is `true`.
  - `abu_enabled` boolean — This field is **DEPRECATED**. For more information, refer to the [ABU documentation](https://developers.pismo.io/pismo-docs/docs/cards-overview-1#mastercards-automatic-billing-updater-option) in the Cards overview guide. When a card is created or reissued, or its account credentials change, Mastercard is notified if this feaure is enabled. Notification updates are sent to Mastercard on a daily basis. For more information, refer to Mastercard's <a href="https://developer.mastercard.com/product/automatic-billing-updater-abu/" target="_blank">ABU</a> documentation.

## Other responses

- `401` — Access token is missing or invalid
- `403` — The request has been lost
- `409` — You already have a card with this type and name active
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)