> 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/implement-nfc-wallet/make-payment/implement-contactless-payments/7.-configure-cdcvm-experiences.md).

# 7. Configure CDCVM experiences

## Overview

This page summarizes the supported transaction types and explains when you must configure risk management to support a **single-tap** experience without authentication for:

* **low-value transaction** (**LVT**)
* **transit transaction**

You may also review CDCVM for Mastercard, Visa, and PURE dedidcated sections. Indeede event if NFC Wallet SDK provides payment-network-agnostic CDCVM behavior, payment-network-specific details still apply.

## Transaction types

### High-value transaction (HVT)

Every HVT requires end user authentication.

NFC Wallet SDK prompts the end user to authenticate before payment.

Each authentication covers one payment only.

### Low-value transaction (LVT)

LVT does not always require end user authentication.

Based on LVT accumulators, NFC Wallet SDK may require end user authentication.

See [Define risk management](https://docs.payments.thalescloud.io/nfc-wallet-sdk-android/implement-nfc-wallet/make-payment/implement-contactless-payments/7.-configure-cdcvm-experiences/define-risk-management.md) for more details.

### Transit transaction

A transit transaction occurs at a transit gate. To improve the end user experience, a transit transaction can be performed without end user authentication.

The digital wallet application can allow transit transactions without authentication.

See [Define risk management](https://docs.payments.thalescloud.io/nfc-wallet-sdk-android/implement-nfc-wallet/make-payment/implement-contactless-payments/7.-configure-cdcvm-experiences/define-risk-management.md) for more details.

## Product-specific CDCVM behavior

NFC Wallet SDK provides a transparent CDCVM behavior across payment networks.

But product-specific details still apply for each digital card product. For more details, see:

* [Mastercard CDCVM](https://docs.payments.thalescloud.io/nfc-wallet-sdk-android/implement-nfc-wallet/make-payment/implement-contactless-payments/7.-configure-cdcvm-experiences/mastercard-cdcvm.md)
* [Visa CDCVM](https://docs.payments.thalescloud.io/nfc-wallet-sdk-android/implement-nfc-wallet/make-payment/implement-contactless-payments/7.-configure-cdcvm-experiences/visa-cdcvm.md)
* [PURE CDCVM](https://docs.payments.thalescloud.io/nfc-wallet-sdk-android/implement-nfc-wallet/make-payment/implement-contactless-payments/7.-configure-cdcvm-experiences/pure-cdcvm.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-wallet-sdk-android/implement-nfc-wallet/make-payment/implement-contactless-payments/7.-configure-cdcvm-experiences.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.
