Migration of virtual to physical card

Introduction

A new feature has been introduced in the system to allow users to migrate a virtual card to a physical card while retaining the same card details.

The flow

Below you can find the flow details:

1. The user calls the Update Card API with the newly introduced parameter change_to_physical = true.

2. The system updates the card status reason code to AT – Active Transition, indicating that the card is in the transition period.

3. Once the embossing of the physical card is generated, the status moves to A0 – Active Initial, and the card type is updated to physical.

Restrictions During Transition:

1. While in the transition period, the status reason can only be changed to ST – Suspended Transition, indicating that the card is temporarily blocked during migration.

2. If the user wishes to permanently block the card, it is allowed at any time during the transition.

3. While the card is in the transition period, authorization settings will be restricted, preventing specific transactions until the migration to physical is fully completed.

API changes

The following API changes added:

1. Update Card API (PUT /v1/cards/{id})

• New Parameter: "change_to_physical" (Boolean)

• Allows the user to initiate the virtual-to-physical card migration.

2. Update Card Authorization Settings API (PUT /v1/cards/{id}/authsettings)

• Restriction: Users cannot change the card’s authorization settings during the transition period.

3. Change Card Status API (PUT /v1/cards/{id}:statuschange)

• New status codes introduced:

  • AT – Active in Transition (Card is in migration phase).

  • ST – Suspended in Transition (Card is temporarily blocked during migration).

4. Card Products APIs Updates:

• New parameter: "virtual_to_physical_expiry_duration"

• Allows configuration of the maximum duration allowed before the virtual card expires during migration.

For more information refer to the API catalog.