# Renewal

Renewing a Card consists of issuing a new card before the original one expires. This new card has the same attributes as their previous one.

Card Renewal is tied to your Card Program and the kind of product issued. Issuing services can be adjusted to optimize the costs and adapt the renewal experience (e.g., packaging).

Toolbox icon

Feature activation – Renewal is not activate by default

Please contact your Treezor Account Manager if you're interested in this feature.

# Renewed card specificities

When a card is renewed, some attributes remain identical to the original one while others have new values. This ensures a continuity of services (e.g., X-Pay and 3DS enrollments) and a smoother experience (identical PIN code) for cardholders.

# Inherited attributes

  • Card design
  • Limits and restrictions
  • 3DS authentication methods (SMS OTP, OOB)
  • X-Pay enrollments
  • PIN code
  • cardTag
  • Type of card (i.e., Virtual or Physical)

# New attributes

  • cardId
  • PAN
  • expiryDate
  • publicToken
  • cvv
  • The outstanding spending limits, which are reset (i.e., if €90/100 were spent on the previous Card, €100 will still be usable on the renewed one)
Info icon

Information – Virtual Converted Cards are automatically produced

Renewing a virtual converted card results in a new virtual converted card. You don't need to go through the conversion process again.

Warning icon

Caution – PIN Change is not automatically done on both cards during Renewal

If the PIN code of the card being renewed is changed during the renewal procedure, then the PIN code must also be changed manually for the renewed Card.

# Renewal process

The renewal process goes through the following steps:

  1. The card renewal process is triggered (manually or automatically)
  2. The card.renew webhook is sent
  3. The cardholder receives the new card (inactive)
  4. The cardholder activates the new card
  5. The original card status is set to EXPIRED

# Automatic renewal

The automatic card renewal process is triggered at the beginning of each month. A request for renewal is sent to the card processor to renew all the cards meeting the following conditions:

  • Expire within the current monthexpiryDate in the current month minus 1 day.
  • Are activeisLive attribute is set to 1.
  • Are renewable – Attached to a product code with the automatic renewal attribute, or the renewal type set to automatic (“renewalType”: “A”).

Won’t be renewed cards which:

  • cardStatus value is STOLEN, EXPIRED, LOST, DESTROYED.
  • renewalType value is N.
  • Have already been renewed (i.e.,renewalDate value is other than null).

# Manual renewal

In case you need to renew a card prior to its expiration month, you can trigger the card renewal manually. This is only possible for active cards that haven't been renewed yet, and whose status is other than STOLEN, EXPIRED, LOST, DESTROYED.

Use the following request with the cardId as a path parameter to renew a card manually.

If successful, the card.renew event is sent, and the Card object is returned:

# Renewal failed responses

The following HTTP 400 errors may occur when failing to renew a Card.

errorCode errorMessage
34000 The card must be already activated.
34001 The request is refused because the card has expired.
34003 The card must not be stolen or lost or destroyed.

# Activation of a renewed card

As a security measure, the new card is issued in an inactive state to ensure that a Card is not usable before the cardholder receives it.

Once received, the card can be activated, and the previous card status will be automatically set as EXPIRED. Expired cards can no longer be used, and this status is permanent.

# Renewal Type (renewalType)

When creating a Card, the card renewal type (automatic or not) is defined by your Card Program. If renewalType is set to null and the product is auto-renewing, the card will be renewed.

The renewal type:

  • Enables you to set automatic renewal on a card-by-card basis if this is not set at product level.
  • Allows you to exclude a card from automatic renewal (for a user who closes their account, for example).

A dedicated endpoint allows you to update the renewal type according to your needs: PUT /v1/cards/{cardId}/renewalDetails.

Note icon

Note – Can’t update renewalType for cards expiring within the month

An endpoint will be provided in the future to manually renew such cards.

# Parameters

Attribute Type Description
renewalType string Define how the Card is to be renewed. Values can be the following:
  • A – Automatic renewal.
  • N – Non-automatic renewal.

Use the following request with the cardId as a path parameter to update the card renewal type.

There is an example of {payload}:

Returns the Card Renewal Details object if successful:

# Endpoints

Endpoint Description
/v1/cards/{cardId}/renewalDetails Update the card renewal options.
/v1/cards/{cardId}/renewalDetails Retrieve the card renewal options.
/v1/cards/{cardId}/renew Renew a Card manually.
Updated on: 5/23/2024, 10:13:49 AM