AI in the enterpriseAnalysis
What Bank of America, JPMorgan, Wells Fargo, Citi and Schwab said and signed about AI agents in customer accounts, 13 October to 24 November 2026, and what replaces the password.
Consumer AI assistants can now open a banking app, read the balance and pay a bill, and in October the largest US banks said so in public. Meta reported that its Muse assistant reached ten million users on 21 October.2 By 27 October Bank of America had emailed its customers asking them not to share their logins with one.1 The question for anyone who uses one of these agents, or employs people who do, is simple and the answers are not yet tidy: when an agent moves money with your credentials and gets it wrong, who pays, and what should replace the password while the industry argues about it?
There are two routes in. In screen-driving, the assistant runs a scripted browser, signs in with the password and one-time code the customer gave it, and clicks through the app as a person would. In the aggregator route, the customer authorises a connector such as Plaid and the agent reads balances through it. JPMorgan told CNBC on 13 October that the second route stays open, read-only, and the first is closed: outside agents cannot log in with a customer’s credentials, send money or pay a bill.6
The first route is the problem, because the bank cannot see it. “They also mimic the behavior of actual human users, so it’s really hard to detect,” Mickey Boodaei, chairman of Transmit Security, told American Banker. Some banks block traffic from the addresses of AI providers such as Anthropic or Meta; Transmit’s chief executive, Matt Thompson, said agents get through proxies.3 Andre Durand, chief executive of Ping Identity, put the bank’s two unanswered questions plainly to USA TODAY: how to detect “that it is an agent and not a human asking”, and then “how do we know that the agent is acting on the authority of the human?”2
To the bank, a screen-driving agent is the customer: same password, same code, same clicks
How a consumer AI agent reaches a bank account by credential sharing, as described by banks and fraud vendors, October 2026
The customer hands over the keys
Username, password, and often the one-time code or the inbox it arrives in, given to a consumer assistant.
The agent drives the app
A scripted browser signs in from the provider’s cloud or through a proxy, and reads, clicks and types as a person would.
The bank sees a valid session
Right password, right code, human-like behaviour. Address blocks catch some agents; proxies defeat them.
The contract says it was you
Instructions that arrive with your login credentials are treated as genuine and authorised by you.
Source: American Banker (27 Oct 2026); USA TODAY (23 Oct 2026); JPMorgan Chase Digital Services Agreement (Oct 2026) · as of 29 October 2026
One incident has been described in public, and only anonymously. A source who asked not to be named told American Banker that at an unnamed large bank an agent “conducted a password reset on an account” and “moved $100,000 out of the account”, after which the bank’s fraud team recommended blocking all external agents.3 We cannot verify it, and no bank has published a count of agent sessions or losses.
The statements came in a cluster. Jamie Dimon told analysts on JPMorgan’s third-quarter call on 13 October, “we’re not going to allow just any outside agent to come in inside the company.”3 Charles Schwab’s chief executive, Rick Wurster, told Bloomberg on 16 October that Schwab is blocking “tens and twenties” of attempts by major AI agents to access and manipulate client funds. Citi told USA TODAY: “We do not permit third-party AI agents or assistants to log into a customer’s account or transact directly within our digital banking platforms,” while allowing “limited, read-only access” through Citi-approved open-banking providers.2 Wells Fargo said it has “taken steps to block unauthorized agents”; American Banker counts Morgan Stanley among the banks blocking, though it did not comment.3
“When you give the agent your credentials, it is you authorizing the payment.”
His next words matter as much: “put a human being in the loop,” so that “before you pay, you authorize it.”2 That is a request for a design change, not only a disclaimer.
In six weeks the US banks went from warning about agents to writing them into their contracts
Public statements and agreement changes on consumer AI agents by US banks and Mastercard, 13 October to 24 November 2026
| Date | Event | Detail |
|---|---|---|
| 13 Oct 2026 | JPMorgan shuts the door | Dimon on the Q3 call; a spokeswoman tells CNBC agents may read balances via Plaid but not move money |
| 15 Oct 2026 | Moynihan to Bloomberg | “it is you authorizing the payment” |
| 16 Oct 2026 | Schwab: “tens and twenties” | Wurster on agent attempts blocked |
| 21 Oct 2026 | Meta's Muse at 10 million users | Meta's own figure, via USA TODAY |
| 23 Oct 2026 | Citi: no agent log-ins | access limited to reading data, through approved open-banking providers |
| 27 Oct 2026 | BofA email; Chase ban in force | BofA email reported:“you're responsible”; Chase bars External AI from using login credentials |
| 29 Oct 2026 | Mastercard: use tokens | Miebach on the Q3 call |
| 24 Nov 2026 | Wells Fargo terms take effect | agent transactions deemed authorised by you |
Source: American Banker; USA TODAY; PYMNTS (CNBC report); TechCrunch; JPMorgan Chase and Wells Fargo agreement texts · as of 29 October 2026 · dates are when each statement was made or reported; the 24 November date is an agreement's stated effective date
Bank of America’s email, titled “Protecting your finances in the AI World”, asked customers never to share their login details, “including an AI-enabled tool or agent that offers to act on your behalf.”1 JPMorgan Chase’s Digital Services Agreement, updated in October, says that from 27 October third parties “including External AI, automated tools, or data aggregators” are prohibited from using a customer’s login credentials, and that anyone who has shared them “must change those credentials”.4
Wells Fargo goes furthest. Section 15(e) says use of an agent is “AT YOUR OWN RISK” and makes the customer responsible for “unintended actions performed by the AI Agent, actions resulting from incomplete, inaccurate, or manipulated inputs”. That last phrase covers prompt injection, a hidden instruction on a web page that redirects an agent. Until the customer notifies the bank of a revocation, the customer “remain[s] responsible for all the AI Agent’s activities”.5
The legal spine is older than AI. Under the US Regulation E, a transfer is not “unauthorized” if it was initiated by a person “who was furnished the access device to the consumer’s account by the consumer”, until the consumer tells the bank that person is no longer authorised.11 Moynihan’s sentence is that rule in plain English. Whether a court reads an AI agent as such a person has not, as far as we found, been tested, and every clause above is hedged with “subject to applicable law”. Jeff McMillan, former head of firmwide AI at Morgan Stanley: “there are no agreed standards yet for how a bank verifies an agent.”3
Most Americans do not want an agent moving their money, and one in five say an agent has already asked for their login
Share of US adults, Morning Consult survey for the American Bankers Association (more than 4,000 adults), released 27 October 2026
77%
Concerned about giving an AI tool or agent permission to move money
27%
Likely to let an agent manage cash balances on its own
61% unlikely
19%
Say an AI agent has already asked them for login credentials or card numbers
Source: ABA Banking Journal (27 Oct 2026); sample size from American Banker (27 Oct 2026) · as of 27 October 2026 · field dates and margin of error were not published in the pages we could read
One adult in five already reports being asked for the very credentials that, once handed over, move the loss onto them.7
The banks are not banning agents; they are banning agents that borrow the customer’s identity. Chase’s agreement permits third-party tools “including External AI, to access customer account data through approved application programming interfaces” with the customer’s authorisation.4 This has happened before: about a decade ago Plaid and Mint signed in with customers’ passwords to scrape data, some banks blocked them, and the fight ended in API data-sharing agreements.3
For payments, the card networks want tokens. Mastercard’s Michael Miebach said on 29 October it is “in everybody’s best interest to use Agent Pay and equivalents”, and that one-time virtual card numbers used as a front for an agent’s purchase “fundamentally break the transaction”; he would accept them only as a stopgap. Visa Intelligent Commerce and American Express’s Intent Intelligence take the same token-based route.8 For identity, Meta and Sierra have published Poppy, the Personal Agent Protocol: an agent identifies itself, and the customer decides whether it can view an account, make changes, or both. Bank of America and Wells Fargo are design partners, and BBVA joined on 13 October. Poppy does not yet cover payments.910
The fix is not a ban on agents; it is an agent with its own credential, its own limits and its own off switch
Credential sharing against delegated, scoped access for consumer AI agents, as set out by US banks and card networks, October 2026
Credential sharing (today)
Delegated, scoped access (what is being built)
Source: JPMorgan Chase Digital Services Agreement; Citi via USA TODAY; American Banker (29 Oct 2026); PYMNTS on Poppy (12 Oct 2026) · as of 29 October 2026
None of this is limited to consumers. Wells Fargo’s agreement governs Wells Fargo Business Online as well as personal banking.5 Chase’s indemnity clause makes the customer answer for third-party claims arising from the acts of “any employee or agent, such as AI agents or agentic AI”, including “actions that were not within the scope of your agent’s authority”, and for a business it extends to “your employees, consultants, and agents, including AI agents and agentic AI.”4 An employee who pastes the treasury login, the payroll portal password or a SaaS admin credential into a browser agent has made the company the guarantor of whatever the agent does. The attacker’s side of the same habit, agents that find a credential and reuse it, is in our piece on CERT-In’s two Critical advisories.
A company's agent policy fits on one page: no shared logins, scoped grants, human approval for money
Five controls for AI agents that touch corporate banking and SaaS logins, TechBag's sequence, October 2026
Step 1 of 5
1. No shared logins, written down
No employee gives a bank, payroll, finance or SaaS admin credential to an AI agent or agent browser extension. Put it in the acceptable-use policy; the bank terms already put the loss on the company.
Source: TechBag analysis of the JPMorgan Chase and Wells Fargo agreement terms; Ping Identity via USA TODAY · as of 29 October 2026
Sources
Related on TechBag: the IAM, SSO & MFA guide compares passkey support across 30 products; the privileged access guide covers the tools that give agents their own scoped credentials; the BFSI obligations register tracks the RBI duties cited here.
Disclosure. TechBag is a software reseller: it earns a margin when a reader buys through it, including from vendors named here. The analysis is TechBag’s own; no vendor paid for or saw this piece before publication. Facts are labelled reported, TechBag count or our view.