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

## FAQ {#faq}

Cardholders are consenting to allow frictionless authentications during future checkout processes where they do not have to enter an OTP or Additional Factor of Authentication (AFA) for that specific transaction. Once cardholders provide their consent, they can perform frictionless authentications for transactions amounting up to INR 2000. Cardholders can request their merchant to revoke the consent they previously provided.   
Once the consent is revoked the cardholders will:
* Stop receiving the benefits of frictionless authentications.
* Require to provide a second factor of authentication during all the checkouts.

Merchants can retrieve the consent for a specific cardholder using the consent ID provided after the consent is stored and check the status of user consent. Cardholders are presented with consent text in English only. Merchants can revoke consent for a cardholder by calling the revoke consent API after an action is initiated by the cardholder in the merchant application. No, merchants can revoke only one cardholder consent at a time. It can be done using a consent ID after an action is initiated by the cardholder in the merchant application. Merchant cannot revoke the consent without a cardholder's input. Cardholder consent is only valid for a single device. If a new device is used, the cardholder will be required to provide separate consent for that device. Mastercard's Customer Implementation Service (CIS) team will help you through the onboarding process for each environment. Once the connectivity is established successfully, you can start using the APIs. There are two environments where onboarding is performed:
* **Mastercard Test Facility (MTF)** is used for all the tests and pre-production validations.
* **Production** is used for commercial deployments.

## Get Help {#get-help}

### Contact us for technical support. {#contact-us-for-technical-support}

Get Help