# Support
source: https://developer.mastercard.com/bs-creditor-api/documentation/support/index.md

## FAQs {#faqs}

### General {#general}

The Betalingsservice Creditor API uses OAuth 1.0a for authentication.

### Onboarding {#onboarding}

For detailed onboarding steps please visit [Getting Started](https://developer.mastercard.com/bs-creditor-api/documentation/getting-started/index.md) section. Depending on your agreement, if there are multiple customerIds for the different agreements, then each agreement must have its own project and set of keys. However, if there are multiple agreements linked to the same customerId, then the same credentials can be used. There are two environments where onboarding is performed: Sandbox test environment is used for API stubs with simulated, static responses. It is intended to be used by developers who want to try out API. It contains sample data and an ability for developers to test their code, so they can determine if the functionality offered meets their needs. Production environment is used for commercial deployments. Sandbox is a pre-production test environment, so there are fewer approvals needed to begin testing with sandbox keys. API users should initially build and test their applications using the sandbox environment to make calls before switching to the production environment. Betalingsservice Creditor API keys expire after 1 year.

### Policy {#policy}

The API is configured to handle up to 500 requests per second.

### Performance {#performance}

We aim for an average response time of under 1 second. The asynchronous process behind the creation of the Delegated Mandate is expected to complete every second hour between 07:00 and 19:00 on banking days.

## Contact Us {#contact-us}

Support teams are available Monday to Friday, from 9 AM to 4 PM CET.

* For sandbox and pre-implementation support, contact [APISupport@mastercard.com](mailto:APISupport@mastercard.com).
* For production support contact [MPS.CTS@mastercard.com](mailto:MPS.CTS@mastercard.com).