> 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-payment/implement-nfc-payment/make-payment/manage-payment-authentication.md).

# Manage payment authentication

### Overview

During payment flows that require CDCVM, the issuer application must trigger Android device authentication.

You can implement this step in one of two ways:

* Let the D1 SDK manage the authentication screen.
* Let the issuer application manage the authentication screen.

Use one model consistently in your payment flow.

### Choose an implementation model

#### Use D1 SDK authentication

Choose this model if you want the D1 SDK to own the Android device authentication step.

This model is simpler to integrate. It also keeps the payment flow behavior consistent with the D1 SDK defaults.

See [Use D1 SDK authentication](/nfc-payment/implement-nfc-payment/make-payment/manage-payment-authentication/use-d1-sdk-authentication.md).

#### Use issuer application authentication

Choose this model if the issuer application must control the authentication UX.

This model gives you more control. It also requires the issuer application to manage the Android device authentication screen and related UI states.

See [Use issuer application authentication](/nfc-payment/implement-nfc-payment/make-payment/manage-payment-authentication/use-issuer-application-authentication.md).


---

# 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-payment/implement-nfc-payment/make-payment/manage-payment-authentication.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.
