RBC Blocks Third-Party AI Agents from online banking, the bank confirmed on October 27, 2026. Royal Bank of Canada has drawn a firm line on autonomous software in finance. The country's largest bank said on October 27, 2026, that it will block third-party personal AI agents from direct access to its authenticated digital properties, including online banking. According to RBC's own customer notice, connections that customers have set up to let outside agents reach their accounts will stop working.

The decision makes RBC the first Canadian bank to shut out outside personal agents, according to reporting on the move. It lands in the middle of a wider standoff between banks and the agent economy: institutions that hold customer money are increasingly unwilling to let software they do not control log in on a customer's behalf, while agent developers argue that blocking access holds back a new kind of personal assistance.

What RBC decided and why

RBC framed the move as a security and privacy decision. Personal AI agents need access to online accounts, including financial ones, and may store passwords to get there, the bank said in its notice. As those systems become more autonomous, the bank argued, the stakes rise when something goes wrong, from fraud and consumer harm to risks that could ripple more broadly through the financial system.

An internal memo to staff, reported by Bloomberg, used blunter language. Group head of technology and operations Naim Kazmi and group head of personal banking Erica Nielsen wrote that third-party personal AI agents accessing banking systems can create unacceptable customer risk, including agents acting beyond what customers expect and creating liability exposure for the bank. According to the memo, the bank will begin work on blocking the platforms immediately following a full security review.

RBC spokesperson Jeff Lanthier confirmed the policy and acknowledged the trade-off, saying the bank understands the change may disappoint the small portion of clients who use the tools, while stressing that the safety and security of clients and systems drove the decision. The bank was careful to draw a boundary around what is blocked: customers can still reach their accounts directly through RBC's official website and mobile app, use the bank's own digital tools, and contact customer service for help.

The timing is notable. According to reporting on the decision, the notice came about a week after chief executive Dave McKay told Bloomberg Television that the bank was weighing a block on Meta's Muse, a personal agent that can act across apps and accounts. RBC's public notice did not name specific products, and the bank did not publish a list of which tools count as third-party personal agents.

A pattern spreading across North American banking

RBC Blocks Third-Party AI Agents, and the wider industry is moving the same way. RBC is not acting alone. PYMNTS reported on October 19 that four of the biggest names in United States banking were already turning away AI agents. According to that report, Charles Schwab blocks unauthorized artificial intelligence agents, JPMorganChase chief executive Jamie Dimon said outside AI agents would not get into the bank, Bank of America is limiting agent access to consumer deposits while it writes protocols deciding who is liable for a payment an AI authorizes, and Citigroup does not let third-party agents log into accounts or transact.

A further report on October 22 said major United States banks were detecting and deleting unauthorized third-party agents taking actions inside customer accounts, with some agents apparently attempting actions that users had not requested. The pattern suggests banks are converging on a shared position: an agent that logs in with a customer's credentials looks, from the bank's side, much like an unauthorized third party, whatever the customer intended.

The tension is sharpened by the liability question. If an agent moves money, pays a bill, or shares account data in a way the customer did not expect, it is unclear who bears the loss: the customer who authorized the agent, the agent's developer, or the bank that allowed the login. Bank of America's effort to write liability protocols before reopening access shows how central that unanswered question has become. RBC's memo cited liability exposure directly, signalling that the legal ambiguity is itself a reason to block first and negotiate later.

What it means for the agent economy

For agent developers, the RBC decision is a warning about the limits of credential-based access. The agentic web is advancing quickly in other sectors: this week alone saw new agent products for business analytics and for making websites ready for agent visitors, as covered in recent reporting on autonomous analyst agents and agent-ready websites. But banking is different from browsing a public website, because every action touches real money and regulated data.

The likely path forward is delegated, permissioned access rather than password sharing: banks issuing scoped tokens to approved agents, with clear limits on what each agent can do and clear liability rules when things go wrong. That model already exists in open banking frameworks, but personal agents that act across many services at once do not fit neatly into the per-app consent screens banks built for an earlier era. Until a standard emerges, expect more banks to follow RBC's lead and close the door while they design the rules.

For consumers, the practical effect is narrow for now, since RBC says only a small portion of clients use the tools. The symbolic effect is larger. Canada's largest bank has told the agent industry that trust must be earned through verifiable controls, not assumed from a customer's login. Agents that want a place in personal finance will need to prove they can act within bounds, keep credentials out of their own storage, and leave an audit trail a bank can inspect. Until then, the vault stays closed to outsiders.

Sources: RBC customer notice on third-party AI agents, PYMNTS coverage of the RBC decision, and Bloomberg Law reporting on the internal memo.