# Create a Sandbox Project
source: https://developer.mastercard.com/identity-insights-solutions/documentation/tutorials-and-guides/sandbox-access/index.md

This guide walks through the steps required to create a new Identity Insights Solutions project and how to gain access to the sandbox environment.

#### What You Will Learn {#what-you-will-learn}

* How to create a Mastercard Developers sandbox project
* How to configure a Mastercard Developers sandbox project

## Step 1: Create a Project {#step-1-create-a-project}

1. To begin you should go to your dashboard, you can do this by clicking on the [My Projects](https://developer.mastercard.com/dashboard) option in the menu.
2. You can create a new project by clicking the **Create New Project** button, in the upper right portion of the screen. ![](https://static.developer.mastercard.com/content/identity-insights-solutions/uploads/new-project-button2.png)

## Step 2: Add Identity Insights Solutions API to your Project {#step-2-add-identity-insights-solutions-api-to-your-project}

1. Enter a descriptive name for your project in **Project name**.
2. Select the "No" option if you are directly employed by the company the project is being created for. If you are creating it on another company's behalf then select the "Yes" option and add the appropriate details for that company.
3. Select **Identity Insights Solutions** from the drop-down list.
4. Click **Proceed** . ![](https://static.developer.mastercard.com/content/identity-insights-solutions/uploads/api-selection2.png)

## Step 3: Configure Service details {#step-3-configure-service-details}

1. Add **Interbank Card Association number**. The Mastercard assigned ICA is used for
   customer identification when sending a transaction to Mastercard Identity Insights Solutions API. The ICA will
   also be used for billing of usage of Identity Insights Solutions.

   Contact your [Mastercard representative](https://developer.mastercard.com/identity-insights-solutions/documentation/support/index.md#how-can-i-find-who-is-my-mastercard-representative) for ICA-related questions.

Note: Ensure the veracity of these details as they cannot be changed after Project Creation.

2. If you would like to participate in the pilot program for sharing identity data with Issuer, select the **Yes** radio button related to sharing data with Issuers, otherwise select **No**.

   Contact your [Mastercard representative](https://developer.mastercard.com/identity-insights-solutions/documentation/support/index.md#how-can-i-find-who-is-my-mastercard-representative) for more information on this pilot program.

Note: The associated terms and conditions displayed in subsequent dialogs will need to be accepted to participate in this pilot.

3. If you would like to be able to access the Identity Risk Score as a standalone product offering independently of Identity Insights for Transactions, select the **Yes** radio button related to identity-based risk evaluation signals, otherwise select **No**.

   Contact your [Mastercard representative](https://developer.mastercard.com/identity-insights-solutions/documentation/support/index.md#how-can-i-find-who-is-my-mastercard-representative) to confirm, you meet the eligibility requirements for this product.

Note: The associated terms and conditions displayed in subsequent dialogs will need to be accepted to access the Identity Insights Risk Score. This selection does not impact access to Identity Insights for Transactions, as this requires a commercial contract to be signed, which can be facilitated through your Mastercard representative.

4. Click **Proceed** . ![](https://static.developer.mastercard.com/content/identity-insights-solutions/uploads/service-details2.png)

## Step 4: Legal Agreements {#step-4-legal-agreements}

1. Accept the terms and conditions associated to your choices in the previous dialog.

   If you selected 'No' to both options then click 'Proceed' without accepting the Terms and Conditions.

![](https://static.developer.mastercard.com/content/identity-insights-solutions/uploads/legal-agreements1.png)

## Step 5: Add Project Credentials {#step-5-add-project-credentials}

Project credentials for Sandbox can be generated either as part of the project creation flow, or after the project has been created.

A pre-existing Certificate Signing Request (CSR) can only be done after the project has been created.

### Add Sandbox Credentials following Project Creation {#add-sandbox-credentials-following-project-creation}

To create the Sandbox Credentials independently of the project creation flow, click the **Skip This Step** button.
![](https://static.developer.mastercard.com/content/identity-insights-solutions/uploads/skip-credentials.png)

### Add Sandbox Credentials as part of Sandbox Creation {#add-sandbox-credentials-as-part-of-sandbox-creation}

Once your project has been created, follow the [mTLS Certificates](https://developer.mastercard.com/platform/documentation/credential-management/mtls-certificate-management/) section of the Developer Zone Platform Overview Space to add a key to your project.

To generate credentials as part of the project creation flow:

1. Enter the Certificate alias along with the Keystore password, taking note of the values used as these will be needed later in this workflow.
2. Specify the values to be included within the Distinguished Name (DN) of the CSR.

Follow the guidelines outlined within the [Security](https://developer.mastercard.com/platform/documentation/security-and-authentication/mtls-csr-requirements/) section of the Developer Zone Platform Overview Space.

3. Click **Proceed**.

![](https://static.developer.mastercard.com/content/identity-insights-solutions/uploads/add-credentials.png)

## Step 6: Additional credentials {#step-6-additional-credentials}

Click **Create project** to complete the project creation process.
![](https://static.developer.mastercard.com/content/identity-insights-solutions/uploads/additional-credentials2.png)

Payload Encryption is an optional capability available to customers alongside MTLS Encryption. The use of Payload Encryption increases the latency associated with the processing of requests.

Additional credentials to facilitate payload encryption are automatically generated when "Create project" is clicked. The "Download key file" is presented on project creation completion.
![](https://static.developer.mastercard.com/content/identity-insights-solutions/uploads/download-key.png)

Clicking the "Download key file" option downloads the sipped key file to the default location for your browser.

The zipped file contains:

1. \*-signing.crt file containing the **mTLS certificate**.
2. \*-private-key.key file containing the **mTLS private key**, which is secured by the Keystore password specified earlier in the flow.
3. *identity-insights-for-transactions-clientenc-* -client-encryption-key.pem file containing the **client encryption certificate**.

When you click 'Open Project' button, you will be redirected to the Project Summary Page from where you can access the various keys generated.
Tip: To encrypt a JSON payload with the downloaded keys, use a tool (such as Open SSL) to first extract the public key from
the CRT file as a PEM file, and then utilize this PEM file within your encryption operation.

The following command can be used to convert the crt file to a pfx file:

`openssl pkcs12 -export -out <certificate.pfx> -inkey <keyfile.key > -in <certificate.crt>`
![](https://static.developer.mastercard.com/content/identity-insights-solutions/uploads/key-creation1.png)