> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/secure-card-display/get-started/manage-cards/create-virtual-cards.md).
# Create virtual cards
Virtual cards are used for e-commerce payments and Tokenization use cases.
### Domain controls for virtual cards
The domain controls you can configure for a virtual card are limited to:
* International payment control
* Denied currency list
* Forbidden merchant category list (MCC list)
### Use dynamic CVV (dCVV2)
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
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.
### Sequence diagram
Virtual card creation and activation flow.
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:
* [Transaction control](https://thales-dis-dbp.stoplight.io/docs/d1-caas/25aregsmz7a2q-transaction-control)
* [Secure Card Display](https://thales-dis-dbp.stoplight.io/docs/d1-caas/3c8a7e6f0a81a-secure-card-display-introduction)
* [Tokenization](https://thales-dis-dbp.stoplight.io/docs/d1-caas/ad6a9b717d3b9-introduction)
* [Push provisioning](https://thales-dis-dbp.stoplight.io/docs/d1-caas/294f33eaf2378-push-provisioning-introduction)
### API endpoint
Create the virtual card using:
* [Create card](/secure-card-display/integrate-d1-api/d1-api-reference/inbound-api-to-d1/card-api.md#post-v2-issuers-issuerid-cards)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.payments.thalescloud.io/secure-card-display/get-started/manage-cards/create-virtual-cards.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.