Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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 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 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:

Last updated

Was this helpful?