# Moving to Production
source: https://developer.mastercard.com/ob-accept-payments/documentation/production/index.md

Once you have integrated our APIs with your service and tested with the **test banks** in our [Test Banks](https://developer.mastercard.com/ob-accept-payments/documentation/testing-and-integration/test-banks/index.md) page, you are almost ready to access real bank data.

To start the process of enabling your Production environment, email the
support team at
[openbankingeu_support@mastercard.com](mailto:openbankingeu_support@mastercard.com).
Your customer delivery manager provides the forms and secure upload
instructions that apply to your market, license model, merchants, and
settlement model.

## Tasks to Enable Production {#tasks-to-enable-production}

Complete the following tasks when you are ready to begin Production testing.

### Tasks for All Integrators {#tasks-for-all-integrators}

You need to complete these steps to move to Production, whatever license model you are operating under.

1. **Complete your Sandbox integration and testing.** Test each payment flow and feature that you plan to use in Production.
2. **Obtain a Production certificate.** Acquire an SSL/TLS Organization Validation (OV) certificate from a supported Certificate Authority (this can take 2-4 weeks). Refer to [API Basics](https://developer.mastercard.com/ob-accept-payments/documentation/api-basics/index.md#production-certificates) for the list of supported Certificate Authorities.
3. **Complete the Integrator Onboarding Form.** Ask your customer delivery manager to provide the form when you have completed sandbox testing.
4. **Onboard the merchants you want to use in Production.** The process depends on your license model:
   * If you use your own PISP license, refer to [Merchant Onboarding for
     Licensed Integrators](https://developer.mastercard.com/ob-accept-payments/documentation/payments/merchant-onboarding/merch-onb-for-licensed-integrators/index.md).
   * If you operate under Mastercard's license, refer to [Merchant Onboarding
     for Unlicensed Integrators](https://developer.mastercard.com/ob-accept-payments/documentation/payments/merchant-onboarding/merch-onb-for-unlicensed-integrators/index.md).
5. **Upload logos.** Upload any merchant logos you want to display in [customized
   Pay Connect flows](https://developer.mastercard.com/ob-accept-payments/documentation/customization/index.md) using the [Theming
   API](https://developer.mastercard.com/mastercard-open-banking-theming-api/documentation/).
6. **Submit your Production certificate.** Provide your public certificate through the secure upload method your customer delivery manager specifies.

### Additional Tasks When You Operate Under Mastercard's License {#additional-tasks-when-you-operate-under-mastercards-license}

1. **Complete KYC checks.** Your customer delivery manager provides the required Know Your Customer (KYC) form.
2. **Provide evidence for settlement accounts.** For each integrator or merchant account that will receive settlement funds, complete the account ownership declaration and provide a bank statement. A bank statement is mandatory when a merchant uses its own account for settlement.

### Additional Tasks When You Use Your Own PISP License {#additional-tasks-when-you-use-your-own-pisp-license}

1. **Provide your TPP certificates.** Start this process as early as possible to avoid delaying Production access. Refer to [TPP
   Certificates](https://developer.mastercard.com/ob-accept-payments/documentation/production/tpp-certificates/index.md) for certificate requirements and secure delivery guidance.
2. **Register Production redirect URLs in the UK.** If you operate in the UK, include all of these redirect URLs in your Open Banking Software Statement:
   * `https://connect.aiia.eu/callback`
   * `https://connect.openbanking.mastercard.eu/callback`
   * `https://app.openbanking.mastercard.eu/connect/callback`

## Payment Rails {#payment-rails}

Each payment runs on a payment rail, and the available rails depend on the market.

You onboard a receiving account for each payment rail, so you receive a `destinationId` for every rail you plan to use.

Refer to [Payment Rails](https://developer.mastercard.com/ob-accept-payments/documentation/production/payment-rails/index.md) for the payment rail requirements you must follow for your region and payment methods.

Refer to [Supported Payment Rails](https://developer.mastercard.com/ob-accept-payments/documentation/production/supported-payments-rails/index.md) for details of the markets, providers and payment schemes available.

## TPP Certificates {#tpp-certificates}

Refer to [TPP certificates](https://developer.mastercard.com/ob-accept-payments/documentation/production/tpp-certificates/index.md) for details of how to acquire the eIDAS certificates required if you operate under your own license as Third Party Provider.