# Support
source: https://developer.mastercard.com/masterpass-merchant-integration-v7/documentation/support/index.md

For questions on Masterpass Merchant Onboarding and Integration please email us at the following address:   

* [merchant.integration@masterpass.com](mailto:merchant.integration@masterpass.com)

## FAQs {#faqs}

If you are a merchant who chooses to directly onboard and integrate with Masterpass (i.e., not use a Payment Service Provider for payment processing) then you will be required to attest that you are PCI - DSS compliant on the Business Profile page.

If you are a merchant that isn't PCI-DSS compliant (or simply doesn't want to receive PCI-DSS data), then you will have to select a Masterpass approved PSP from the drop down on the Business Profile page.

If you do not see your PSP in the drop down, please contact us and submit your query [here](https://www.mastercard.us/en-us/business/overview/grow-your-business/improve-checkout/secure-digital-checkout.html#!contact). You can find more about Mastercard PCI-DSS requirements [here](https://www.mastercard.us/en-us/business/overview.html).
Mastercard is reminding customers about an upcoming change regarding supported encryption protocols for Internet browsers and other integrations that access Mastercard applications and services. Please see [full article](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/) for explicit details. Your first sandbox key is automatically created for you upon registration, along with a checkout ID (environment agnostic). You can find this in the Key Management section. You cannot create production keys until you've been granted production access. You may invite add/delete users by navigating to the [Permissions](https://developer.mastercard.com/masterpass/merchant/#/permissions) section of the Merchant Dashboard. You may contact [merchant.integration@masterpass.com](mailto:merchant.integration@masterpass.com). Please use the following format to report a bug: issue description, expected result, actual result, steps to reproduce, consumer key (if there is any), screen shots (if there is any).
* General Open API support (e.g. security questions and how to utilize the OpenAPI in general): please contact [APISupport@mastercard.com](mailto:APISupport@mastercard.com)
* Feedback specific to Merchant Checkout: [merchant.integration@masterpass.com](mailto:merchant.integration@masterpass.com)
* Ideas for additional APIs that MasterCard could offer: Please visit our community area and leave a forum post regarding additional APIs or any other suggestions you may have. Our forums are read by and responded to by developers like you. Chances are if you'd like it, we would too.
Please register for an account [here](https://developer.mastercard.com/account/sign-up?referrer=masterpass&locale=en_US). If you are having issues with the merchant dashboard, submit a query to [APISupport@mastercard.com](mailto:APISupport@mastercard.com). However, if your questions are specific to your merchant account, reach out to your CIS team. Merchants and PSP's who implemented with Masterpass prior to August of 2017 had their accounts migrated to the new onboarding experience. Any email addresses associated with accounts on MC Developers and the Merchant Portal were sent instructions for log-in. If you have questions about your log-in credentials, please contact [merchant.integration@masterpass.com](mailto:merchant.integration@masterpass.com) You may remove users by navigating to the [Permissions](https://developer.mastercard.com/masterpass/merchant/#/permissions) section of the Merchant Dashboard. You can use this function to add and remove users simply by providing their email address. This portal is user-agnostic and encourages developers and business administrators to share one comprehensive portal. Users on our legacy experience may have multiple business accounts that were migrated over from MC Developers and the Merchant Portal. We encourage these users to move their information into one account for ease of use moving forward.

## Get Help {#get-help}

Contact us for technical support.