Several of the largest US banks are restricting third-party AI agents after finding them inside customer accounts, and the AI agents bank login problem is coming to Canada, Axios reported on October 22. In most cases the customer had handed the agent a username and password. Morgan Stanley has begun blocking third-party agents, and JPMorgan, Bank of America and Citi are restricting them, according to people Axios spoke to. A Chase spokesperson said customers should not give their usernames and passwords to anyone.
Canadian banks have not announced anything comparable. They do not need to. For many personal accounts, the agreement a customer already accepted settles who pays if an AI agent with a bank login gets it wrong, and the answer is the customer. Banks aren’t the only ones changing rules, and ChatGPT Go ads show who pays for cheap plans.
What does a Canadian bank agreement actually say?
Take RBC’s Electronic Access Agreement, which governs its personal online and mobile banking. It says customers “must not disclose” their sign-in credentials “to anyone,” with one exception: you may share your password with an Aggregator or an Account Verifier. The definition of Aggregator then closes the door on agents.
It “does not include a Third Party that allows you to do transactions through their service or that does transactions on your behalf.”
An AI assistant that pays a bill, moves money or files a dispute is doing transactions on your behalf. Under this wording, it is not an aggregator, and sharing your password with it falls outside the exception.
The cost shows up in the security guarantee. RBC reimburses losses from unauthorized digital banking transactions, but not if “you share any of your Sign-In Credentials,” and not if you “consent to, contribute to, provide instructions for, or authorize a transaction in any way.” The agreement also says RBC may accept any instruction “given by you or purported to be given by you” under your credentials. An agent’s mistake, made with your login, reads as your instruction.
Is there a sanctioned route for AI agents yet?
There is no sanctioned route in force today. The Consumer-Driven Banking Act received Royal Assent on March 26, 2026, and sets up a framework in which the Bank of Canada accredits the firms that can receive customer financial data at a consumer’s request. Its accreditation provisions are marked as not in force.
The proposed regulations were pre-published in the Canada Gazette on June 27, 2026, and Finance Canada says they will come into force in stages, starting with accreditation.
The framework, as Finance Canada describes it, is about sharing financial data with accredited providers. It is the likely home for an agent that reads balances and transactions. Whether and when it will cover an agent that moves money has not been set out.
Fine Print
- Instruments: Your bank’s electronic access agreement (RBC’s personal agreement is the example here); the Consumer-Driven Banking Act, S.C. 2026, c. 3, s. 224.
- Status: Bank agreements apply now. The Act has Royal Assent, but accreditation is not in force; regulations were proposed on June 27, 2026.
- Who enforces: The bank, through its agreement and reimbursement decisions. The Bank of Canada will supervise the consumer-driven banking framework.
- Who it applies to: Personal online banking customers under the agreement quoted. Business accounts are on separate terms, which you should read for the same clauses.
- What changes: Nothing in the agreement is new. What is new is that staff and owners are giving AI agents bank logins to do real transactions.
- Still undecided: When accreditation starts, and whether the framework will ever cover agents that initiate payments.
The other reading
A fair objection is that these clauses were written for fraudsters and careless password habits, not for a customer’s own assistant, and that a bank would struggle to refuse a claim when the customer clearly did not intend the loss. That may prove true case by case. We would not plan a company’s cash management around it. The agreement’s wording is plain, and the US banks in the Axios report said they could not reliably tell a customer’s agent from a rogue one. A bank that cannot tell the difference will lean on the contract.
What to put in policy this month
For a Canadian business, three rules cover most of it. No AI agent gets a bank login with authority to pay, transfer or change payees. Agents that need financial data get it through exports, statements or the bank’s own approved connections, not a shared password. And anyone who already gave an agent a bank password changes it today, as RBC’s agreement requires when a third-party service ends. Our personal AI agent policy guide covers who should approve agent access in the first place. The Bank of Canada is watching AI from a different angle, and its view on when AI pays off sets expectations for small firms.
More policy analysis is in AI Policy in Canada. This is general information, not legal advice.
Before the next statement
Pull your company’s and your own bank agreements before the next statement date and search them for “aggregator,” “credentials” and “third party.” If an agent’s access does not fit the exceptions you find, end it.
FAQ
Can I give an AI agent my bank login in Canada?
Most bank agreements forbid sharing sign-in credentials. RBC’s personal agreement allows sharing only with an aggregator or account verifier, and its definition excludes services that do transactions on your behalf.
Who pays if an AI agent with a bank login makes a mistake?
Under RBC’s personal agreement, the security guarantee does not cover losses if you shared your credentials or authorized the transaction in any way, so the customer is likely to bear it.
Does Canada’s consumer-driven banking framework cover AI agents?
It does not yet. The Consumer-Driven Banking Act has Royal Assent, but accreditation is not in force, and the framework as described covers sharing data with accredited providers rather than moving money.
