# Move Project to Production
source: https://developer.mastercard.com/transactions-service/documentation/tutorials-and-guides/production-access-tutorial/index.md

This section walks through the steps required to get the Production environment access and then call the Transactions Service.

#### What you will learn {#what-you-will-learn}

* How to request access to the production environment
* How to create a client in the production environment

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

After validating your OAuth integration in Sandbox, you can request Production access. The steps are similar for both OAuth 1.0a and OAuth 2.0 projects.

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

1. From your project dashboard, click the **Request Production Access** button in the Production section of the screen.
   ![Request Production Access](https://static.developer.mastercard.com/content/transactions-service/img/requestproductionaccess.png)

2. The Request Production Access window is displayed with details about your project.
   ![Overview Production Access](https://static.developer.mastercard.com/content/transactions-service/img/overviewproductionaccess.png)

3. Review the requirements and click **Continue** or **Next** to proceed with production key creation.

Note: Production access requests typically require 3-5 working days for review and approval. You will receive an email notification at your registered email address once the review is complete.

## Create a Production Key {#create-a-production-key}

The MRS Transactions Service supports both **OAuth 1.0a** and **OAuth 2.0** authentication methods. Create your production credentials using the method that matches your project configuration.

### OAuth 1.0a Key Setup {#oauth-10a-key-setup}

If your project is configured for OAuth 1.0a authentication:

1. Enter a descriptive name for the key in the **Key Alias** field (e.g., "Production-OAuth1-Key").

2. Enter a password in the **Keystore Password** field to encrypt your keys.

3. Click **Next** to generate a 2048-bit RSA key pair for production API calls.
   ![Client Encryption Key](https://static.developer.mastercard.com/content/transactions-service/img/clientencryptionkey.png)

4. You will receive the client encryption keys for encrypting sensitive payloads.

5. Download the key package and securely store the keystore password and key alias.

6. Complete the flow and wait for the production key provisioning confirmation email.

Note: You can renew or rotate your OAuth 1.0a production key later from the project dashboard without creating a new project.

### OAuth 2.0 Key Setup {#oauth-20-key-setup}

If your project is configured for OAuth 2.0 authentication:

1. Navigate to your project and click **Add Production Key** for OAuth 2.0.

2. Enter a descriptive key alias and keystore password for your Production key (e.g., "Production-OAuth2-Key").
   ![Create OAuth 2.0 Production Key](https://static.developer.mastercard.com/content/transactions-service/img/oauth2-credentials.png)

3. Click **Next** to generate your client assertion key (used for `private_key_jwt`).

4. Download the generated key package containing your client credentials.
   ![Download OAuth 2.0 Production Keys](https://static.developer.mastercard.com/content/transactions-service/img/oauth2-downloadkeys.png)

5. Copy and securely store the Client ID and keystore password for production onboarding.

6. Complete the flow and wait for the production key provisioning confirmation email.

Note: For both OAuth 1.0a and OAuth 2.0 projects, keys can be renewed or rotated later from the dashboard. You do not need to create a new project when rotating or renewing Production keys. Tip: OAuth 2.0 production enablement may require additional approval steps. Refer to the official page [Using OAuth 2.0 to Access Mastercard APIs](https://developer.mastercard.com/platform/documentation/authentication/using-oauth-2-to-access-mastercard-apis/#step-by-step-implementation) for detailed production setup instructions. Note: When you click **Download key file**, a private key and certificate signing request (CSR) are generated in the browser. Only the CSR is sent to Mastercard, which helps keep your private key private.

## Generate Encryption Key {#generate-encryption-key}

1. After the production key is downloaded, the client encryption keys are auto-generated. The client encryption keys will be used to encrypt the payload.
2. Click **Next** to generate a 2048-bit key pair that will be used for the MRS Transactions API calls. ![Create Production Key](https://static.developer.mastercard.com/content/transactions-service/img/createproductionkey.png)

## Confirm and Download {#confirm-and-download}

1. Click **Confirm and Download Keys** and save the downloaded file. ![Confirm and Download Keys](https://static.developer.mastercard.com/content/transactions-service/img/confirmanddownloadkeys.png)
2. Once you complete this process, the Mastercard API Support team will review and approve your request for Production access.
3. You will receive an email from Mastercard Developers to your registered email address, depending upon the outcome of the review. Note: Typically, it takes 3-5 working days to review and approve the Loyalty Management API Production access request.

## Download the Encryption Key {#download-the-encryption-key}

1. After the production environment is provisioned, navigate to **My Projects** and select your project.
2. Open the **Actions** dropdown list and click the **Download Encryption Key** to download the client encryption key. ![Production Keys APIs](https://static.developer.mastercard.com/content/transactions-service/img/productionkeysapis.png)

## Provide information to Mastercard Product Delivery or CIS Implementation manager {#provide-information-to-mastercard-product-delivery-or-cis-implementation-manager}

Once you have the consumer key, provide it to your Mastercard Product Delivery or Customer Implementation Services Implementation Manager (CIS IM).
To complete this, perform the following steps:

1. From the Mastercard Developers project summary page, go to the Production Keys section, click on the Actions dropdown button, and select the Copy Consumer key option.
2. Paste the Client ID value into an email and send it to your Product delivery or CIS IM. The first 48 characters of this key value (up to the exclamation point) will be the Mastercard API Client ID, which will be used for the production environment. An example of the key value, with Client ID represented in bold **6Fmo7rEvHmVFTrv73a0m6qfUExPxMzOdY5Rs32KI09979c7f**!aea8847fa4b84b9886143a40ac117aee0000000000000000.
3. Once the CIS team adds the Client ID you would be able to test the APIs.