> 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/help/faq.md).

# FAQ

Quick answers to common NFC Wallet SDK questions.

### What is the Thales TSH Pay SDK?

Thales TSH Pay SDK is the former name of the NFC Wallet SDK.

### Is it required for the card issuer to implement both green and yellow flows from the first version of the mobile?

No. You can start with the green flow in the first issuer application release. You can add the yellow flow later.

Related guides:

* [Implement the green flow](/nfc-wallet-sdk-ios/implement-nfc-wallet/tokenize-a-card/digitize-card/green-flow-digitization.md)
* [Implement the yellow flow](/nfc-wallet-sdk-ios/implement-nfc-wallet/tokenize-a-card/digitize-card/yellow-flow-digitization.md)

### Is there a limit to the number of cards to be tokenized per Wallet application?

No. The NFC Wallet SDK does not enforce a limit.

### What is a Digital Card ID?

A digital card ID is a unique identifier for a digitized card. The NFC Wallet backend generates it.

### What is the Product ID?

The product ID identifies the card product (for example, Platinum or Gold). Retrieve it from the NFC Wallet backend.

### When the first T\&C are accepted, we do not like to show it again on the next digitization. How can we do it?

Use the NFC Wallet SDK API to accept the terms and conditions (T\&C) on behalf of the end user. After acceptance, you can skip showing the T\&C in later Tokenization flows.

### When the card information is sent, which are the mandatory fields to send?

Send the PAN and expiry date.

### Is it possible to "terminate" or "freeze" a card through the Thales NFC Wallet SDK?

Yes. The end user can delete a digital card from the issuer application using the NFC Wallet SDK. The SDK then processes the related CPS notifications. See [Handle push notifications](/nfc-wallet-sdk-ios/get-started/configuration/4.-push-notifications/handle-push-notifications.md#process-cps-notifications-digital-card-operations).

Suspending a card is supported. Do not expose it to the end user by default. The issuer and payment network typically control that action.

If you need a user-facing “stop payments” control, consider unsetting the default payment card instead.

### What is the process to configure a default card?

A card that is in the `active` state and has a minimum of one payment key can be selected as the default payment card through the `DigitalCard#setDefault` API.

### Is there any other push platform supported other than FCM?

Yes. You can integrate your own push messaging platform by implementing the Wallet Push Server API (per Thales specification).

### Are push messages mandatory in order for the SDK to work as expected?

Yes. Push messages are mandatory because NFC Wallet SDK APIs rely on them to complete specific operations.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/nfc-wallet-sdk-ios/help/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
