Card renewal enables the issuer to update an existing card's expiration date, keeping the same card while assigning a new expiration date.

Renewal behavior differs depending on the card type.

Virtual card—The new expiration date is applied immediately after the renewal request.

Physical card:—The new expiration date initially remains pending. It is used during the new card embossing and is effectively applied only after the renewed physical card is activated.

Important—For both card types, the PAN and PIN remain the same. And, if the issuer wishes to change the card PIN, they can use the Pismo endpoints available for that purpose.

Virtual card renewal

For virtual cards, the renewal process is a single step.

Step 1: Request the renewal

The issuer must call the Renew card expiration date endpoint.

In the request, the issuer must provide the desired new expiration date in the new_expiration_date field.

Expected behavior after renewal

• The new expiration date is applied to the card.
• The Card updated event is sent with operation_type = EXPIRATION_DATE_RENEWED. The event has an expiration_date_renewal_data object. For example:
  JSON

  {
      "new_expiration_date": "3006",  // YYMM
      "expiration_date_update_status": "APPLIED",  
      "renewal_request_date": "2026-01-01T07:51:20Z",
      "renewal_applied_date": "2026-01-01T07:51:20Z"
  }

• If the issuer uses ABU (Mastercard's Automatic Billing Updater) or VAU (Visa Automatic Updater), the Automatic Updater notification file sent event is generated with reason_code = E
• From this point forward, authorizations will use the new expiration date.

Physical card renewal

For physical cards, the renewal process includes additional steps because the card must go through a new personalization process before the new expiration date becomes effective.

The renewal process has three main steps:

1. Request the card renewal.
2. Emboss the card with new details.
3. Activate the renewed card.

Step 1: Request the renewal

The issuer must call the Renew card expiration date endpoint.

In the request, the issuer must provide the desired new expiration date in the new_expiration_date field

Expected behavior after renewal

1. The new expiration date remains pending

• Through the Get non-PCI card information endpoint, the issuer can retrieve data for cards that are currently undergoing the renewal process and whose new expiration date is still pending, meaning the renewed card has not yet been activated.
  Data includes:
  • New expiration date provided when submitting the renewal request
  • Pending renewal status. Only renewals with status WAITING are returned
  • Date and time the renewal was requested

2. The Card updated event is sent with operation_type = EXPIRATION_DATE_RENEW The event has a expiration_date_renewal_data object. For example:
   
   JSON

   {
       "new_expiration_date": "3006",  // YYMM
       "expiration_date_update_status": "WAITING",  // Not yet applied
       "renewal_request_date": "2026-01-01T07:51:20Z"
   }

3. The card is marked as not embossed, and the Card can be added to next scheduled embossing event that is sent with operation_type = EXPIRATION_DATE_RENEW.

At this stage, the new expiration date is not yet effective for authorization processing. Authorizations will continue to consider the card's current expiration date.

Step 2: Embossing

After initiating the renewal, the issuer must submit the card again to the embossing process.

To do this, the issuer must call the Add card to next scheduled embossing endpoint.

New data to be sent in the embossing file

The embossing file will be generated considering the updated card information, including:

• New expiration date
• New CVVs, calculated using the new expiration date
• Track 1 containing the new expiration date and CVV
• Track 2 containing the new expiration date and ICVV
• ISSUE-REASON field with the following value R (Renewal)

Considerations regarding authorizations

Even after the card has been sent in the embossing file, the new expiration date remains pending.

Until the renewed physical card is activated, authorizations will continue to use the card's current expiration date.

This allows the existing card to remain operational while the renewed physical card is being produced and delivered to the cardholder.

Step 3: Activate the renewed card

Once the cardholder receives the renewed physical card, the issuer must perform the activation process to complete the renewal.

For this purpose, the Activate physical card endpoint must be called.

Expected behavior

After activation:

• The pending new expiration date is effectively applied to the card.
• The card status remains the same.
• The Card updated event is sent with operation_type = EXPIRATION_DATE_RENEWED. The event has a expiration_date_renewal_data object. For example:
  
  JSON

  {
      "new_expiration_date": "3006",  // YYMM
      "expiration_date_update_status": "APPLIED",  
      "renewal_request_date": "2026-01-01T07:51:20Z",
      "renewal_applied_date": "2026-01-01T07:51:20Z"
  }

• If the issuer uses ABU or VAU, the Automatic Updater notification file sent event is sent with reason_code = E
• From this point forward, authorizations will consider the new expiration date.

Virtual versus Physical card renewal

Key implementation considerations

• The main difference issuers must consider is when the new expiration date becomes effective.
• For a virtual card, the renewal request effectively completes the expiration date update, and subsequent authorizations use the new expiration date.
• For a physical card, the renewal request only initiates the renewal process. The new expiration date remains pending while the renewed card is embossed, produced, and delivered. The new expiration date becomes effective for authorization only after the renewed physical card is activated.

Endpoints

• Get non-PCI card information—Can return card renewal information
• Renew card expiration date—Renew a card via changing its expiration date
• Add card to next scheduled embossing—Get renewed physical card embossed.
• Activate physical card— Activate renewed physical card

Events

• Card updated—Generated when the Renew card expiration date endpoint is called
• Card can be added to next scheduled embossing—Generated when the card is scheduled for the next embossing
• Automatic Updater notification file sent—Generated when physical card sent for embossing