--- title: "Update card information" method: PATCH path: "/wallet/v2/cards/{cardId}" tags: ["Cards"] --- # Update card information `PATCH /wallet/v2/cards/{cardId}` ## Request - Base URL: `https://sandbox.pismolabs.io` - URL: `https://sandbox.pismolabs.io/wallet/v2/cards/{cardId}` - Auth: HTTP bearer Update card information - `name`, `transaction_limit`, `printed_name`, `contactless_enabled`, `abu_enabled`, or `metadata`.
This endpoint generates a [Card updated](https://developers.pismo.io/events/docs/cards-update-1) event. **Note:** This endpoint requires 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/embossed card name. Currently, you have 3 ways to populate this field: 1. During account creation via the `application.applicant.personal.social_name` field. 2. During account creation via the `application.applicant.personal.name` field when the field in #1 is not set. 3. Passing the `printed_name` field during card creation, updating a card, or when reissuing a card. This takes priority over #1 and #2. No letters with accents, numbers, or special characters - only letters (a-z|A-Z) and space, as specified in the ISO EMV tag 5F20 for cardholder name. **REQUIRED** for an `UNNUMBERED` card (Card created without PIN or PAN that issuer defines at some point in the future.) - `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` Metadata: Any key-value object. Max length = 3200 bytes. This **must** be valid JSON data. **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](ref:get-started-with-pismo-apis#metadata). ## Response `200` Card update response object - UpdateCardResponse: Response body for card update request - `id` integer: Card ID - `status` string: Card status enum. Refer to the [Card lifecycle and statuses](doc:card-lifecycle-and-statuses) guide for more information and a complete list. - `printed_name` string: Printed/embossed card name. Currently, you have 3 ways to populate this field: 1. During account creation via the `application.applicant.personal.social_name` field. 2. During account creation via the `application.applicant.personal.name` field when the field in #1 is not set. 3. Passing the `printed_name` field during card creation, updating a card, or when reissuing a card. This takes priority over #1 and #2. No letters with accents, numbers, or special characters - only letters (a-z|A-Z) and space, as specified in the ISO EMV tag 5F20 for cardholder name. **REQUIRED** for an `UNNUMBERED` card (Card created without PIN or PAN that issuer defines at some point in the future.) - `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 enum: * `PLASTIC` - Physical card - plastic or metal. * `VIRTUAL` - Digital card with fixed PAN and dynamic CVV. * `TEMPORARY` - Virtual card with a fixed PAN and CVV meant for short-term use, typically 24 hours. For more information, refer to [Configuring temporary cards](https://developers.pismo.io/pismo-docs/docs/cards-overview-1#configuring-temporary-cards) in the Cards management guide. * `RECURRING` - Virtual card with a fixed PAN and CVV originally meant for use with recurring subscriptions. This type is being **DEPRECATED** and it is recommended you use `VIRTUAL` instead. - `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](doc: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 ABU documentation. ## Other responses - `401`: Access token is missing or invalid - `403`: You don't have permission to access this resource - `409`: You already have a card with this type and name active - `500`: Internal server error --- [API](https://skmtc.dev/pismo/apis/card-issuing-cards.md) - [All operations](https://skmtc.dev/pismo/apis/card-issuing-cards/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/card-issuing-cards/revisions/05611ac051b0?raw)