# Onboarding Checklist
source: https://developer.mastercard.com/benefit-allocation-service-mtls/documentation/tutorials-and-guides/onboarding-checklist/index.md

This guide outlines the end-to-end process, Service Level Agreements (SLAs), and requirements for moving your Benefit Allocation Service integration from Sandbox project setup, to MTF testing, then to Production.
Note: The SLA time frames documented on this page apply uniformly across all regions, product tiers, and risk categories. There are no region-specific or product-specific variations for the Benefit Allocation Service API.

### Prerequisites {#prerequisites}

* Complete integration and testing in the MTF environment with a 100% success rate, and complete all required agreements.

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

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

Before starting MTF testing, execute the required Mastercard Customer Agreement. No separate KYC or compliance review step is required for the Benefit Allocation Service API. Standard business verification is completed as part of the contract signing process.

* **Artifacts needed:** Solutions Assessment, Addendum to Mastercard Enhancement Enrollment Agreement Schedule (Benefits Allocation Services), and Data Information Sheet (if applicable)
* **Requirement:** All artifacts must be signed off before the customer gets full access to MTF.
* **SLA:** Contract review and countersignature takes 5--7 business days from submission of all required artifacts.

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

### 2. Sandbox project setup and MTF validation {#2-sandbox-project-setup-and-mtf-validation}

After the contract is signed and your Sandbox project credentials are generated, validate your keys by executing final integration tests against the MTF environment.

This step is complete when all required MTF integration tests pass and final validation is confirmed.

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

After successful MTF validation, request Production keys through the developer portal.

* **Artifacts needed:** Production Access Request (submitted online in Mastercard Developers within your project), [CSR (Certificate Signing Request)](https://developer.mastercard.com/benefit-allocation-service-mtls/documentation/api-basics/index.md#client-authentication) for production certificates, and your application's public IP addresses for the IP address allow list.
* **SLA:** Technical promotion and approval of Production keys takes 3 business days upon submission of the correct artifacts.

Once approved, Production mTLS certificates 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/benefit-allocation-service-mtls/documentation/support/index.md) page.
2. Contact the [API Consultancy \& Standards Support Team](mailto:API_Consultancy_and_Standards@mastercard.com).
3. If your technical promotion request (3 business days) exceeds the SLA without resolution, forward your original case to **[Integration_Escalations@mastercard.com](mailto:Integration_Escalations@mastercard.com)**. Include "SLA EXCEEDED" and the original ticket number in the email subject. You will receive an acknowledgment response within 24 hours.