# Getting Started
source: https://developer.mastercard.com/mdes-token-connect/documentation/getting-started/index.md

## Before You Start {#before-you-start}

You must already be integrated with Mastercard Digital Enablement Service (MDES) before you can integrate with MDES Token Connect. To familiarise yourself with high-level MDES use cases, refer to [MDES Issuer Implementation Guide](https://techdocs.mastercard.com/bundle/m_MIIG/page/r_SmryChngsMIIG.html?frontSlug=Payment%20Services).

## Good to Know {#good-to-know}

Regional Availability:

* Global

### Compatibility {#compatibility}

MDES Token Connect is compatible with account ranges that Issuers have enabled for MDES:

* Mastercard card account ranges
* Maestro card account ranges
* 'Pay with Bank Account' financial account ranges

<br />

For inquiries about Private Label account ranges, please contact your Mastercard representative.

### Connections {#connections}

The following connections are supported:

* Issuer website to token requestor website
* Issuer website to token requestor app (Android and iOS) on same device
* Issuer app (Android and iOS) to token requestor app (Android and iOS)
* Issuer app (Android and iOS) to token requestor website

## Get Started {#get-started}

### 1. Plan {#1-plan}

#### Scope your Project {#scope-your-project}

* Which of your customer interfaces will support Push Provisioning with MDES Token Connect?
  * Mobile Banking App (Android and/or iOS)
  * Online Banking (web browser)
* Will you support a Callback URL for Token Requestors to redirect the consumer back to your banking website or mobile app?
* If the Token Requestor supports this option, will you push multiple cards simultaneously to the Token Requestor?
* Will you support Streamlined Activation? See [MDES Token Connect Issuer Interface Implementation Guide](https://developer.mastercard.com/mdes-token-connect/documentation/tutorials-and-guides/issuer-implementation-guide/index.md) for details.
* Will you send account holder data to Token Requestors that accept it? See [MDES Token Connect Issuer Interface Implementation Guide](https://developer.mastercard.com/mdes-token-connect/documentation/tutorials-and-guides/issuer-implementation-guide/index.md) for details.

#### Define your Security Policy {#define-your-security-policy}

* Review the [MDES Issuer Implementation Guide](https://techdocs.mastercard.com/bundle/m_MIIG/page/c_MIIG_IssuerInitiatedDigitizationwithMDESTokenConnect.html) for security details about MDES Token Connect (login to Mastercard Connect is required).
* In which circumstances will you decline the issuer-initiated tokenization request?
* When will you require additional authentication?
* When will you accept the tokenization request?
* Which entity will execute the security policy: static MDES pre-digitization rules or your authorization/back-end server?

### 2. Develop {#2-develop}

#### Try the Sandbox {#try-the-sandbox}

* Review the MDES Token Connect [API Reference](https://developer.mastercard.com/mdes-token-connect/documentation/api-reference/index.md).
* Create a new MDES Token Connect API project in Mastercard Developers and generate the keys required to gain access to the Sandbox environment.
* Generate your own MDES Token Connect API client and use it against the MDES Token Connect sandbox. Refer to [How to Consume the MDES Token Connect API?](https://developer.mastercard.com/mdes-token-connect/documentation/api-basics/index.md) for more information.

Note: Please use MDES Token Connect API to test in Sandbox environment.

#### Create {#create}

* Using the [MDES Token Connect Issuer Interface Implementation Guide](https://developer.mastercard.com/mdes-token-connect/documentation/tutorials-and-guides/issuer-implementation-guide/index.md), create wireframes for mobile and/or desktop users before and after the integration with the Token Requestor.
* Contact your Mastercard representative, indicate your will to implement Token Connect, and provide your wireframes. Mastercard will review your wireframes against the [Design Check-list](https://developer.mastercard.com/mdes-token-connect/documentation/tutorials-and-guides/issuer-implementation-guide/index.md#summary-user-interface-design-check-list).

#### Implement {#implement}

* Implement the wireframes for mobile apps and web browser.
* Move your MDES Token Connect sandbox code to your MTF back-end server.
* Integrate mobile apps and web server with your back-end server.
* Implement on your authorization/back-end server the changes related to your security policy, if needed.

### 3. Deploy {#3-deploy}

#### Contact Us {#contact-us}

* Contact your Mastercard Customer Delivery Manager to open a Customer Integration Services (CIS) project for your MDES Token Connect implementation. Note that it usually takes several days to obtain a CIS project number.
* Once you have obtained your CIS Project Number, you are ready to move your project to Production.

#### Test {#test}

* The Customer Implementation Services (CIS) team will grant you access to the MTF environment, and they will supply you with a list of applicable test cases for your implementation.
* Test your implementation in the MTF environment, using our fictitious test merchants **ProFilmHub** and **ProMovieHub**.

Warning: **ProFilmHub** and **ProMovieHub** are fictional merchants and services. Any similarity to an existing service is entirely coincidental. Mastercard created these merchants (the "Stores") for the sole purpose of allowing its authorized issuers to perform integration testing with the MDES Token Connect service in a preproduction test environment. For avoidance of doubt, goods or services cannot be purchased via the Stores. **The system is not intended to collect or retain personal information. Only fictitious or dummy data should be used.** All testing should be performed using only issuer test devices. Note: **ProFilmHub** and **ProMovieHub** are not supporting pull proivisioning.

* Once your CIS Implementation Manager grants you access to the Production environment, perform the friendly user testing in the Production environment.
* You're ready to go live!

### 4. Manage {#4-manage}

* Determine what has changed with each release by reviewing the [Release History](https://developer.mastercard.com/mdes-token-connect/documentation/pre-release-notes/index.md).
* To avoid any service outage, make sure to renew your project keys before they expire! See the tutorial to renew [OAuth Consumer Key](https://developer.mastercard.com/platform/documentation/security-and-authentication/using-oauth-1a-to-access-mastercard-apis/#renewing-keys).

## Next Steps {#next-steps}

Please refer to the following sections for more information:

* [API Basics](https://developer.mastercard.com/mdes-token-connect/documentation/api-basics/index.md) section to understand some foundational material.
* [Tutorials and Guides](https://developer.mastercard.com/mdes-token-connect/documentation/tutorials-and-guides/index.md) section to understand the integration steps.