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

## Overview {#overview}

Diagram behalf_of_banks

As a fintech acting on behalf of an issuer or a Co-brand partner, consent to share data with your service may have already been obtained by the issuer with the explicit permission of the cardholder as part of the card agreement. If this is the case, you may be allowed to register cards for Transaction Notifications API without having to re-obtain consent from cardholders.

Once you have confirmed consent to access a cardholder's transaction data, you can utilize the same [Consent and Authentication API's](https://developer.mastercard.com/consent-management/documentation/api-reference/index.md#authentication-consent-management) to register their cards for transaction notifications, without the need to authenticate the cardholder. This not only saves time and effort for both the issuer and the cardholder, but also ensures a seamless and secure process for enrolling cards into the Transaction Notifications API.

It is important to note that permission to access transaction data must only be used for the approved purpose of providing transaction notifications and not for any other purposes without the cardholder's explicit consent. Additionally, you must comply with all applicable laws and regulations, including data privacy requirements, when accessing and using transaction data.

Large volumes of card registrations can be done using the Bulk Card API. For more information on the Bulk Card API, please refer to the [API specification](https://developer.mastercard.com/consent-management/documentation/api-reference/index.md#cards-bulk).

## Sample Code {#sample-code}

The sample code can be downloaded from here:

* Java: [bulk-apis-java-ref-app.zip](https://static.developer.mastercard.com/content/consent-management/uploads/bulk-apis-java-ref-app.zip) (163KB)