bysepa
Guide

Open Banking Timeline: Key Milestones, Regulations, and Global Growth

Learn the history of open banking, from 1980s experiments to PSD2 APIs in 2018. See the open banking timeline and key regulations.

By Editorial TeamJuly 04, 20264 min read
Open Banking Timeline: Key Milestones, Regulations, and Global Growth

When did open banking start? A quick timeline answer

Open banking started long before most apps and APIs. Many trace the history of open banking to the 1980s. Then came standards, rules, and safer access.

For the mainstream era, regulators matter most. HBCI arrived in 1998 and set a secure interface path. PSD1 launched in 2007 to lift competition and protect users.

PSD2 is the big switch for today’s model. It was set in place in 2018. Banks had to share access with third parties via APIs.

  • 1980s: early trials of shared banking access
  • 1998: HBCI and FinTS help set secure messaging
  • 2007: PSD1 supports competition and user safety
  • 2018: PSD2 pushes API access with strong checks
Terminal-era workspace representing early banking interface experiments.
Origins in early banking tech

Origins of open banking: the 1980s experiments

Early work treated banking access like a shared tool. It explored ways to let others use bank features. It did not mean full public access. It meant tight, testable paths.

One line of history points to the German Federal Post Office in the 1980s. Citibank is also linked to early ideas. These teams looked at how systems could talk to each other.

That matters for the open banking timeline because the mindset came first. People wanted new services without breaking bank safety. They also needed clear rules for what could be shared.

So, when did open banking start? It depends on your definition. If you mean “interface ideas,” the 1980s fit. If you mean “API programs,” later rules fit better.

Circuit components and connectors symbolizing standards and interoperability work.
How interfaces were engineered

Key developments in the 1980s: building the idea into bank systems

The 1980s had limits that shaped early designs. Most systems used phone lines or terminals. Data moved in slow, planned batches. That slowed “open” thinking.

Engineers still built clear request and reply flows. They used set formats and set checks. That is the core habit behind modern API integration in banking.

Teams also focused on narrow access. They avoided handing over the whole bank stack. Instead, they tested one function at a time. That reduced risk and helped learning.

  • Access stayed narrow and testable
  • Interfaces needed shared formats
  • Security checks came early
  • New providers could build on set rules

Regulatory milestones: PSD1 and PSD2

Europe pushed open banking from idea to law. PSD1 started in 2007. It aimed to grow fair competition in payments. It also aimed to protect customers.

PSD1 did not yet force today’s API model. But it nudged banks toward clearer roles. It also pushed the market toward more set rules.

PSD2 is what many people remember. It was in force in 2018. It told banks to let third parties access data and payments via APIs.

PSD2 also required strong sign-in checks. It aimed to keep access safe while enabling new apps. That change is why open banking regulations now shape product work.

If you follow the open banking timeline, map it to these steps. PSD1 set the direction. PSD2 set the access method. After that, the market built services.

Professional workspace representing banking regulations and policy milestones.
Regulations that shifted access

Technological advancements that made open banking work

Rules need tech to become real. One key early step was HBCI. It stands for Home Banking Computer Interface. It was set up in 1998.

HBCI helped define secure messaging for banking tasks. It worked with FinTS. FinTS is the related format used for message flow. Together they pushed safer, set interfaces.

Another early signal came from SOFORT in 2004. SOFORT focused on security plus a fast user flow. That showed “safe” can still feel easy. It helped payment adoption.

Later, banks moved toward APIs. But integration meant more than a new endpoint. Teams had to manage user consent, sign-in state, and clear scopes.

Some early services used screen scraping methods in banking. That means pulling data from a bank view. It can break when screens change. API access became a better fit over time.

Milestone Year Why it mattered
HBCI set up 1998 Helped standardize secure message flows
SOFORT 2004 Showed safe payments can be simple
PSD1 2007 Supported competition and user protection
PSD2 2018 Required API access with key security steps

Global expansion: from Europe to other banking markets

Open banking spread after Europe proved a workable model. Many other places started similar efforts. They copied key ideas like consent and safe access.

Adoption grew for two main reasons. Banks wanted new ways to compete. FinTech innovations also built useful apps for users. Those wins made the idea stick.

People also ask about when open banking is coming to canada. Canada has discussed open banking plans in public talk. Exact timing depends on local policy choices. So watch official updates from Canada’s rule makers.

Growth targets also look big. Many forecasts point to a multi-billion dollar market ahead. The number varies by report, but the trend is steady. More links mean more services and more volume.

  1. Rules define data scope and consent rules
  2. Banks build safe APIs and test sandboxes
  3. Third parties build apps for account and pay use
  4. More users join, and costs fall

Open banking is moving from “possible” to “reliable.” Banks must keep APIs stable while they change systems. Third parties must handle downtime and odd data. That work is not optional.

Consent will get more focus. Users want clear control over what is shared. They also want to know how long access lasts. Regulators also keep attention on sign-in safety.

Security remains a daily job. One weak step can harm trust fast. Strong logs, tight checks, and test plans help. Teams also need clear ways to react to issues.

Finally, open banking regulations will keep evolving. New data types may come into scope. New flows may require new steps. The open banking timeline will keep adding chapters.

  • API uptime and version changes will matter
  • Consent UX can drive adoption
  • Security must match real user paths
  • Rules may widen to new data and pay use

FAQ

When did open banking start?
Open banking can be traced to experiments in the 1980s. Mainstream use grew later, especially after PSD2 in 2018.
What is the open banking timeline in Europe?
It starts with early trials and HBCI in 1998. PSD1 came in 2007, and PSD2 was set in 2018.
How did PSD1 influence open banking regulations?
PSD1 aimed to raise competition and protect customers in payments. It set the stage for later, clearer access rules.
What changed with PSD2 in 2018?
PSD2 required banks to provide access to third parties via APIs. It also focused on strong sign-in checks and security.
Why do people mention screen scraping in open banking history?
Some early services used screen scraping methods in banking when APIs were not ready. API access later became more stable and easier to audit.
When is open banking coming to Canada?
Canada has discussed open banking plans, but dates depend on local policy steps. Track official updates from Canada’s rule makers.
#open banking timeline milestones#open banking regulations in europe#when did open banking start#psd2 api access rules#hbcI finTS standards#global open banking growth
ShareXFacebookLinkedInWhatsAppTelegram