# Why Banks Are Blocking Unauthorized AI Agents

URL: https://3ammarketer.com/news/why-banks-are-blocking-unauthorized-ai-agents
Published: 2026-10-26

> Financial institutions are blocking AI agents that rely on credential sharing, transitioning to read-only API access and FAPI standards to mitigate security risks.

Major U.S. financial institutions, including JP Morgan, Bank of America, Citi, and Morgan Stanley, have detected third-party AI agents operating inside customer accounts. The inability to distinguish between human and bot traffic is forcing institutions to block this technology and revise their terms of service. [1][2]

![The logo of JPMorgan Chase, one of the financial institutions affected by unauthorized AI agent access.](https://dygolixznokmekyvajbb.supabase.co/storage/v1/object/public/images/content/930632efb6194d31dcec96a1.jpg)

The primary security challenge for financial institutions is attribution. When a customer provides login credentials to an AI agent, the agent becomes indistinguishable from the customer, leaving the bank unable to tell whether activity originates from a human user or an automated system. [1][3]

## Why screen scraping creates critical vulnerabilities

Screen scraping accesses user data and functionality by impersonating a user through password sharing. The OpenID Foundation characterizes this practice as brittle, inefficient, and insecure because relying on shared passwords creates direct security vulnerabilities. [4]

## Technical solutions: FAPI and DPoP

To secure third-party integrations, the industry is turning to hardened authentication specifications. The Financial-grade API (FAPI) security profile provides a higher level of security than standard OAuth or OpenID Connect for high-risk API use cases. RFC 9449 introduces Demonstrating Proof-of-Possession (DPoP), an application-level mechanism that enables an OAuth client to prove possession of a private key. DPoP stops unauthorized parties from using leaked or stolen access tokens by binding tokens to a public key upon issuance and verifying the client holds the matching private key, preventing replay attacks. [4][5]

![The official OpenID Foundation specification page for the Financial-grade API security profile.](https://dygolixznokmekyvajbb.supabase.co/storage/v1/object/public/images/content/14b01680922f2fc379387d60.png)

## How banks mitigate agent access risks

Financial institutions are shifting from raw credential access to constrained integration models to limit operational exposure. [1][3]


| Access Method | Credential Mechanism | Attribution Capability | Risk Profile |
| --- | --- | --- | --- |
| Screen Scraping | Raw password sharing | Indistinguishable from human user | High security vulnerabilities |
| Read-Only API Access | Constrained API tokens | Separates viewing from transactional execution | Interim risk mitigation |
| FAPI with DPoP | Public-private key binding | Sender-constrained client verification | High security standard |

Limit: The cited sources do not specify the exact technical timelines or binding regulatory dates for when major financial institutions will complete the deprecation of screen scraping in favor of mandatory FAPI compliance.

Most banks have authorized or are currently moving toward read-only access that allows external tools to view financial data without executing transactions. Because full write access via customer credentials presents elevated risks, organizations must abandon credential-sharing automations and transition integration roadmaps to read-only APIs and sender-constrained token standards. [1][3]

## Sources

1. [Unauthorized AI Agents in Banks: Who Is Responsible? - STARTUP HAKK](https://startuphakk.com/unauthorized-ai-agents-in-banks/)
2. [Scoop: Unvetted AI agents are accessing U.S. bank accounts](https://www.axios.com/2026/10/22/ai-agents-banks-unauthorized-accounts-access)
3. [Major US Banks Detect Unauthorized AI Agents Accessing Customer Accounts](https://cyberpress.org/major-us-banks-detect-unauthorized-ai-agents/)
4. [Final: Financial-grade API Security Profile 1.0 - Part 2: Advanced](https://openid.net/specs/openid-financial-api-part-2-1_0.html)
5. [RFC 9449 - OAuth 2.0 Demonstrating Proof of Possession (DPoP)](https://datatracker.ietf.org/doc/html/rfc9449)
