# Onboarding Checklist
source: https://developer.mastercard.com/mastercom-extended/documentation/tutorials-and-guides/onboarding/index.md

This guide outlines the end-to-end process, Service Level Agreements (SLAs), and requirements for moving your Mastercom Extended integration from the Sandbox environment to Production.
Note: The SLA time frames documented on this page apply uniformly across all regions, product tiers, and risk categories. Note: Service providers are provisioned by acquirers.

### Prerequisites {#prerequisites}

* Completed integration and testing in the Sandbox environment with a 100% success rate.

## Step-by-Step Workflow {#step-by-step-workflow}

### 1. Contract signing and agreement {#1-contract-signing-and-agreement}

Once you have completed Sandbox testing, execute the required Mastercard License Agreement.

* **Artifacts needed:** Signed License Agreement Form
* **SLA:** Uploaded to a centralized database 5--7 business days from the time you submit all required artifacts.   

This step is complete when the contract is signed and returned by Mastercard.

### 2. Mastercard Test Facility (MTF) validation {#2-mastercard-test-facility-mtf-validation}

After the contract is signed and your MTF project keys are generated, execute your final integration tests against the MTF environment.

This step is complete when the Customer Implementation Service (CIS) team has verified your MTF tests.

After the MTF keys have been configured, test data is loaded and integration testing begins. Your project contact works with you to ensure that sufficient test data is added, and that each endpoint and use case is tested.

### 3. Technical promotion and Production enablement {#3-technical-promotion-and-production-enablement}

After integration testing in MTF is completed, your customer representative works with you to schedule your go-live date and production access. A user must have the correct Mastercom Extended API BIN or ARID access in Access Manager within Mastercard Connect before a Production client ID can be mapped to their account. A Production client ID is associated with one Mastercard Connect User ID.

After successful sign-off on Sandbox or if applicable MTF validation, request Production keys via the developer portal.

* **Artifacts needed:** Production Key Request Form, CSR (Certificate Signing Request) for production certificates
* **SLA:** Technical promotion and approval of production keys takes three business days upon submission of the correct artifacts.   

Once approved, Production OAuth and encryption keys are available for download from your project dashboard on [Mastercard Developers](https://developer.mastercard.com/dashboard). You will receive an email notification confirming that Production access has been activated for your project.

This step is complete when Production keys are downloaded from the portal, the activation confirmation email is received, and your application is live using the Production base URL.

## Escalation Paths {#escalation-paths}

If these SLAs are exceeded or you encounter blockers during onboarding, use the following channels:

1. Submit a technical support request using the Get Help button on the [Support](https://developer.mastercard.com/mastercom-extended/documentation/support/index.md) page.
2. Contact your assigned Mastercard representative.

If your contract time frame (5--7 business days) or technical promotion request (three business days) has exceeded the SLA without resolution, contact your Mastercard representative.

## Next Steps {#next-steps}

* Visit [Support](https://developer.mastercard.com/mastercom-extended/documentation/support/index.md) for FAQs and troubleshooting guidance.