Wells Fargo puts AI agent losses on you, starting November 24

On Tuesday, Wells Fargo's revised Online Access Agreement takes effect for millions of customers, and the new Section 15 is the reason to read it before you connect anything to your bank account. "Your use of any AI Agent is AT YOUR OWN RISK," the clause says, in the bank's own capitals, per the agreement text.
It is the bluntest version of a shift that ran through the largest US banks in about five weeks. JPMorgan Chase blocks third parties that log in with a customer's credentials. Bank of America told customers not to hand logins to agents. Citigroup added a Section H deeming agent activity the customer's own, and PNC changed its terms on November 18, TechCrunch reported. Charles Schwab's chief executive told Bloomberg the firm blocks unauthorized agents trying to move client money 10 to 20 times a week. Wired surveyed the group this weekend and found five banks reaching the same destination by two roads: Chase bans the login, Wells Fargo permits it and moves the loss.
What Section 15 actually does
The definitions do the work. An "AI Agent" is "any software, application, program, or other technology that takes autonomous, semi-autonomous, or non-autonomous action on behalf of any person or entity" — which reaches budgeting apps, browser extensions and homemade scripts.
Then the authorization clause. If you give an agent your login or otherwise authorize it, any instruction or transaction it initiates is "deemed to have been initiated and authorized directly by you, without further verification," and the bank has "no obligation to investigate the validity or scope of such authority."
Then the responsibility clause: you are "solely responsible" for monitoring the agent and keeping it inside the authority you granted, and — unless law says otherwise — for "unintended actions," for actions from "incomplete, inaccurate, or manipulated inputs," and for the agent exceeding what you allowed. The bank says it does not monitor, screen or review agent activity.
Then the clause a lawyer would circle. You must revoke authorization "properly and timely," retain evidence that you did, and produce it when the bank asks. Until you notify Wells Fargo, you "remain responsible for all the AI Agent's activities." Turning the agent off in its own app is not the same as telling the bank. And by using an agent you "expressly consent" to sharing financial and personal information with it, outside the bank's privacy policies.
A ban would be cleaner. This is a liability transfer written as a disclosure, and its effect is to turn a question about intent — did you mean to buy that? — into a question about authorization — did the software have your password?
Why the banks moved now
Two things happened in October. Banks began detecting third-party agents logging into customer accounts and, in some cases, acting beyond what the customer asked; executives said they struggled to tell which agents had been properly authorized, Decrypt reported during the scare. The agents also kept supplying the bad examples on their own.
The volume is still close to nothing. DoorDash said in October that third-party agent orders numbered in the several hundred against 993 million orders in the quarter, as we noted in DoorDash: several hundred agent orders against 993 million in Q3. Forrester's Sucharita Kodali told Wired that most consumers do not know what an agent is. Banks are writing for a future they expect.
They are also building the alternative while they write it. Wells Fargo's generative-AI assistant has passed a billion customer interactions, Bank of America reworked EricaAssist this year, and Citi built an internal platform for agents. Close the front door to outside agents, open a side door for your own.
The Regulation E problem
The fight is not about whether an agent can be trusted. It is about whether a contract clause can reclassify a transaction consumer protection law already classifies for you.
Regulation E caps a consumer's liability for an unauthorized electronic transfer at $50 if it is reported within two business days and $500 after that, and puts the investigation duty on the bank. The clause's escape hatch is "unless otherwise provided by law or regulation," which every one of these agreements carries. If a transfer your agent initiated counts as authorized, the caps may not apply at all — including when a prompt injection or a leak, rather than your instruction, produced it. Citi's version goes further: the customer stays responsible even if the tool leaks credentials and someone else uses them, per TechCrunch.
No court has tested this. Hunton Andrews Kurth's comparison of the four October moves flags authority and attribution as the open questions, and consumer advocates have the better statutory argument in the obvious case: a stolen password used by a stranger is not something the account holder authorized, whatever a click-through says. The risk is the ambiguous middle — an agent was authorized, went off-script, and the bank's system logs a valid login.
Who wins, who loses
Registered agents win. American Express launched a developer kit in April that verifies agents before they transact and extends purchase protection to purchases made by agents a card member has registered, per Amex's announcement. That is the model the industry is converging on: the agent gets an identity, the credential is a token scoped to a mandate, and the loss lands somewhere defined. It is the part of agentic commerce that AI 101 — What is agentic commerce? argued was genuinely hard — not the shopping, but proving who allowed the spend.
Credential-based agents lose, which means the personal-finance startups whose entire pitch was "we log in as you and do the work." Read-only access through open banking connectors such as Plaid still works at Chase; anything that moves money does not. Platforms have been here before — Resy banned diners whose AI agents grabbed the tables — and the pattern repeats: whoever owns the account relationship decides who may act, then sells access back on its own terms.
The counter-case
The banks are not wrong about the risk. Credential sharing is a major vector for account takeover, and an agent that reads web pages can be prompt-injected. A bank cannot audit software it did not build, and it still answers to regulators for fraud. Writing a clause that says so is defensible; writing one that also disclaims any duty to notice a pattern of agent-driven withdrawals is a different thing.
There is also a limit to what the terms settle. They qualify themselves with "to the extent permitted by law," an admission that the statute outranks the contract. And Wired's experts put the threat in perspective: people are comfortable letting an agent buy toilet paper, less comfortable letting it refinance anything. The disaster here is ten roast chickens, not an emptied retirement account.
What to watch
Whether a state attorney general or the CFPB tests Section 15 against Regulation E. Whether Wells Fargo's reserved right to require agent registration becomes a real registry with Amex-style protection attached. And whether Chase's updated Digital Services Agreement, effective January 1, does what its block does not: give customers a lawful path to a first-party agent while the third-party door stays shut.
Until then, the practical reading is narrow and unpleasant. If you connect an agent to a bank account, assume every action it takes counts as your decision, assume you will need to prove you revoked access, and assume the fraud protections you paid for were written for a world where the only actor with your password was you.
Does your bank let an agent touch your account — and did you read what you agreed to? Write to us via our contact page.







