> 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/nfc-wallet-sdk-ios/implement-nfc-wallet/tokenize-a-card.md).

# Tokenize a card

## Overview

**Tokenization** creates a digital card from a funding card (FPAN) and provisions it in your **digital wallet application**.

During Tokenization, you typically:

* Capture card credentials.
* Check card eligibility.
* Present the terms and conditions (T\&C) and record the end user’s acceptance.
* Digitize the card to create a digital card.

{% hint style="info" %}
Depending on your program, the terms and conditions (T\&C) might not be required.
{% endhint %}

## Capture card credentials

Card credentials can be provided by:

* **Issuer backend**. For example, when the digital wallet application is an issuer application.
* **End user**, via manual entry or camera scan. For example, when your digital wallet application is an open wallet (supporting cards from multiple issuers).

{% hint style="warning" %}
Treat FPAN, expiry date, and CSC as sensitive data. Never log them. Only send them in encrypted form.
{% endhint %}

## Issuer Tokenization decision

During digitization, the issuer approves or declines **Tokenization**.

The issuer Tokenization decision can be:

* **Green:** Approve Tokenization without step-up authentication.
* **Yellow:** Approve Tokenization with step-up authentication (**ID\&V**).
* **Red:** Decline Tokenization.

{% hint style="info" %}
When the end user enters card details manually, the issuer Tokenization decision is typically **Yellow** and requires step-up authentication (**ID\&V**).
{% endhint %}

## User experiences

### Green flow

Typical flow:

1. End user selects a card to digitize.
2. End user accepts the terms and conditions (optional).
3. Issuer backend approves Tokenization with no conditions.
4. The digital wallet application shows the digital card, ready to pay.

<figure><img src="/files/Z9ZpzUhElL4y4zLZjPYE" alt=""><figcaption></figcaption></figure>

### Yellow flow

Typical flow:

1. The end user enters card information (manual entry or camera scan).
2. The end user accepts the terms and conditions.
3. The issuer backend approves Tokenization with conditions (step-up authentication required).
4. The digital wallet application displays the available ID\&V methods.
5. The end user selects an ID\&V method and completes ID\&V
6. After successful ID\&V, the digital wallet application displays the digital card, ready to pay.

<figure><img src="/files/lIZOkDkCzdLn0r95RVUd" alt=""><figcaption></figcaption></figure>

## Implementation guides

Implement these steps in order:

1. [Check card eligibility](/nfc-wallet-sdk-ios/implement-nfc-wallet/tokenize-a-card/check-card-eligibility.md)

   Check whether the card is eligible and retrieve the applicable T\&C.
2. [Digitize a card](/nfc-wallet-sdk-ios/implement-nfc-wallet/tokenize-a-card/digitize-card.md)

   Digitize the card to create a digital card.

{% hint style="info" %}
Complete wallet enrollment before you start **Tokenization**. See [Enroll wallet](/nfc-wallet-sdk-ios/implement-nfc-wallet/enroll-wallet.md).
{% endhint %}


---

# 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/nfc-wallet-sdk-ios/implement-nfc-wallet/tokenize-a-card.md?ask=<question>
```

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.