# Quick Start Guide
source: https://developer.mastercard.com/mastercom-extended/documentation/quick-start-guide/index.md
## Overview {#overview}
Mastercom Extended provides a set of APIs that let you consume data in a variety of ways for efficient and secure querying and updating. This tutorial guides you through the process of onboarding and being able to consume this data.
Tip: **Postman Collections Quick Start:** If you are already ready to start making calls, you can head over to our [Postman Collections](https://developer.mastercard.com/mastercom-extended/documentation/developer-tools/postman-collection/index.md) page to leverage Sandbox and Production environments without having to write code.
>
> #### You can follow this guide to learn: {#you-can-follow-this-guide-to-learn}
>
> * How to create a project for the service.
> * How Mastercard Developers approaches authentication.
> * How to generate your credentials and API client.
> * How to get access to Sandbox and Production.
## Pre-requisites: {#pre-requisites}
* Create a [Mastercard Developers](https://developer.mastercard.com/) account.
* Have a secure place to store downloaded OAuth keys.
* Decide how you want to test: Postman, Insomnia, the reference application, or your own client.
### Sandbox checklist {#sandbox-checklist}
| # | Step | What to do |
|---|-------------|-------------------------------------------------------------------------------------------------------------|
| 1 | Access | Get access to Mastercom Extended and create your Mastercard Developers project. |
| 2 | Credentials | Generate your Sandbox OAuth credentials and record your consumer key. |
| 3 | First call | Send your first Sandbox request using the Sandbox base URL and OAuth 1.0a signing. |
| 4 | Validation | Use the sample response and Testing page to validate test data, positive flows, and negative flows. |
| 5 | Production | After Sandbox validation is complete, use Step 5 and the Onboarding Checklist to request Production access. |
## Step 1: Get access to the API {#step-1-get-access-to-the-api}
1. Navigate to [Mastercard Developers](https://developer.mastercard.com/) and select sign up and create an account.
2. Activate your account by opening the link sent to your email address, and log in.
3. Open your [My Projects](https://developer.mastercard.com/dashboard) page and start a new project. Sandbox access is open, so you can begin testing as soon as your project credentials are generated.
## Step 2: Create a project and generate Sandbox credentials {#step-2-create-a-project-and-generate-sandbox-credentials}
Create a Mastercard Developers project to generate your Sandbox credentials. Sandbox gives you mocked data so you can validate your integration before requesting Production access.
### Project Details {#project-details}
1. Select 'Create new project' on your [My Projects](https://developer.mastercard.com/dashboard) page.
2. Enter a project name.
3. If prompted, indicate whether you are creating the project on behalf of a client.
Note: Check "yes" if you are creating an API integration project for a customer. For example, you could be an integrator, a processor, or a service provider and the customer could be a merchant, issuer, or acquirer.
4. In the 'Select at least one API' field, choose **Mastercom Extended**.
### Service Details {#service-details}
5. Complete the 'Service details' form if it appears.
6. Provide the client company name and client company address (if applicable).
### Project Credentials {#project-credentials}
7. In 'Project Credentials', select the 'OAuth 1.0' radio button for this OAuth 1.0a service.
8. Download, and keep safe, your PKCS#12 (.p12) keystore file.
9. Create a key alias and keystore password for your OAuth keys, record them securely, and click 'Proceed'.
10. Download your OAuth 1.0a keys, store them in a safe place. Click on Open Project.
11. Once you complete this flow, you will land on the Project page. From the Project page, take note of your consumer key and begin testing.
Tip: Review information regarding consumer keys and [Credential Management](https://developer.mastercard.com/platform/documentation/credential-management/).
### Save the values you will need {#save-the-values-you-will-need}
12. On the project dashboard, record the following values:
* Sandbox and Production status
* Authentication consumer key
## Step 3: Make your first Sandbox request {#step-3-make-your-first-sandbox-request}
Once you have Sandbox credentials, make a simple POST request to confirm that your project is set up correctly.
Before you run the request, make sure you have:
* Your Sandbox consumer key
* The private key used to sign OAuth requests
* A Mastercard OAuth library or signer that generates `oauth_timestamp`, `oauth_nonce`, and `oauth_signature`
Note: For a full client setup see the [API Basics](https://developer.mastercard.com/mastercom-extended/documentation/api-basics/index.md) section.
**Example Request (cURL):**
```bash
curl -X 'POST' \
'https://sandbox.dispute.mastercard.com/mastercom-extended/claims' \
-H 'accept: application/json' \
-H 'Content-Type: application/json' \
-d '{
"contextId": "TXN_63cef42e6f7711eaa77feeee0afdc116",
"contextType": "TRANSACTION"
}'
```
> For step-by-step examples see the [Tutorials](https://developer.mastercard.com/mastercom-extended/documentation/tutorialsandguides/index.md).
**Expected Response:**
{
"claimId": "700000000070"
}
> **Test data:** The sandbox includes pre-loaded `201 Created` response and the `claimId`. For a negative-flow test, pass an invalid status value (for example, `?status=INVALID`). The API returns a `400 Bad Request` with a `BAD_REQUEST` reason code. See [Testing](https://developer.mastercard.com/mastercom-extended/documentation/testing/index.md) for additional scenarios.
## Step 4: Choose how you want to test and integrate {#step-4-choose-how-you-want-to-test-and-integrate}
After the first Sandbox request succeeds, pick the integration path that matches your workflow:
* **Postman or Insomnia:** Use the [Developer Tools](https://developer.mastercard.com/mastercom-extended/documentation/developer-tools/index.md) page for collection downloads and setup.
* **Reference Application:** Use the [Reference Application](https://developer.mastercard.com/mastercom-extended/documentation/developer-tools/reference-app/index.md) page.
* **curl or a custom client:** Use the [Testing](https://developer.mastercard.com/mastercom-extended/documentation/testing/index.md) page for test cases and additional examples.
### Generate Your Own API Client {#generate-your-own-api-client}
1. Navigate to the API documentation page.
2. Download the API specification (OpenAPI or Swagger).
3. Generate and configure an API client for this API.
4. Configure your client using our [client libraries](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/#client-libraries). For a detailed step-by-step guide, see [Generating and Configuring a Mastercard API Client](https://developer.mastercard.com/platform/documentation/security-and-authentication/generating-and-configuring-a-mastercard-api-client/).
### Integration Testing {#integration-testing}
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.
Note: The Mastercard Test Facility (MTF) environment is not suitable to perform high-volume or load-testing.
### Contact us {#contact-us}
Contact us when you are ready to onboard with our APIs. Provide your company name, the Mastercard program name (Mastercom Extended), and services that interest you.
Contact details for each region:
**Asia/Pacific:** Contact your account manager.
**Europe:** Contact your account manager.
**[Latin America and the Caribbean](mailto:CIS_LAC_Support@mastercard.com)**
**[Middle East and Africa](mailto:CIS_EEMEA@mastercard.com)**
**[North America](mailto:CIS_NorthAmerica_Support@mastercard.com)**
A regional customer representative will work with you on how to order this product through the [Mastercard Connect Store](https://www.mastercardconnect.com/-/store-plus), set up BINs, ARIDs and ICAs, and promote the Sandbox keys to MTF.
## Step 5: Promote the same project to Production {#step-5-promote-the-same-project-to-production}
Once your project is working in Sandbox, request Production access for that same project.
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.
Prerequisite: Complete [Company Verification](https://developer.mastercard.com/platform/documentation/account-management/company-verification-via-connect-linking/) before requesting Production access.
### Transition your project from Sandbox to Production {#transition-your-project-from-sandbox-to-production}
1. **Open your project in Mastercard Developers** Go to your [My Projects](https://developer.mastercard.com/dashboard) page and open the Mastercom Extended project you used for Sandbox testing.
2. **Request Production access** In the project dashboard, select 'Request Production Access'. Your Sandbox and Production statuses are shown separately on the project page, so you can track when Production moves from `Not Requested` to an enabled `Ready` state.
Note: Production Credentials are generated instantaneously, but they still need to be approved for Production environment access before you can go live. Once your Production access request has been reviewed, you will receive a notification confirming your access has been approved or denied.
3. **Generate or download your Production keys** After Production access is approved, download the Production OAuth keys for the same project. Keep the Production key material separate from your Sandbox keys.
4. **Update your application configuration** Switch the base URL from Sandbox to Production:
* Sandbox Global:
* Production Global:
* Sandbox India:
* Production India:
OAuth 1.0a authentication works the same way in Sandbox and Production. The main changes are the Production key set, the Production approval state, and the Production base URL.
If you need the full onboarding process, including contract, MTF, SLA, and escalation details, see the [Onboarding Checklist](https://developer.mastercard.com/mastercom-extended/documentation/tutorials-and-guides/onboarding/index.md).
## Next Steps {#next-steps}
Continue with the documentation that matches your next task:
* [API Reference](https://developer.mastercard.com/mastercom-extended/documentation/api-reference/index.md) for endpoint details
* [API Basics](https://developer.mastercard.com/mastercom-extended/documentation/api-basics/index.md) for authentication and client configuration
* [Testing](https://developer.mastercard.com/mastercom-extended/documentation/testing/index.md) for additional request scenarios
* [Onboarding Checklist](https://developer.mastercard.com/mastercom-extended/documentation/tutorials-and-guides/onboarding/index.md) for the full operational go-live process
* [Use Cases](https://developer.mastercard.com/mastercom-extended/documentation/use_cases/index.md)