# Moving to Production
source: https://developer.mastercard.com/authentication-facilitator/documentation/tutorials-and-guides/move-to-prod/index.md

## Overview {#overview}

### What You'll Learn: {#what-youll-learn}

* Get access to the Production environment
* Move your project to Production and go live

### What you'll need: {#what-youll-need}

Before moving to Production:

* You must have a CIS project open.
* You must have received your CIS project number (CIS-xxxx-xxxx) from Mastercard.
* You must have completed testing in the MTF environment.

### APIs Used in this Tutorial {#apis-used-in-this-tutorial}

* Authentication facilitator

## Log in and Add API to existing project {#log-in-and-add-api-to-existing-project}

1. Log in to your Mastercard developers account and select the project.
2. Under the Production access prerequisites section on your project summary page:
   * **Verify your company details** . This ensures your company is registered to do business with Mastercard. You can follow the steps in the [Company Verification guide](https://developer.mastercard.com/platform/documentation/account-management/company-verification/) to complete this step. ![Project dashboard company verification screen](https://static.developer.mastercard.com/content/authentication-facilitator/documentation/tutorials-and-guides/images/afverifycompanydetails.png)

## Request Production Access {#request-production-access}

1. On the Project summary page, click **Request Production access** . ![Project dashboard summary screen](https://static.developer.mastercard.com/content/authentication-facilitator/documentation/tutorials-and-guides/images/adrequestproductionaccess.png)

## Additional Service Details {#additional-service-details}

1. Provide additional service details including Entity name, Customer ID, Security Officer details, and Push API Endpoint. ![Additional service details fields](https://static.developer.mastercard.com/content/authentication-facilitator/documentation/tutorials-and-guides/images/afprodservicedetails.png)
2. Click **Proceed**.

Note: Push API Endpoint is a valid endpoint (URL + TCP Port + Context Root) for MDES to use when sending Production service requests to the customer in the Push API Endpoint. An example might look like: `https://www.mycompany.com:8543/prodweb`.

## Project Credentials {#project-credentials}

Note: Please ignore the OAuth information. The Authentication facilitator API service supports MTLS.

1. Enter **Key alias** and **Keystore password** . A key alias is a label for specific key within a keystore. Ensure that you make a note of the key alias and the keystore password as you will need this information when you send the API request to Mastercard. ![Add Sandbox consumer key alias and password](https://static.developer.mastercard.com/content/authentication-facilitator/documentation/tutorials-and-guides/images/afprodprojectcredentials.png)
2. Click **Proceed**.

Note:   

* If you are using a CSR to generate the project keys, click **Skip this step** , and continue with the project creation. Refer to [Adding Keys and CSR](https://developer.mastercard.com/authentication-facilitator/documentation/tutorials-and-guides/addkey/index.md).

## Additional Credentials {#additional-credentials}

This section is to configure the data-level encryption and decryption keys. Authentication facilitator API uses [Mastercard encryption](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/).

1. Provide **Key alias** and **Keystore password** for Mastercard Encryption Key. The project key creation process starts and completes in a few seconds.
   ![Confirm Sandbox client encryption key will be generated](https://static.developer.mastercard.com/content/authentication-facilitator/documentation/tutorials-and-guides/images/afprodadditionalcredentails.png)

2. Click **Submit** to generate the key.

## Download Production Keys {#download-production-keys}

1. To download the key information, click **Download key file** . ![Create project loading icons and download keys button](https://static.developer.mastercard.com/content/authentication-facilitator/documentation/tutorials-and-guides/images/aeprodupdaingproject.png) The key file has the following information:

* The OAuth Signing key - P12 file
* The client encryption key - pem file - The issuer will use the public key to encrypt data in the response.
* The Mastercard encryption key - P12 file - the issuer will use this key to decrypt the sensitive data encrypted by Mastercard in the payload sent.


Note: The encryption keys cannot be renewed after expiry. We recommend you add a new key before the existing key expires. Refer to the [Rotate a Client Encryption Key](https://developer.mastercard.com/platform/documentation/getting-started-with-mastercard-apis/renewing-your-keys/rotate-encryption-keys/#1-rotate-a-client-encryption-key) topic for detailed instructions. 2. Click **Open project** to see the project details:

<br />

1. Sandbox Client ID
2. Production Client ID
3. Project API status ![Project dashboard summary screen](https://static.developer.mastercard.com/content/authentication-facilitator/documentation/tutorials-and-guides/images/afprodsummarypage.png)

Note:   

* If you see Production Status is "Under Review" or "Declined", please contact the Mastercard implementation manager and request for approval.
* If Production Status is "Ready" then contact the Mastercard implementation engineer or manager for further onboarding.

## Ready to Test in Production {#ready-to-test-in-production}

1. From the Mastercard Developers project summary page, navigate to the Summary section. ![Production client ID](https://static.developer.mastercard.com/content/authentication-facilitator/documentation/tutorials-and-guides/images/afproductionclientid.png)
2. Copy the Production client ID and provide it to your CIS IM.