# 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 Loyalty 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.

### 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/uploads/request_prod_access_1.png)

2. The Request Production Access window is displayed with details about your project.

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.

## Escalate an Overdue Production Request {#escalate-an-overdue-production-request}

If you have not received a decision after 5 working days, check the project dashboard and registered email account for an outstanding information request. If none explains the delay, email your assigned Mastercard Product Delivery contact or CIS Implementation Manager on the existing onboarding thread and request a status update and escalation of the Production access review.

Include the following details:

* Project name and project identifier or dashboard URL.
* Production Client ID, if already issued, and the configured OAuth method. Send only the Client ID, not the full Consumer Key, private key, password, or access token.
* Submission date, number of working days elapsed, and any provisioning or support reference.
* Your organization, registered contact email, and a summary of completed Sandbox validation.
* Current dashboard status, any approval emails or sanitized error details, and the business impact of the delay.

If you do not have an assigned contact or cannot reach them, use [Support \> Get Help](https://developer.mastercard.com/transactions-service/documentation/support/index.md#get-help) to raise a Production access request with the same details and reference the original submission. Ask the recipient to confirm the responsible owner, outstanding actions, and the next update date. Keep follow-ups on the same request so the review history remains available.

The documented 3-5 working days is a typical approval timeframe. No separate escalation response target is specified here; confirm the applicable target with your Product Delivery or CIS Implementation Manager instead of assuming another approval deadline.

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

The Loyalty Transactions Service supports **OAuth 1.0a** 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 **Proceed** to generate your production signing key.
   ![Client Encryption Key](https://static.developer.mastercard.com/content/transactions-service/uploads/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.

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

1. The encryption keys are auto-generated. The Client Encryption key will be used to encrypt the request and the Mastercard Encryption key will be used to decrypt the response. ![Encryption keys](https://static.developer.mastercard.com/content/transactions-service/uploads/additionalcredentials.png)
2. Click **Proceed** to continue.

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

1. Click **Download key file** to download a zip file containing the .p12 file required for OAuth authentication in Production. ![Download key file](https://static.developer.mastercard.com/content/transactions-service/uploads/downloadprodkeys.png)

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.

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. Click on **manage** under **Client Encryption Keys** and click **Download** to download the client encryption key. ![Production Keys APIs](https://static.developer.mastercard.com/content/transactions-service/uploads/prodkeys.png)
3. The Client Encryption key will be used to encrypt the request and the Mastercard Encryption key will be used to decrypt the response.

Note: **Mastercard Encryption Keys** will be automatically downloaded upon project creation.

## 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.

## Validate Production Access {#validate-production-access}

After approval and Client ID enablement, configure `https://api.mastercard.com/loyalty/mrs` with Production credentials as listed in [API Basics](https://developer.mastercard.com/transactions-service/documentation/api-basics/index.md#environments). Do not reuse Sandbox keys or test account identifiers in Production. Send an authorized transaction search for an approved Production account and apply the [success-validation checks](https://developer.mastercard.com/transactions-service/documentation/tutorials-and-guides/api-testing-tutorial/index.md#validate-a-successful-response) without running Sandbox negative tests against live accounts. Resolve failures through [Code and Formats](https://developer.mastercard.com/transactions-service/documentation/code-and-formats/index.md) before releasing the integration.