Update card information

patch

https://sandbox.pismolabs.io/wallet/v2/cards/{cardId}

Update card information - name, transaction_limit, printed_name, contactless_enabled, abu_enabled, or metadata.

This endpoint generates an Card updated event.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

cardId

string

required

Pismo card ID

Body Params

Request body

Card update request object

name

string

length between 1 and 50

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

length between 2 and 26

Printed/embossed card name.

Currently, you have 3 ways to populate this field:

During account creation via the application.applicant.personal.social_name field.
During account creation via the application.applicant.personal.name field when the field in #1 is not set.
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

Defaults to true

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 falseto optout.

metadata

object

Any key-value object. Max length = 3200 bytes. This must be valid JSON data.

Headers

x-customer-id

integer

required

Pismo customer ID

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

Update card information

Changelog

Support

Pismo is here to help

200Card update response object