> 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/tokenization/implement-tokenization/end-user-notifications.md).

# End User notifications

D1 can send informational notifications to the **End User**. Notifications are sent by SMS or email.

During **Tokenization**, D1 can confirm activation. D1 can remind step-up authentication (ID\&V). D1 can also confirm digital card deletion.

### When D1 sends notifications

The table below lists the supported cases:

| Condition                                                                                                        | Description                                                                                                                                                                                                                                                                                                                                                | Message Example                                                                                                                                                                                                                                         |
| ---------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The end user has not performed the authentication                                                                | If the end user does not take any action for the authentication, the token remains in an inactive state and cannot be used for payment. The purpose of the message is to remind the end user that there are still actions expected to complete the process. The message will be sent after a time of inactivity that can be configured. Default is 24 hrs. | "Your card ending with **{{fpanLastDigits}}** for **{{wallet}}** is pending for activation"                                                                                                                                                             |
| The end user has completed the authentication with success                                                       | This notification is meant to confirm to the end user that the process has been completed successfully and that the token can now be used for payments.                                                                                                                                                                                                    | "Your card ending with **{{fpanLastDigits}}** for **{{wallet}}** has been activated"                                                                                                                                                                    |
| The end user decides to decline the activation of the service OR digital card has been deleted Post-tokenization | The end user can decide, at any time, to decline the activation of the service by simply deleting the token from the wallet. This notification is meant to confirm the deletion of the token.                                                                                                                                                              | "Your card ending with **{{fpanLastDigits}}** was successfully removed from **{{wallet}}** on **{{deviceName}}**. **{{** The reason for deletion is **{{reason}}**. **}}** If you require more information contact us at **{{customerServiceNumber}}**" |

### Sequence diagram

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

### Message templates and placeholders

The **Issuer** defines the notification templates. Use placeholders to inject runtime values. Use placeholders exactly as shown.

#### Available placeholders

* `{{fpanLastDigits}}`: Last four digits of the **FPAN**.
* `{{wallet}}`: xPay Wallet name (for example, Apple Pay or Google Pay).
* `{{deviceName}}`: End User device name, if provided by the wallet.
* `{{reason}}`: Deletion reason, if provided to D1 (**optional**).
* `{{customerServiceNumber}}`: Customer service phone number set during **D1 onboarding**.
* `{{cardProductName}}`: Card product name, when available in your configuration.

{% hint style="info" %}
Keep optional placeholders in optional sentences. For example, mention `{{reason}}` only when you have a value.
{% endhint %}

#### Email subject example

Email notifications can include a subject.

* Subject: Your **{{cardProductName}}** card has been removed from **{{wallet}}**.

### Channels and prerequisites

Notifications are **optional**. Enable them during **D1 onboarding**.

Only **SMS** and **email** are supported. D1 relies on End User contact data registered in D1.

{% hint style="warning" %}
Do not include sensitive data in notifications.

Do not include PAN, DPAN, or full card details. Use last digits only.
{% endhint %}

Register End Users from your **Issuer backend** using [Register end users](/tokenization/get-started/manage-end-users.md).

{% hint style="info" %}

* If the **Issuer** sends **OTP** by SMS or email, D1 does **not** send End User notifications.
* If you enable End User notifications, keep End User contact data current in D1.
  {% 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, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/tokenization/implement-tokenization/end-user-notifications.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.