# Create a Project in Sandbox
source: https://developer.mastercard.com/mastercard-checkout-solutions/tutorial/onboarding-sandbox/step6/index.md

## 6. Create a Project in Sandbox {#6-create-a-project-in-sandbox}

On the **Projects** tab, click **Create project**, fill out the form, and read the necessary requirements to create your first project.
Warning:   

* The **Create project** button on the **Projects** tab is visible only after enrolling for a specific program on the **Program Enrollment** tab.   

* Your project attributes (SRC Client ID, support emails, keys, DPAs) cannot be shared across Sandbox projects or Production environments.

You can create a maximum of 30 Sandbox projects. You can contact your [Mastercard representative](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/support/index.md#get-help) if you would like to create more than that. Each sandbox project has distinct attributes (SRC Client ID, support emails, keys, \& DPAs) to perform testing across various lower environments. For example, you may have one or more environments for integration and testing.
Tip: SRC Client ID is the identifier for the connecting client, refer to the [API Specifications](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/api-reference/apis/index.md) to learn more.

### 6.1 Provide Project Details {#61-provide-project-details}

![Create a Project](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/images/mcc_create_project_step1.png "Fill Project Details")

To create a Sandbox project, provide the following information:

* **Select the program** --- select the program(s) you want to include in this Sandbox project.

* **Project Name** --- the name of the project.

* **Description** --- a brief description of your project.

<!-- -->

* **Notifications** --- Support email addresses will receive notifications related to their Mastercard Checkout Solutions onboarding application project. These email addresses are used for support or troubleshooting. You can add up to 4 email addresses by clicking the **Add** button.

<!-- -->

* **Requirements** --- You should be eligible to accept payment credentials in the payload response returned by Mastercard. Select the check box and click **Continue** to create a project and move to Program selection.

### 6.2 Choose Programs for your Project {#62-choose-programs-for-your-project}

![Choose a Program for a Project](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/images/edo_chooseprograms1.png "Choose a Program")

* **Choose enrolled programs** --- select the program(s) you want to include in this project. The enrollment form will vary depending on the program type being requested:

There is no enrollment form for this program. There is no enrollment form for this program. For Commerce Platforms who want to become an integrator. You can specify only one Commerce Platform name.
For merchants who want to integrate directly with Mastercard for tokenization programs, e.g. large streaming merchant, can have between 1 and 20 program names.
There is no enrollment form for this program. It is for service providers who want to provide merchant tokenization programs to their merchants.

The program names for this model are generated using the [Submit DPA Data API](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/api-reference/apis/index.md#registration) endpoint and do not require user input during enrollment.
There is no enrollment form for this program. It is for service providers who want to provide tokenization programs to their sub-merchants. Payment Facilitator (Service Provider) uses a `serviceId` to register a group of sub-merchants. A `serviceId` is shared between sub-merchants.
Tip: Mastercard provides upto five `serviceId` to Payment Facilitator. The Payment Facilitator should register their sub-merchants as `srcDpaId` within each `serviceId` that they will use. Mastercard recommends segmenting sub-merchants into `serviceId` based on Merchant Category Code (MCC).

The program names for this model are generated using the [Submit DPA Data API](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/api-reference/apis/index.md#registration) endpoint. Up to five program names can be generated to be used amongst the sub-merchants.
For Technical Integrators who want to provide technical integration service for their commerce platforms.   

In step 2 of project creation (refer to the above image), provide the consumer-facing name of the commerce platform, and assign the client name with the company ID combination.   

![OBO Project](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/images/edo_obocp1.png "OBO Project")

* The program name is mapped with the merchant's consumer-facing name, or the entity that stores the cardholder's credentials on file. It is recommended to choose an accurate program name that Issuer uses to identify the merchant during tokenization and transaction authorization. Depending upon the model you are enrolling in, you can edit or remove one or more Program Names or Commerce Platform Names for the selected program type.

<br />

* Click **Create Project** to complete the step.

* Each project will be visible as a separate tile on the **Projects** tab.

![Projects Tab](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/images/edo_projectpage1-DUP3.png "Projects tab")

### Understanding a Project Tile {#understanding-a-project-tile}

On the **Projects** tab, a tile will be visible for each project. The following callouts help you understand the information contained within a project tile.

![Understand Project Tile](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/images/mcc_project_tile.png "Project tile")

1. Denotes a program included in the project.
2. Denotes a program enrolled in Production but not included in this project.
3. A red dot indicates that Mastercard could not generate a `serviceid` for a program. An amber dot indicates that a `serviceid` generation for a program is in progress.
4. Allows you to edit the email addresses and other details related to the project (except Project name).
5. Indicates the project status as **Approved**.