# Single card enrolment
source: https://developer.mastercard.com/consent-management/documentation/use-cases/transaction-notifications/single-card-enrolment/index.md

## Overview {#overview}

Single card enrolment is used to enrol individual consumer cards into Transaction Notifications. Therefore, in situations where issuers or corporates do not enrol cardholders directly into your service, you will need to use single card enrolment through Consent Management APIs or Consent Management UI for cardholders to give their explicit consent to deliver Transaction Notifications for their purchase. For example, if you are an Expense Management provider who works with corporates where employees use personal cards for corporate expenses, you will need to enrol the cardholders using single card enrolment.

Within single card enrolment, there are three [Consent Management authentication APIs](https://developer.mastercard.com/consent-management/documentation/api-reference/index.md) can be used in situations where you are PCI compliant and are able to handle PAN data on behalf of the cardholder. Here, your own UI may be used to enrol cardholders into your service. If you are not PCI compliant, you must use the [Consent Management UI](https://developer.mastercard.com/consent-management/documentation/use-cases/transaction-notifications/single-card-enrolment/card-auth-consent-ui/index.md). Mastercard will then handle PAN data on your behalf and return the card reference of the enrolled consumer card.

For some use cases, it is possible that single card enrolment and bulk card enrolment will both need to be used to enrol different types of cardholders. Please see the [Bulk Enrolment APIs](https://developer.mastercard.com/consent-management/documentation/use-cases/transaction-notifications/bulk-card-enrolment/index.md) section for more information on issuer or corporate led use cases.