---
title: "Open banking"
description: "Learn how to integrate with the Adyen Open Banking platform."
url: "https://docs.adyen.com/business-accounts/open-banking"
source_url: "https://docs.adyen.com/business-accounts/open-banking.md"
canonical: "https://docs.adyen.com/business-accounts/open-banking"
last_modified: "2026-06-01T15:33:15+02:00"
language: "en"
---

# Open banking

Learn how to integrate with the Adyen Open Banking platform.

[View source](/business-accounts/open-banking.md)

Open banking is a regulatory initiative that was introduced in Europe in 2018 through the Revised Payment Services Directive ([PSD2](https://www.adyen.com/knowledge-hub/psd2). It requires financial institutions, such as Adyen, to provide secure access to their customers' data and allow third-party providers to initiate payments on behalf of the customer with the customer's explicit consent. Adyen provides secure open banking APIs that let third-party service providers interact with Adyen business accounts and get the account holders' consent for those interactions.

This documentation is for third-party providers and explains how they can interact with Adyen business accounts to:

* Retrieve account information

* Initiate payments

* Confirm funds

  This is not [Pay by Bank (Europe)](/payment-methods/pay-by-bank-europe) or [Pay by Bank (US)](/payment-methods/pay-by-bank-us) , which is a specific payment method within Checkout.

## Requirements

| Requirement          | Description                                                                                                                                                                                                                                                                                                                                                                                             |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Integration type** | Not applicable; this documentation is intended for third-party providers.                                                                                                                                                                                                                                                                                                                               |
| **Limitations**      | This documentation is for the EU region only. For UK documentation, see the [Open Banking documentation](https://openbankinguk.github.io/read-write-api-site3/v4.0/profiles/read-write-data-api-profile.html). Also, see a list of [supported countries and regions](#supported-countries-and-regions).                                                                                                 |
| **Setup steps**      | If you are a third-party service provider seeking access to Adyen's open banking interfaces, you must:- Be licensed by a national regulatory authority.
- Have a Qualified Website Authentication Certificate (QWAC). This can be obtained from [Qualified Trusted Service Providers](https://webgate.ec.europa.eu/tl-browser/#/) (QTSP).
- Complete the [Adyen onboarding steps](#onboard-with-adyen). |

## Adyen open banking APIs

Adyen's open banking interface provides a secure and reliable way for third-party providers to access Adyen's APIs and interact with the data of Adyen business accounts. This involves the use of APIs that allow third-party providers to access and use financial data from financial institutions. Typically, the Adyen open banking flow has three participants:

* **Adyen business account holder**: This is an account holder that has a business account with Adyen, often referred to as the *payment service user* in the open banking industry.

* **A third-party provider**:

  * An **account information service provider (AISP)**: a third-party provider that requests information about Adyen business accounts.
  * A **payment initiation service provider (PISP)**: a third-party provider that initiates payments from Adyen business accounts.
  * A **payment instrument issuer service provider (PIISP)**: a third-party provider that requests information about the available funds in Adyen business accounts.

* **Account servicing payment service provider**: Adyen, as the financial institution that manages the business accounts of the account holders.

Adyen provides third-party providers with the following regulatory APIs:

* **Open Banking API for the EU**: Follows the [NextGenPSD2](https://www.berlin-group.org/nextgenpsd2-downloads) standard created by [The Berlin Group](https://www.berlin-group.org).
* **Open Banking API for the UK**: Follows the [Open Banking API specifications](https://standards.openbanking.org.uk/api-specifications) created by [Open Banking Limited](https://www.openbanking.org.uk/about-us).

### Base URL and API structure

The table below describes the structure of each API request URL.

| Description               | Value                                                                                                                                                                           |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test base URL**         | `https://openbanking-psd2-test.adyen.com`                                                                                                                                       |
| **Live base live URL**    | `https://openbanking-psd2-live.adyen.com`                                                                                                                                       |
| **Region identifier**     | * `obeu` for EU APIs.
* `obuk` for UK APIs.                                                                                                                                     |
| **Third-party providers** | - `/asip` for account information service providers for EU APIs.
- `/pisp` for payment initiation service providers.
- `/piis` for payment instrument issuer service providers. |
| **API version**           | The version of the API. Currently, `/v1` is supported.                                                                                                                          |
| **Endpoint**              | The specific resource you are accessing (for example, `/accounts`).                                                                                                             |

**Example URL**\
`https://openbanking-psd2-live.adyen.com/obeu/pisp/v1/accounts`

## How it works

The typical open banking flow with Adyen is as follows:

1. An account holder requests a service from a third-party provider. The third-party provider can only ask for those scopes agreed to by the account holder.

2. The third-party provider requests the account holder to:

   1. Authenticate themselves with Adyen.
   2. Provide consent to Adyen to allow the third-party provider to perform the requested service.

3. If the previous step is successful, Adyen allows the third-party provider to use the open banking API.

4. Adyen sends the requested information through the open banking API.

## Onboard with Adyen

To integrate with the Adyen's open banking interface, third-party providers need to register and obtain the necessary credentials to access the APIs. They also need to ensure that their systems comply with the relevant security and data protection requirements. Third-party service provider must be licensed by a national regulatory authority and have a Qualified Website Authentication Certificate (QWAC). This can be obtained from [Qualified Trusted Service Providers](https://webgate.ec.europa.eu/tl-browser/#/) (QTSP).

1. To onboard with Adyen as a third-party provider, gather the required information:

   * **QWAC certificate**: PEM-formatted QWAC certificate file. Add the certificate as an attachment.

   * **Redirect URL**: This URL used to redirect successful authentications with the authorization code.

   * **Third-party provider website**: Your website URL.

   * **Scopes**: The scopes to be enabled for your OAuth client. The available scopes are:

     * **AISP**
     * **PISP**
     * **PIISP**

2. Send an email to <openbanking@adyen.com>. Adyen reviews your information and sends you the **client ID** and **client secret** used in the [OAuth flow](/business-accounts/oauth-flow) to get access token.

## Supported countries and regions

The table shows the supported countries and regions, and availability. This documentation is for the EU region only. For UK documentation, see the [Open Banking documentation](https://openbankinguk.github.io/read-write-api-site3/v4.0/profiles/read-write-data-api-profile.html).

| Countries/regions | Account information                                                                         | Payment                                                                                     | Funds check                                                                                 |
| ----------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| EU                | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") |
| UK                | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") |

## Next steps

[required](/business-accounts/oauth-flow)

[Authentication](/business-accounts/oauth-flow)

[Implement OAuth 2.0 to enable secure communication with Adyen.](/business-accounts/oauth-flow)

[required](/business-accounts/consent)

[Consent interface](/business-accounts/consent)

[Learn how to manage user consents with our dedicated endpoints.](/business-accounts/consent)

[AISP interface](/business-accounts/aisp)

[Learn how to consume our dedicated AISP endpoints.](/business-accounts/aisp)

[PISP interface](/business-accounts/pisp)

[Learn how to consume our dedicated PISP endpoints.](/business-accounts/pisp)

[PIISP interface](/business-accounts/piisp)

[Learn how to consume our dedicated PIISP endpoints.](/business-accounts/piisp)
