More banks say customers using AI agents are on their own — even if they get hacked
- ID
- 47919
- Status
- summarized
- Published
- 19 Nov 2026, 1:32 AM
- Fetched
- 19 Nov 2026, 3:02 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/11/18/more-banks-says-customers-using-ai-agents-are-on-their-own-even-if-they-get-hacked/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 7.5
- Created
- 19 Nov 2026, 3:03 AM
- Tags
- Audience
- developersai_agent_userssaas_startup_founders
What happened
Citibank updated its Online User Agreement this week to state that customers who grant account access to third-party AI agents are responsible for anything those agents do — including losses if the tool leaks credentials or is hacked. JPMorgan and Bank of America, the two largest US banks, announced similar policies last month, PNC (eighth largest) changed its terms the same day, and Citizens emailed customers this week with a comparable warning. A Citi spokesperson framed the change as clarifying risks of sharing banking credentials or authorizing third-party AI tools.
Why it matters
If you are building anything that touches a user's bank account — an agent that pays bills, rebalances, or reads transactions — the liability line has moved: the user now eats the loss, and at Citi that includes breach losses, not just bad trades. That kills the 'just ask users for their banking password' onboarding path and pushes you toward scoped, revocable access plus an explicit consent screen, because your users are being told in writing that they, not the bank, are on the hook for your bug. For founders, the gap is also a product opening: nobody in this list is offering a guarantee, so whoever builds the audit trail or reimbursement layer sits in an unclaimed slot. Note this is US-bank policy only — no Malaysian or SEA bank is named in the text, so treat any local parallel as unconfirmed.
Discussion angle
Citi puts breach liability on the customer, not just transaction liability — so who actually pays when an agent's credentials get stolen? Worth walking through what a defensible agent-finance stack looks like (read-only scopes, per-transaction caps, revocable tokens, signed audit logs) and whether anyone in the local market is building the guarantee layer none of these four banks offer.