Create virtual cards

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

Domain controls for virtual cards

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

You can configure the virtual card product to enable dynamic CVV (also referred to as DCVV or dCVV2).

When DCVV is enabled:

A new dynamic CVV is generated each time the virtual card is displayed with the D1 SDK.
The dynamic CVV is valid only for a limited period, which you configure in the card product.

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

The virtual card renewal process is transparent for the end user.

When renewal is enabled for the virtual card product:

D1 automatically renews the virtual card before its expiration 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 any 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.
The cardId is not the PAN; it is a technical unique identifier for the card.
The cardId is used with the D1 API and the D1 SDK to reference the card for any subsequent operation.
If the consumer referenced in Create Card is not yet register in D1 then D1 register it from the consumerId

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

Last updated 5 months ago

Was this helpful?