> For the complete documentation index, see [llms.txt](https://help.xaman.app/app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.xaman.app/app/xaman-cards/creating-a-pin-on-your-xaman-tangem-card.md).

# PINs on older Xumm/Xaman cards

What to know if you set a passcode on a first-generation card

{% hint style="warning" %}
**New Xaman cards do not support PINs.** If you received your cards recently, there is nothing to set up here. To keep your new cards secure, see [Best security practices for the Xaman cards](https://help.xaman.app/app/xaman-tangem-cards/best-security-practices-using-a-xaman-card).
{% endhint %}

#### Which cards does this apply to?

This article only applies to **first-generation cards**. These cards let you set a PIN, which Xaman calls a **passcode**. Once a passcode is set, you have to enter it before the card can sign or change its settings.

Older and newer cards look the same, so the only way to tell is to check in Xaman:

1. Go to **Settings**, then **Accounts**.
2. Tap **Edit** next to your card account.
3. If you see **Card enforced security**, your card supports passcodes. If you do not, your card is a newer card and does not support them.

<figure><img src="https://3221812686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMiHAzvIPISVuuzt0AeOR%2Fuploads%2FAF6Yn5dzUFP8H3RWUkeC%2F1-edit-account.png?alt=media&amp;token=48f830bf-24e3-488f-aada-aa45364c6258" alt="The Edit account screen in Xaman, with Card enforced security set to Long Tap" width="298"><figcaption><p>Card enforced security on an older card</p></figcaption></figure>

Xaman will keep supporting older cards, including their passcodes, in all future versions of the app.

#### Long Tap and Passcode

**Card enforced security** has two settings:

* **Long Tap** is the default. It adds a short delay before the card carries out a command, which protects your card if someone tries to use it from a distance.
* **Passcode** asks for your passcode before the card carries out any command that changes it.

<figure><img src="https://3221812686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMiHAzvIPISVuuzt0AeOR%2Fuploads%2FfP6atccjRELEmk27gMrU%2F2-card-security.png?alt=media&amp;token=2aa50edc-f67c-41f8-8a46-10516ce21300" alt="The Card security screen in Xaman, showing the Long Tap and Passcode options" width="299"><figcaption><p>The two Card enforced security settings</p></figcaption></figure>

#### Why we removed the PIN feature

On earlier Xumm cards, users had the option to set a custom PIN directly on the card's secure chip. The intent was to protect against physical theft, but in practice, it introduced an irreversible point of failure.

When customers received their cards, our setup guide strongly advised activating a secondary backup card, but many people skipped this step. Since on-card PINs are stored strictly within the hardware's secure element, there is no 'forgot password' flow, no backdoor, and no way for anyone to recover it. When a PIN was forgotten without a backup card in place, users permanently lost access to their funds.

Strong security shouldn't rely on ideal human behavior when the penalty is total loss of access. We disabled the PIN feature on newer cards to eliminate this risk. The safest, most forgiving security model remains keeping your primary card physically secure and maintaining a secondary [Backup card](https://help.xaman.app/app/xaman-tangem-cards/getting-started) in a separate location.

#### If you already set a passcode

Your passcode still works, and you still need it to use that card. **We recommend switching back to Long Tap**, so a forgotten passcode can never lock you out:

1. Go to **Settings**, then **Accounts**.
2. Tap **Edit** next to the card account with the passcode.
3. Select **Card enforced security**.
4. Select **Long Tap**, then tap **Save**.
5. When Xaman asks, tap your card. Then enter your current passcode and tap **Continue**.

<figure><img src="https://3221812686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMiHAzvIPISVuuzt0AeOR%2Fuploads%2Ffl7cDBjrXOp0FeWO4GZQ%2F6-enter-passcode.png?alt=media&amp;token=82a35b5a-76fb-4f5d-a7ed-61ba3492b363" alt="The passcode screen, with a Passcode field and a Continue button" width="296"><figcaption><p>Enter your current passcode, then tap Continue</p></figcaption></figure>

A message confirms that your card security has changed to Long Tap.

<figure><img src="https://3221812686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMiHAzvIPISVuuzt0AeOR%2Fuploads%2FP3TlvKZexTp9VaaxJLeL%2F7-success-long-tap.png?alt=media&amp;token=55bca3aa-ee10-40f5-b47d-0157723b6e9e" alt="Message reading: Card security successfully changed to LongTap" width="299"><figcaption><p>Your card is back on Long Tap</p></figcaption></figure>

If you decide to keep your passcode:

* **Write it down** and keep it somewhere secure, separate from the card.
* **Make sure the account has a Backup card.** If you forget the passcode on a card that has no backup, you lose access to the funds on that account. If your card has a passcode but no backup, link a Backup card **now**, while you still remember your passcode. See [How to configure a backup signing account](https://help.xaman.app/app/xaman-tangem-cards/how-to-configure-a-backup-signing-account).

#### If you forget your passcode

There is no reset and no "back door," and Xaman Support cannot recover a passcode for you. What you can do depends on which card has the passcode:

* **If you configured a passcode on your Backup card**, your funds are safe. Use your Primary card to remove the link to the Backup card, then link a new Backup card.
* **If you configured a passcode on your Primary card**, use your Backup card to move your funds to another account.
* **If you did not configure a Backup card for your Primary card**, there is unfortunately no way to access the funds on that account.

See [Lost or damaged cards](https://help.xaman.app/app/xaman-tangem-cards/lost-or-damaged-cards) for step-by-step help. A card with a forgotten passcode works the same way as a lost card.

#### Setting a passcode on an older card

{% hint style="danger" %}
We strongly recommend that you **do not** set a new passcode. If you choose to set one anyway, only do it on a card whose account has a Backup card.
{% endhint %}

1. Go to **Settings**, then **Accounts**.
2. Tap **Edit** next to the card account.
3. Select **Card enforced security**.
4. Select **Passcode**, then tap **Save**.
5. Xaman warns you that a forgotten passcode cannot be recovered. Read it carefully, then tap **Yes, I'm sure** to continue.

<figure><img src="https://3221812686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMiHAzvIPISVuuzt0AeOR%2Fuploads%2FW1lR0vwbdCPwLdY6AWdL%2F5-warning.png?alt=media&amp;token=27b453ac-5406-4d3e-873b-521dd35e8ea3" alt="Xaman warning that funds will be inaccessible and cannot be recovered if you forget your passcode, with Cancel and Yes, I’m sure buttons" width="254"><figcaption><p>The warning Xaman shows before you<br> set a passcode</p></figcaption></figure>

6. When Xaman asks, tap your card. Then enter your new passcode twice and tap **Save**.

A message confirms that your card security has changed to Passcode.

#### Questions?

If you have questions about a passcode on your card, contact us through the [Xaman Support xApp](https://xaman.app/detect/xapp:xumm.support-md) in Xaman.


---

# 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://help.xaman.app/app/xaman-cards/creating-a-pin-on-your-xaman-tangem-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.
