PIpismo
Card reissue

Reissue card

Reissue a physical (plastic/metal) or virtual card for a given customer/account.

For information on card reissue scenarios and statuses, refer to the Card reissuing guide.

This endpoint generates a Card updated event for the old card, and a Card created event for the new card. The Card created event is generated asynchronously - any operation that tries to access a card before this event, such as update password or get PCI information, is going to return a 404, not found error.

Notes:

  • If an attempt is made to reissue a card that has already been reissued, the new card's data created in the previous reissue is returned, that is, another card is not created and events are not generated.
  • To update the new card with the old card's PIN, call Get password for the old card, then update the new card's password with Change card password
  • To transfer tokens to the new card, set the update_tokens field to true. You can also do this later with the Transfer card tokens to other card endpoint.
  • Currently, there is no way to transfer a card's PAN
  • This endpoint requires an account token—an access token encoded with a Pismo account ID.
post/wallet/v1/customers/{customerId}/accounts/{accountId}/cards/{cardId}/reissue

Request

  • Base URL
    https://sandbox.pismolabs.io
  • URL
    https://sandbox.pismolabs.io/wallet/v1/customers/{customerId}/accounts/{accountId}/cards/{cardId}/reissue
  • Auth
    HTTP bearer

Path parameters

customerIdstring required

Customer ID

accountIdinteger required

Pismo account ID

cardIdstring required

Pismo card ID

Headers

x-idempotency-keystring

A unique identifier to ensure the operation remains idempotent, allowing for operation repetition without causing unintended effects or duplication. An idempotent operation is one that can be applied multiple times, yet the outcome remains the same. it ensures that network errors, retries, or failures can occur without introducing inconsistencies. 36 chars max.

Request body

reason_idinteger required

Reissue reason identifier. You can get reason IDs using the List reissue reasons endpoint. The must_block flag comes from the reissue reason object.

printed_namestring

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 <a href="https://emvlab.org/emvtags/show/t5F20/" target="_blank">ISO EMV tag 5F20</a> for cardholder name.

REQUIRED for an UNNUMBERED card (Card created without PIN or PAN that issuer defines at some point in the future.)

pin_length4 | 6

PIN length - 4 or 6 digits. Default is 4.

cvv_rotation_interval_hoursinteger

<b>REQUIRED</b> for a virtual card. Virtual card CVV rotation interval in hours.

To force a rotation manually, call the Rotate virtual card CVV endpoint.

If 0 is passed, the CVV will NOT be rotated.

embossing_groupstring

Embossing group name. Clients can work with multi-embossers. You can use this field to notify an embosser about a card request. If this parameter is not passed, and you work with multi-embossers, the default embosser is used. For more information, refer to the Physical card embossing guide.

embossing_custom_fieldstring

For physical cards. Additional information for embossing company. For example: tracking number or whether the card should be plastic or metal.

You can use this field for any embossing needs specific to your business. Whatever is sent must be agreed upon with the embosser—what to send, what values to send, what format to send, what size to send for each value, and so on.

contactless_enabledboolean

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.

metadataMetadata

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.

abu_enabledboolean

This field is DEPRECATED. For more information, refer to the ABU documentation 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.

template_idstring

Template ID. Templates are used to implement the BIN override feature. For more information, refer to the BIN override guide.

mode_type'SINGLE' | 'COMBO'

Mode type enum - SINGLE or COMBO. A combo card can have both a credit and debit mode, meaning it is associated with both a credit and debit program and account. A single card has one mode - credit or debit. Refer to the mode documentation in the Card overview guide for more information.

update_tokensboolean

Should the card be updated with associated tokens?

If true, the cardholder will not need to redigitize their card for their current wallet apps.

Default is false.

IMPORTANT: This feature requires additional access setup. Contact your Pismo representative for details.

status'UNNUMBERED'

Card status, sent when an UNNUMBERED card is requested. For issuers who want to create cards on the Pismo platform that will not have PCI data (PAN, PIN) generated here but that they will provide at some point in the future.

brand'VISA' | 'MASTERCARD' | 'ELO' | 'RUPAY' | 'PRIVATE' | 'GPN'

Card network that overrides the one set up by the card's program.

REQUIRED when the status field is used for UNNUMBERED cards.

generate_pvvboolean

For physical cards. Should a PIN Verification Value (PVV) be generated and inserted into the card tracks during embossing, or should the PVV be generated and sent to Visa when updating the card's PIN? Visa's PIN Verification Service (PVS) must be enabled. The default is false.

expiration_datestring

Card expiration date (format = yymm). If passed, the card expiration date is not calculated using the "Card expiration (# of months)" program parameter.

