Skip to main content
Logo
API Documentation Status page Submit a request
Sign in
  1. Bank Account Data
  2. Bank Account Data API
  3. Authentication

What is continuous access and why is it limited to 180 days?

Continuous access, in the context of Open Banking API in Europe, refers to the ongoing and real-time access that authorized third-party providers (TPPs) have to a customer's bank account information. It allows TPPs to retrieve transaction data, balances, and other relevant details directly from the customer's bank account on a regular basis.

The duration of continuous access is typically determined by the consent provided by the customer during the authentication process. The customer can specify the duration for which they authorize the TPP to access their account information. 

Recently, there has been an update to the Regulatory Technical Standards regarding Open Banking in Europe. Previously, banking institutions were required to ensure that Third Party Providers (TPPs) could access linked accounts for 90 days after authentication without requiring the end user to re-authenticate. However, this duration has now been extended to 180 days.

This extension is crucial for various applications and use cases that rely on real-time access to transaction data. For example, budgeting apps and accounting platforms need to continuously gather new transaction information as it happens.

The extended access period applies to account information services and is valid for 180 days at the Account Servicing Payment Service Provider (ASPSP). This change aligns with the requirement to apply strong customer authentication, as outlined in Article 10a of the Regulatory Technical Standards(read more about it here).

It's important to note that this time-frame applies to all PSD2 APIs and all Third Party Providers connecting to these APIs. This update provides more flexibility and convenience for TPPs and the applications they support, allowing for a longer duration of continuous access to account information without the need for frequent re-authentication.

Read more about EEA 180-day access in our article here.

Was this article helpful?
  • Promoted articles

    • Bank Account Data API Usage - how is your usage number calculated
    • EEA 180-day access
    • Bank Account Data API Rate Limits
    • How to recognise and handle end user authentication errors
    • Account Endpoint Errors and Suspended Accounts
  • Recently Added Articles

  • Top Articles

Bank Account Data Quickstart Guide

Simple and streamlined guide to start using our Bank Accoun Data API

Quickstart Guide

Demo page of our Bank Account Data API

See the product in action with few easy clicks

Bank Account Data Demo

Need Support?

Contact us

We're available Monday to Friday, 9am-5pm GMT

Quick links

Knowledge base
Gocardless Bank Account Data

About GoCardless

Legal
Privacy
Security
Blog

Support

Contact support
Complaints
Contact sales

API Documentation

Developer documents

GoCardless Ltd, Sutton Yard, 65 Goswell Road, London, EC1V 7EN, United Kingdom


GoCardless Ltd (company registration number 07495895) is authorised by the Financial Conduct Authority under the Payment Services Regulations 2017, registration number 597190, for the provision of payment services.





https://docs.google.com/spreadsheets/d/1EZ5n7QDGaRIot5M86dwqd5UFSGEDTeTRzEq3D9uEDkM/edit?gid=976380583#gid=976380583
/hc/theming_assets/01JVYEMDH4NW2KMNM8HG9Y2GXA
Detailed bank coverage
A detailed list of the available institutions and specifications.
custom
https://gocardless.com/stories/bondora/
/hc/theming_assets/01JKWXK6T8QZWQQSYYJAD0X703
Our latest customer story
Learn about how companies are using our technology.
custom
https://developer.gocardless.com/bank-account-data/overview
/hc/theming_assets/01JVYEMQ0208DBSNG2GPZRZ36T
Developer Docs
All the documentation you need to integrate with our API.
Rate Limits, Access expired, Requisition