# Use Cases
source: https://developer.mastercard.com/consent-management/documentation/use-cases/index.md

## Overview {#overview}

Consent and Authentication APIs encompass two primary use cases:

1. Single Card Enrolment
2. Bulk Card Enrolment

**Single card enrolment**

When explicit cardholder consent is required, fintech applications can obtain consent using either Mastercard Consent Management APIs or the Mastercard Consent Management UI. Through the Consent Management APIs, a Fintech application manages both the consent user experience and the card registration for Transaction Notifications, which includes handling PAN. Alternatively, by using the Mastercard Consent Management UI, a fintech can acquire cardholders' consent without handling card data.

The following example sequence shows single card enrolment flow.

Diagram single_card_enrolment

**Bulk cards enrolment**

In scenarios where a fintech has already received consents from cardholders as part of a card agreement (e.g., Corporate card program), the fintech can utilize bulk enrolment APIs. This enables the enrolment of multiple cards in a single API request.

The following example sequence shows bulk cards enrolment flow.

Diagram bulk_enrolment_usecase

**Both** the options offer a seamless and secure process for enrolling in Transaction Notifications,
while also ensuring that the cardholder's explicit consent is obtained before
any registration takes place. It is essential to note that **fintech applications**
must comply with all applicable laws and regulations, including data privacy and security
requirements, when obtaining consent and accessing cardholder information.