> 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-android/get-started/configuration/5.-push-notifications.md).

# 5. Push notifications

NFC Wallet uses push notifications for **LCM** events, payment key replenishment, and transaction notifications.

On Android, implement push delivery using **Firebase Cloud Messaging (FCM)**.

{% hint style="info" %}
On Huawei devices without Google Play services, use **HMS Push Kit**.
{% endhint %}

### What you need to implement

Your **digital wallet application** must:

* Configure FCM or HMS Push Kit.
* During enrollment, retrieve the push token and pass it to the NFC Wallet SDK.
* Route inbound push payloads from the NFC Wallet backend to the NFC Wallet SDK.
* Handle push token refresh and update the NFC Wallet SDK.

### In this section

* [Configure push provider](/nfc-wallet-sdk-android/get-started/configuration/5.-push-notifications/configure-push-provider.md)

  Set up FCM or HMS Push Kit.
* [Handle push tokens](/nfc-wallet-sdk-android/get-started/configuration/5.-push-notifications/handle-push-tokens.md)

  Keep the push token in sync with the NFC Wallet SDK.
* [Handle push notifications](/nfc-wallet-sdk-android/get-started/configuration/5.-push-notifications/handle-push-notifications.md)

  Route and process inbound NFC Wallet push notifications.


---

# 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.payments.thalescloud.io/nfc-wallet-sdk-android/get-started/configuration/5.-push-notifications.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.