Back to blog

Why do big banks keep blocking your AI agent from your money?

Thắng Đoàn
Thắng Đoàn

You connected an AI agent to your bank and it can read your balance but cannot pay a bill. The biggest US banks are doing this on purpose, and the reason is liability, not missing APIs.

Reading is easy, moving money is not

PYMNTS reports that JPMorganChase, Citigroup, Bank of America and Charles Schwab all said in one week that outside AI agents cannot move customer money. Schwab alone says it blocks Meta's Muse dozens of times a week. Yet the same banks still let authorized connectors read balances. So the wall is selective: data can flow out, payments cannot flow through an agent you chose yourself.

  • Bank of America is writing liability rules with agent developers
  • JPMorgan builds its own Smart Cash sweep instead

The real blocker is liability

If an agent moves money wrongly, who eats the loss: the bank, the customer, or the agent's developer? Nobody has answered that yet. PYMNTS notes Bank of America is negotiating liability rules with agent developers. That tells you the gap is contractual, not technical. Banks that build their own in-house agents keep the liability inside the bank.

A read-only bridge is emerging

Danske Bank is piloting an MCP Server, a standard way for AI tools to connect to data sources. Per The Paypers, corporate customers connect assistants like Claude or ChatGPT to Danske Bank's Premium APIs and query their own account balance, under their own credentials and control. Q2 Holdings is also enabling MCP endpoints for banks. Q2 insists banks keep control of permissions, security, branding and compliance.

  • Q2 frames personal AI agents as banking's next customer channel

New doors invite new attacks

Every new agent channel is also a new fraud channel. Q2 warns that attackers can use AI for deepfakes and social engineering. Its account-takeover product now watches for threats originating through AI-agent interfaces. So banks are not being stubborn; they are pricing in risk before opening the payment gate.

What this does not solve

Read-only MCP access does not settle who pays when an authorized agent makes an unauthorized mistake. It also does not stop banks from preferring their own captive agents over yours. And none of the sources show a live payments path for third-party agents at any major bank. The open question of liability remains the rate limiter.

If your product depends on agents moving money, does your roadmap assume a bank partnership, and who carries the liability?
Could you ship value today with read-only agent access and keep payments human-approved?

List every place your product moves money on a customer's behalf and write down who is contractually liable if the action is wrong.

Sources

Yahoo Finance: Q2 Eyes Personal AI Agents as Banking's Next Channel

The Paypers: Danske Bank pilots MCP Server for corporate AI banking access

PYMNTS: Big Banks Won't Let Outside AI Agents Move Money

Share:

Recommended for you

Enjoyed this article?

Subscribe for new articles. No spam. Unsubscribe anytime.

By subscribing you agree to receive the newsletter. No spam, and you can unsubscribe anytime.