> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/credit-card.md).

# Credit card

Configure the Credit card data entry in Remote Desktop Manager to store the card number, expiration, CVC, PIN code, and issuer details.

This article details the many settings and options available for ***Credit card*** data entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry. This field is required.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td><p>How the entry opens:</p><ul><li><strong>Embedded (tabbed)</strong> — Opens the entry in a tab of the main window.</li><li><strong>Undocked</strong> — Opens the entry in a separate window. Additional lists let you choose the monitor and the virtual desktop where the window opens.</li></ul><p>On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list.</p></td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Reveal sensitive information</strong></td><td>Show or hide the masked values of the card. This requires the permission to view sensitive information or passwords on the entry. When the entry requires a check out before revealing its values, check it out first.</td></tr></tbody></table>

**Card information**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Card owner</strong></td><td>Select a contact entry as the owner of the card, or enter the owner's name.</td></tr><tr><td><strong>Card number</strong></td><td>Enter the card number. When the number matches a known card type, that type is displayed next to the field.</td></tr><tr><td><strong>Expiration (mm-yyyy)</strong></td><td>Enter the expiration month (<code>mm</code>) and year (<code>yyyy</code>) of the card. These fields accept digits only.</td></tr><tr><td><strong>Validation (CVC)</strong></td><td>Enter the card verification code. This field accepts digits only.</td></tr><tr><td><strong>Valid from (mm-yyyy)</strong></td><td>Enable to enter the month (<code>mm</code>) and year (<code>yyyy</code>) from which the card is valid. These fields accept digits only.</td></tr></tbody></table>

**Security**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>PIN code</strong></td><td>Enter the PIN code of the card.</td></tr><tr><td><strong>Password</strong></td><td>Enter the password associated with the card.</td></tr><tr><td><strong>Verified by</strong></td><td>Enter the Verified by value associated with the card.</td></tr><tr><td><strong>Secure code</strong></td><td>Enter the secure code associated with the card.</td></tr></tbody></table>

**Issuer**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Issuing bank</strong></td><td>Enter the name of the bank that issued the card.</td></tr><tr><td><strong>Customer service phone</strong></td><td>Enter the customer service phone number of the issuer.</td></tr><tr><td><strong>International service phone</strong></td><td>Enter the international service phone number of the issuer.</td></tr></tbody></table>


---

# 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.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/credit-card.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.
