Create virtual cards

Virtual cards are used for e-commerce payments and Tokenization use cases.

The domain controls you can configure for a virtual card are limited to:

You can configure the virtual card product to enable dynamic CVV (also called dCVV2).

When dCVV2 is enabled:

D1 generates a new dCVV2 each time the D1 SDK displays the virtual card.
Each dCVV2 is valid only for a limited period you configure in the card product.

This reduces the risk of card-on-file (COF) data being misused, because the CSC / CVV2 value changes frequently.

Virtual card renewal is transparent for the end user.

When renewal is enabled for the virtual card product:

D1 automatically renews the virtual card before its expiry date.
D1 automatically activates the renewed card.
D1 generates a new expiry date but keeps the same PAN.
D1 keeps the same cardId for the renewed card.
The renewed card is automatically displayed the next time it is shown through the D1 SDK.
D1 updates existing digital cards with the new expiry date.

As a result, the end user can continue to use the virtual card for e-commerce payments and Tokenization without manual action.

If the virtual card is created with state active, it is immediately ready for a first payment.

When the card is created:

D1 returns a cardId.
cardId is not the PAN. It is a unique technical identifier for the card.
Use cardId in the D1 API and D1 SDK to reference the card for subsequent operations.
If the end user referenced in Create card is not registered in D1, D1 can implicitly register the end user from consumerId.

Once created, you can use the same virtual card across other D1 services, for example:

Create the virtual card using:

Last updated 4 months ago

Was this helpful?