Open banking support
Stripe supports open banking so third parties can access a Stripe account.
The second EU Payment Services Directive (PSD2) implements an access model that requires providers of payment accounts to create interfaces to allow authorized third-party providers to access user accounts with the user’s consent. This is known as access to accounts, or open banking.
Open banking allows third parties to request three types of access to users’ payment accounts:
- Access account information: Account Information Service Providers (AISPs) can view transaction history of a payment account.
- Confirming that funds are available: Before a payment can be completed, Card-Based Payment Instrument Issuers (CBPIIs) or Payment Initiation Service Providers (PISPs) can check if the balance of an account has sufficient funds.
- Initiating new payments: Payment Initiation Service Providers (PISPs) can initiate a payment from a user’s payment account.
The aim of open banking is to encourage collaboration across the banking industry and provide consumers with more options to access information and functionality across their financial institution accounts.
How third parties access Stripe accounts![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
Since its inception, Stripe has provided a full suite of APIs for third parties to request access to any Stripe user account using OAuth. Stripe’s existing OAuth system allows for two types of access:
Access type | Stripe API functionality |
---|---|
read_ OAuth scope | Read most API resources |
read_ OAuth scope | Read and write most API resources |
Many third parties have built extensions using our existing OAuth flow. We recommend that most builders of third-party extensions continue to use our existing OAuth flow; you can find the documentation here.
However, to support open banking, we provide three types of access:
Access type | Stripe API functionality |
---|---|
open_ OAuth scope | Read Application Fees, Balances, Charges, Disputes, Payouts, Refunds, Top-ups, Transfers, and Balance Transactions |
open_ OAuth scope | Read Balances |
Payment Initiation Request API | Create Payouts to an External Account on file, and create Transfers to a connected Stripe account |
We encourage you to compare our existing OAuth system with these open banking APIs to see which solution makes sense for you. Only a limited subset of Stripe user accounts are eligible to be accessed using the Open Banking APIs.
eIDAS certificates![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
To use Stripe’s Open Banking APIs, third parties need to obtain an eIDAS QWAC certificate that identifies them as an AISP, PISP, and/or CBPII in good standing. These certificates are issued by European signing authorities, known as trust service providers (TSPs).
Contact us if you think you need access to our Open Banking APIs.
Open banking on FinancialAccounts![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
For information related to open banking support on our FinancialAccounts based products, see the API documentation.
Our Open banking API performance metrics provide visibility into availability and performance in the last quarter. We update these metrics quarterly.