> 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/define-card-product.md).

# Define card product

Configure the following **card product** parameters in the D1 backend before you create virtual cards.

| Parameter                       | Description                                                                                                                                                                   |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| scheme                          | Payment network of the card: Visa or Mastercard.                                                                                                                              |
| class                           | Card program level. For Visa: `CLASSIC`, `GOLD`, `PLATINUM`, `SIGNATURE`, `INFINITE`. For Mastercard: `GOLD`, `PLATINUM`, `WORLD ELITE`.                                      |
| type                            | Card type. Currently, only `DEBIT` is supported.                                                                                                                              |
| PAN range                       | Range of PANs used by the D1 backend to generate the card PAN, defined by a start and end PAN value.                                                                          |
| Supported account currency list | List of native currencies supported by the D1 backend for authorization (used for multi-currency cards).                                                                      |
| Default currency                | Default currency of the card.                                                                                                                                                 |
| Initial validity period         | Validity period used to compute the card expiry date when the card is first created.                                                                                          |
| Renewal validity period         | Validity period used to compute the card expiry date when the card is renewed.                                                                                                |
| Default control settings        | Default domain controls applied to the card at creation or registration (for example, international payment control, denied currency list, forbidden merchant category list). |
| Default limits                  | Default spending limits applied to the card at creation or registration.                                                                                                      |
| Dynamic CVV                     | Enables dynamic CVV (dCVV2) for this card product and defines the dCVV2 validity period.                                                                                      |
| Initial state                   | Initial state of the card when it is created in D1 (for example, `active`).                                                                                                   |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/secure-card-display/get-started/define-card-product.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.