# Consent using Consent Management & Enrollment APIs
source: https://developer.mastercard.com/consent-management/documentation/use-cases/transaction-notifications/single-card-enrolment/apis/index.md

If you are PCI compliant and currently manage cardholder data, you can build your own authentication UI for customer verification. Consent Management \& Enrollment APIs can work with your UI to authenticate your customers.

The following pages describe each stage of the consent lifecycle:

* [Enrollment](https://developer.mastercard.com/consent-management/documentation/use-cases/transaction-notifications/single-card-enrolment/apis/enroll/index.md) --- Create a consent and authenticate the cardholder using 3DS.
* [Retrieve Consent](https://developer.mastercard.com/consent-management/documentation/use-cases/transaction-notifications/single-card-enrolment/apis/retrieve/index.md) --- Get existing consents for an enrolled card.
* [Delete Consent](https://developer.mastercard.com/consent-management/documentation/use-cases/transaction-notifications/single-card-enrolment/apis/delete/index.md) --- Revoke consent for a card or a specific consent.

## Next Steps {#next-steps}

To learn how to use Consent Management \& Enrollment APIs, check out the [Card-based Consent using APIs](https://developer.mastercard.com/consent-management/documentation/tutorials-and-guides/card-consents-tutorial/index.md) tutorial.