# Open Banking Connect APIs
source: https://developer.mastercard.com/open-banking-connect/documentation/index.md

Release 1.64.0  

[Release Notes](https://developer.mastercard.com/open-banking-connect/documentation/specification-release-notes/index.md)

## Overview {#overview}

Mastercard Open Banking Connect provides a unified set of APIs that enable Third Party Providers (TPPs) to connect to Account Servicing Payment Service Providers (ASPSPs) APIs through the Mastercard TPP Connectivity Hub.

* For Account Information Service (AIS) functionality, see the [Open Banking Connect Account Information Service API Documentation](https://developer.mastercard.com/open-banking-connect/documentation/aisfeatures/overview/index.md).
* For Payment Initiation Service (PIS) functionality, see the [Open Banking Connect Payment Initiation Service API Documentation](https://developer.mastercard.com/open-banking-connect/documentation/pisfeatures/overview/index.md).

## Environment Domains {#environment-domains}

* Sandbox
* Pre-Production
* Production

```Sandbox
https://sandbox.api.mastercard.com/openbanking/connect/api
```

```Pre-Production
https://api.mastercard.com/openbanking/connect/preprod/api/
```

```Production
https://api.mastercard.com/openbanking/connect/api/
```

#### Pre-Production environment {#pre-production-environment}

Pre-Production (Pre-Prod) is a live environment provided by Open Banking Connect in addition to Sandbox and Production, where onboarded TPPs can perform live proving/testing activities before the code is released in Production and affects real customers.  

Pre-Prod is a close replica of Production with some limitations (for example, Power BI data is not available). TPPs operate with real data in Pre-Prod which may result in real transactions and account updates. No additional TPP onboarding is needed to use Pre-Prod. However, TPPs should contact their Mastercard representative ([openbankingeu_support@mastercard.com](mailto:openbankingeu_support@mastercard.com)) to define the list of ASPSPs they want to work with in Pre-Prod. If the TPP is not yet registered with any ASPSPs, they will need to go through the standard registration process before those ASPSPs can be added. In case a TPP intends to use a different, separate redirect URI that is not already registered with the ASPSP, they should firstly register it with the ASPSP.  

Pre-Production releases will be performed at the same time as Sandbox releases. In this way, TPPs can do live proving of new functionalities or new ASPSPs before the code is released in Production and affects real customers.

## How It Works {#how-it-works}

![How it works](https://static.developer.mastercard.com/content/open-banking-connect/img/how-it-works-update12.png)

The individual components are as follows:

1. A TPP-facing single/unified set of APIs, defined by Mastercard Open Banking Connect, allowing standardized connection with us, made available through a Mastercard gateway.  
2. A message validation layer, checking if the request received from the TPP is complete, and verifying that the service being requested is in line with the permissions defined by the TPP license (for example, checking if the correct TPP license is held, if notified in the country of the ASPSP, and so on.).  
3. A message translation layer that performs the conversion of the request received from the TPP into the format required by the target ASPSP.  
4. Connectivity maintenance layer, assuring that the connections are robust. The maintenance layer also ensures that regular upgrades are made available in a robust and timely manner.  
5. An onboarding module, allowing TPPs to register with us with ease.  
6. A fully functional sandbox environment, matching the specification of the full production environment, allowing for testing of all APIs (current and forthcoming releases).  
7. Pre-Production (further named Pre-Prod) is a live environment provided by Open Banking Connect in addition to Sandbox and Production, where onboarded TPPs can perform live proving/testing activities.  
8. Full certificate management capability, enabling the setup, facilitation and management of the certificates required by TPPs and ASPSPs.  
9. A suite of support services, ranging from help facility (email, chat and phone), set of documentation of existing services and announcements on forthcoming enhancements, and account management tools.  
10. An outward gateway that sends messages to and receives responses from the ASPSPs potential through a network of connectivity partners.

Our service will cater for a whole range of TPP use cases. Since we assume the role of the TSP, we leave the decisions on the specific user experiences, presentation of the underlying data, and the duty to obtain and store the relevant user consents on the TPPs using our services.

## More Information {#more-information}

See tutorials and topic-specific information in our [Knowledge Base](https://developer.mastercard.com/open-banking-connect/documentation/tutorials/index.md).  

See topic-specific questions in our [Frequently Asked Questions](https://developer.mastercard.com/open-banking-connect/documentation/frequently-asked-questions/index.md) section.

## Get Help {#get-help}

### Contact us for technical support. {#contact-us-for-technical-support}