API access uses a dedicated interface that the bank provides for authorised third parties, while screen scraping imitates customer access to retrieve data from the online channel. Under the RTS, screen scraping is no longer allowed where a dedicated API exists, and third parties using the fallback approach must digitally sign messages to identify themselves. The API model is more controlled and easier to govern.
How API access differs from screen scraping under PSD2
Under PSD2 payment account rules, the key difference is not just technical style, but how access is governed. API access uses a dedicated, bank-provided interface for an authorised third party. Screen scraping imitates customer logins to pull data from the online channel, which makes control, consent, and auditability much weaker.
API access is designed for structured permissions, stable interfaces, and clearer accountability. That matters because payment account data access under PSD2 is meant to be mediated, not improvised. The bank can expose defined endpoints, set policy around authentication and access, and manage third-party use through a dedicated channel rather than through customer credentials.
Screen scraping, by contrast, inherits the risks of the customer-facing web channel. It depends on a third party behaving like a user in a live online session, which means changes to page design, anti-bot controls, and authentication flows can break access without warning. It also blurs the line between customer use and delegated access, which is why the dedicated interface model is preferred.
Why the RTS treats fallback scraping as a controlled exception
The regulatory logic is to push third parties toward the dedicated interface wherever it exists, because that model is easier to monitor, govern, and attribute. The fallback approach is narrower and more constrained, and the direct answer’s point about digital signing is important: third parties using the fallback path must sign messages so they can be identified rather than remaining indistinguishable from ordinary customer traffic.
That identification requirement is a practical control, not a formality. It helps the bank distinguish legitimate third-party activity from ordinary consumer browsing, supports traceability, and reduces ambiguity in incident handling. In practice, the API model gives the bank a cleaner control surface, while scraping makes assurance depend on a fragile imitation of user behaviour.
This is why the subject is often discussed alongside open banking interface governance. The rules are not simply about whether data can be retrieved, but about whether access is mediated through an accountable technical path. CFPB Section 1033 Open Banking Rule Guide is useful background for the same interface-versus-scraping distinction in US open banking.
The same control logic appears in broader financial-services security practice, where regulated access paths need stronger identity and access governance than consumer-style session reuse. PSD2/PSD3 Strong Customer Authentication Guide and Financial Services Identity Security Guide both cover the access-control implications that sit behind PSD2-style third-party access.
What this means for banks and third parties in practice
For banks, the operational difference is that API access can be versioned, monitored, tested, and governed as a productised control surface. Screen scraping forces the institution to tolerate uncontrolled interaction with its consumer channel, which is harder to secure and harder to support. For third parties, the API path usually means clearer integration stability and less dependence on fragile login automation.
For practitioners, the real test is whether the access method can be reviewed as a defined relationship rather than as a borrowed customer session. That is why PSD2 implementation teams should treat API onboarding, third-party identification, and exception handling as part of the same control model, not as separate technical tasks. Where a dedicated interface exists, scraping should be treated as a legacy fallback, not an equal option.
Source material on API governance and third-party access helps here. OWASP API Security Top 10 gives a useful security lens for API exposure, while RFC 6749: The OAuth 2.0 Authorization Framework explains the delegated-access pattern that underpins controlled machine access.
Risk and Threat Considerations
Screen scraping concentrates several risks at once: credential exposure, session abuse, fragile automation, and weak traceability. If a third party is operating through customer-style login flows, the bank and the customer both inherit the security consequences of that session model, including the possibility that access is blocked, misused, or difficult to investigate.
Failure mechanism: The third party depends on customer-session behaviour rather than a purpose-built authorisation path, so control changes, anti-fraud measures, or credential compromise can break access or widen exposure without clean governance boundaries.
Impact: Access becomes harder to attribute and harder to revoke cleanly, and the bank may face operational instability, weaker audit evidence, and greater abuse potential if customer credentials or sessions are reused beyond the intended scope.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 addresses the attack surface, NIST SP 800-53 Rev 5 sets the technical controls, and ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP API Security Top 10 | API8 — Security Misconfiguration | API and scraping differences turn on controlled interface exposure and governed access paths. |
| Recommendation — Harden the dedicated API and restrict exposed functions to the minimum needed. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | PSD2 access hinges on controlled authentication material and third-party sign-in handling. |
| AC-2 — Account Management | Third-party access under PSD2 needs governed account lifecycle and revocation. | |
| Recommendation — Manage third-party authenticators and rotate them when access is revoked or changed. Assign, review, and revoke third-party access accounts on a defined lifecycle. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | The question is fundamentally about controlled access versus improvised access. |
| Recommendation — Define and enforce access rules for payment data interfaces and fallback paths. | ||
Practitioner Guidance
What to verify: Confirm whether the access path is a dedicated interface or a customer-session workaround, then check that the third party is identifiable and the integration is governed as an authorised relationship, not as an ad hoc login pattern.
Decision rule: If a dedicated API exists, treat screen scraping as an exception path that should be retired or tightly constrained; if fallback access is still used, require strong third-party identification, clear monitoring, and a documented business justification.
Practitioner takeaway: The operational goal is not simply to move data from one channel to another, but to ensure the access method is governable, attributable, and resilient enough to stand up in audit and incident review.
Related resources from NHI Mgmt Group
- What is the difference between screen scraping and API-based banking access?
- What breaks when API access under PSD2 is not tightly scoped?
- What is the difference between Section 1033 API access and screen scraping?
- How should banks adapt payment authentication and authorization when PSD2 opens account access to third parties?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org