> 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/mastercard-cdcvm.md).

# Mastercard CDCVM

### Overview

This page describes CDCVM behavior for a Mastercard digital card.

### Supported CDCVM variants

Mastercard supports two CDCVM variants in the `MCBPv2` digital card profile:

* `FLEXIBLE_CDCVM` supports LVT without authentication and transit payments without authentication.
* `CDCVM_ALWAYS` requires **end user** authentication for every transaction.

### Low-value transaction (LVT)

For Mastercard, the terminal determines whether a transaction is an LVT.

It uses data in the `Generate AC` APDU command, including the CVM result and terminal capabilities.

To support LVT without authentication:

* The Mastercard digital card profile must be `FLEXIBLE_CDCVM`.
* You must enable the LVT payment experience as described in [Define risk management](/nfc-wallet-sdk-android/implement-nfc-wallet/make-payment/implement-contactless-payments/7.-configure-cdcvm-experiences/define-risk-management.md).

### Transit payment without authentication

For Mastercard, NFC Wallet SDK treats a transaction as a transit transaction when both conditions are true:

* The transaction amount is `0`.
* The transaction `MCC` identifies a transit merchant.

To support transit payments at a transit gate without authentication:

* The Mastercard digital card profile must be `FLEXIBLE_CDCVM`.
* You must enable transit payment without authentiction as described in [Define risk management](/nfc-wallet-sdk-android/implement-nfc-wallet/make-payment/implement-contactless-payments/7.-configure-cdcvm-experiences/define-risk-management.md).

#### MCC for transit

<details>

<summary>MCC for transit</summary>

<table><thead><tr><th width="114.22222900390625">MCC</th><th>Description</th></tr></thead><tbody><tr><td>4111</td><td>Transportation - suburban and local commuter passenger, including ferries</td></tr><tr><td>4131</td><td>Bus lines</td></tr><tr><td>4784</td><td>Bridge and road fees, tolls</td></tr><tr><td>7523</td><td>Automobile parking lots and garages</td></tr></tbody></table>

</details>


---

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