Screen scraping uses the customer's login; open banking never does. Scraping asks a customer for their online banking credentials and reads the account by logging in as them. Open banking replaces that with a consented, bank-authenticated API: the customer approves access at their own bank, no login is shared, and structured data is returned. Open banking is safer, more reliable and the regulated successor to scraping.
How each one works
Screen scraping is exactly what it sounds like: a tool takes the customer's online banking username and password, logs in as the customer, and reads the information off the pages, then stores or parses it. Open banking does none of that. The customer is sent to their own bank to authenticate, approves a specific, scoped request, and the bank returns the agreed data to a regulated provider through a defined API. The difference is not cosmetic: in one, a third party holds the keys to the account; in the other, it never sees them. See how open banking works.
Side by side
| Open banking | Screen scraping | |
|---|---|---|
| Credentials | Never shared | Customer hands over login |
| Authentication | By the bank (SCA) | Tool logs in as the customer |
| Consent | Explicit, scoped, revocable | Broad, and hard to revoke cleanly |
| Data | Structured, consistent fields | Parsed from web pages |
| Reliability | Stable, standardised API | Breaks when the website changes |
| Regulation | FCA-regulated activity | Outside the open banking framework |
Why screen scraping persists
If open banking is better on every axis, why does scraping still exist? Two honest reasons. First, coverage: some accounts, products or data that a firm needs are not yet exposed through open banking APIs, so a scraper fills the gap. Second, inertia: existing integrations keep working, and replacing them takes effort. Neither is a reason to prefer scraping; both shrink as open banking coverage widens and as strong customer authentication makes automated logins harder to sustain.
Migrating away from it
For most data a lender, broker or accountant needs, open banking now covers it, and the migration is mainly about switching the data source behind your existing process. The practical steps are to map which of your checks still rely on scraped data, confirm open banking coverage for the banks your customers use, and move the connection journey to a consented open banking flow. The customer experience improves at the same time, because they stop being asked for their password. See choosing a provider.
From the data consumer's side
If you still rely on scraping, the risk sits with you: you are asking customers to share credentials, your integration is fragile, and you are outside the regulated framework that open banking provides. Moving to open banking reduces your risk and your support burden, and it is a better story to tell customers and auditors. The one thing to check before switching is coverage for your specific customer base, which is a provider question.
How Credit Canary does it
Credit Canary uses regulated open banking access, not scraping: consented, bank-authenticated connections returning structured data, enriched into income, affordability and payments. You get the data you need without ever asking a customer for their banking login.
Common questions
What is the difference between open banking and screen scraping?
Screen scraping asks for the customer's bank login and reads their account by logging in as them. Open banking never takes the login: the customer authenticates with their own bank and a regulated API returns only the agreed data. Open banking is consented, authenticated and far safer.
Is screen scraping legal in the UK?
Sharing banking credentials is discouraged and sits awkwardly with banks' terms and strong customer authentication rules. Open banking was created precisely to provide a regulated, consented alternative, which is why the market is moving away from scraping.
Why do some firms still use screen scraping?
Usually for coverage of accounts or products not yet available through open banking APIs, or legacy integrations. As open banking coverage widens, the reasons to keep scraping shrink.
Is open banking more reliable than screen scraping?
Yes. Scraping breaks whenever a bank changes its website or login, and strong customer authentication frustrates automated logins. A standardised API is more stable and returns structured, consistent data.
Related pages
Primary sources
- Delegated Regulation (EU) 2018/389 (SCA RTS) (checked 14 Oct 2026).
- openbanking.org.uk, What is open banking (checked 14 Oct 2026).
Credit Canary provides open banking through fumopay limited, an FCA-authorised account information and payment initiation service provider (FRN 925689), of which Credit Canary is an agent. Underlying bank connectivity is also provided by fumopay limited. This page is an evergreen reference and is reviewed and dated; it is not regulatory, legal or financial advice.