# Support
source: https://developer.mastercard.com/consent-management/documentation/support/index.md

## FAQ {#faq}

A maximum of 300-350 cards should be enrolled per call when using Bulk Consent API. When creating a project utilize both consents and transaction notification APIs. Please refer to the [Project Setup](https://developer.mastercard.com/consent-management/documentation/tutorials/project-setup/index.md) section for specifics.
* You can test the 3DS flow with different scenarios in sandbox by taking a look at our [Test Page](https://developer.mastercard.com/consent-management/documentation/testing/index.md)
The service doesn't provide an SDK. No. We work with ABU to automatically update a previously enrolled card when it expires or is stolen/lost and replaced with new card. You cannot update the card number for a given consent. In this case, we suggest [Deleting Consent](https://developer.mastercard.com/consent-management/documentation/support/documentation/api-reference/index.md#delete-consents) and requesting [Create Consents](https://developer.mastercard.com/consent-management/documentation/api-reference/index.md#create-consents) with a new card number. Authentication is triggered by Cardholder's Bank (Issuer). When a cardholder initiates enrolment either through the Mastercard UI or using Partner's UI, Issuer will determine if the cardholder needs to be Authenticated (e.g. using 3DS). Partners can leverage their own UI using Consent APIs if they are PCI compliant. Our team will review the UI to ensure cardholders understand how their data will be shared and stored. The partner will not receive transaction notifications on a card with expired consent. The partner will have to capture the cardholder's consent again to receive transaction notifications on that card. Consent expiration can be set in days during the Consent creation request. During onboarding the consent maximum duration will be decided and configured for the use case. If consent expiration equals the agreed upon duration, the consent expiration field can be left blank in the consent request. If a partner acts on behalf of an Issuer or Co-brand partner, and the cardholder has previously granted consent for data sharing, no further authentication may be needed. This is particularly applicable when registering cards for the Transaction Notifications API. Please contact us for more details on enrolling such cards. No, consent deletion is available exclusively through APIs. There is no UI available for this process. You can easily delete consent by integrating with Delete Consent APIs. The Consent Management Service is currently running with a select few customers, to request access to Production system please contact us at [transaction.notifications@mastercard.com](mailto:transaction.notifications@mastercard.com). Email us at [transaction.notifications@mastercard.com](mailto:transaction.notifications@mastercard.com) to get tailored pricing for your use case.

## Get Help {#get-help}

Email us at [transaction.notifications@mastercard.com](mailto:transaction.notifications@mastercard.com) with any further questions.

Consent Management Service is currently running with a select few customers, to request access to production system please contact us at [transaction.notifications@mastercard.com](mailto:transaction.notifications@mastercard.com).