validity_period_hoursinteger

How long, in hours, the card is valid. Cannot exceed the card's expiration_date. Once this period is exceeded, and the card has a NORMAL, BLOCKED, PENDING, WARNING or REISSUED status, its status becomes INOPERATIVE.

This field is used to calculate the datetime value for valid_until.

For VIRTUAL and PLASTIC cards. Setting this field for TEMPORARY or RECURRING cards returns a 400 Bad request error.

atm_change_online_pin_when_script_sentboolean

During ATM transactions, should the card's online PIN be updated when the offline PIN change script is sent to the terminal for execution?

If false, the online PIN is only updated after a subsequent transaction, once the Pismo platform verifies - via the card's CVR (Card Verification Results) — that the offline script was successfully applied.

Default is false.

Example request

{
  "reason_id": 123,
  "embossing_group": "EM1-embosser",
  "embossing_custom_field": "Tracking ID = 5859930",
  "metadata": {
    "my-custom-key": "my-custom-value"
  },
  "abu_enabled": true,
  "template_id": "EAFA693A-57B2-4029-97F3-D20D6F06D79B",
  "mode_type": "COMBO",
  "update_tokens": true,
  "status": "UNNUMBERED",
  "brand": "VISA",
  "generate_pvv": true,
  "expiration_date": "2803",
  "validity_period_hours": 240
}

Response

Reissue card response

idinteger

Update ID

statusstring

Card status enum. Refer to the Card lifecycle and statuses guide for more information and a complete list.

issuing_datestring

Date/time when card was issued in RFC3339 format, i.e., 2019-07-03T17:23:18Z

expiration_datestring

Card expiration date (format = yymm). If passed, the card expiration date is not calculated using the "Card expiration (# of months)" program parameter.

printed_namestring

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 <a href="https://emvlab.org/emvtags/show/t5F20/" target="_blank">ISO EMV tag 5F20</a> for cardholder name.

REQUIRED for an UNNUMBERED card (Card created without PIN or PAN that issuer defines at some point in the future.)

namestring

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.

mode'CREDIT' | 'DEBIT' | 'COMBO' | 'MULTIPLE'

Mode enum: CREDIT - Single credit card DEBIT - Single debit card COMBO - Card has both a credit and debit mode, meaning it is associated with both a credit and debit program and account. MULTIPLE - Combination card created with the DEPRECATED Create combo card endpoint.

For more information, refer to the mode documentation in the Card management guide.

track_numberinteger

Sequential counter incremented every time card is reissued.

transaction_limitstring

Optional for virtual cards. Maximum amount allowed per transaction. Set up to the approved limit. If not set, account limit is used.

embossing_custom_fieldstring

For physical cards. Additional information for embossing company. For example: tracking number or whether the card should be plastic or metal.

You can use this field for any embossing needs specific to your business. Whatever is sent must be agreed upon with the embosser—what to send, what values to send, what format to send, what size to send for each value, and so on.

contactless_enabledboolean

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_enabledboolean

This field is DEPRECATED. For more information, refer to the ABU documentation 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.

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 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.
validity_period_hoursinteger

How long, in hours, the card is valid. Cannot exceed the card's expiration_date. Once this period is exceeded, and the card has a NORMAL, BLOCKED, PENDING, WARNING or REISSUED status, its status becomes INOPERATIVE.

This field is used to calculate the datetime value for valid_until.

For VIRTUAL and PLASTIC cards. Setting this field for TEMPORARY or RECURRING cards returns a 400 Bad request error.

valid_untilstring

Card is valid until this datetime. ISO 8601 format. Once this time is exceeded, and the card has a NORMAL, BLOCKED, PENDING, WARNING or REISSUED status, its status becomes INOPERATIVE. This field's value is calculated using the validity_period_hours.

Example response

{
  "id": 6743052,
  "status": "CREATED",
  "stage": "BLOCKED",
  "issuing_date": "2022-01-07T14:29:19Z",
  "expiration_date": "2027-01-07T14:29:19Z",
  "printed_name": "Some person",
  "card_type": "PLASTIC",
  "name": "PLASTIC",
  "mode": "CREDIT",
  "track_number": 2,
  "program": {
    "id": "8519"
  },
  "account": {
    "id": 102378693
  },
  "customer": {
    "id": 102377856
  },
  "org": {
    "id": "TN-f878e4a1-2879-48ba-be16-821e73ac98db"
  },
  "contactless_enabled": true,
  "abu_enabled": true,
  "embossing_custom_field": "Use metal"
}

Changes

No recorded changes to this operation across all 1 revision of this API.