Say you are building an agent in Toronto that books freight. It needs a weather feed, a customs-tariff lookup and a model call, and each provider wants paying. Sending a card number would need a human, an account and a checkout page, per provider, per task. What has happened in the past year is that the providers started answering with a price instead: HTTP status 402, Payment Required, with a wallet address attached. The agent pays a fraction of a cent in a stablecoin and retries. Nobody typed anything.
That loop now runs tens of millions of times a month. The x402 standard, which Coinbase built and handed to the Linux Foundation on July 14, 2026, counted 75.41 million transactions in the 30 days to September 10, 2026 (x402.org). The XRP Ledger’s agent hub shows 4.94 million agent payments all time (XRPL AI Hub). Tether has shipped a toolkit that hands an AI agent a self-custodial wallet (Tether WDK docs).
For a Canadian builder the technical part is the easy part. The harder questions are what the volume numbers actually show, who is liable when an agent overspends, and which of FINTRAC’s and the CSA’s rules apply to a company whose customers are pieces of software. This guide takes them in that order. It is a sourced explainer, not legal advice.
The 402 loop, in one paragraph
HTTP has had a 402 status code since the 1990s, reserved for a payment mechanism that never arrived. x402 fills it in. A server marks an endpoint as paid; a request arriving without payment gets a 402 response carrying the price, the accepted networks and the address to pay. The client, human or agent, pays and sends the request again with proof. A “facilitator” verifies and settles the payment so the seller does not have to run blockchain infrastructure. x402.org describes the standard as free of protocol fees and not tied to any one network; Coinbase’s developer platform says its facilitator has processed more than 100 million x402 payments across the Base and Solana networks (Coinbase Developer Platform, x402 overview). Under the x402 Foundation, launched July 14, 2026 with founding members from finance, cloud infrastructure and payments, the protocol sits under vendor-neutral governance rather than one company’s (Linux Foundation announcement).
The reason this suits agents is that it removes every step that assumes a person: no account, no form, no personal information, no wait. It also suits sellers who want to charge tiny amounts for single calls, which cards cannot do economically.
What the XRP Ledger numbers really show
Ripple launched its XRPL AI Starter Kit on June 9, 2026, with x402-style payments in XRP and its RLUSD stablecoin, pitching the ledger’s fast settlement and predictable fees for machine-to-machine commerce (Ripple Insights, June 9, 2026).
AI agents are no longer a future state. They're already paying for compute, settling invoices, navigating policy constraints, and completing transactions without a human in the loop. Ripple, "Building the future of agentic payments", June 9, 2026
Three months on, the community’s own index gives the numbers. As of September 10, 2026, the XRPL AI Hub listed 4,943,154 transactions all time, 154 registered merchants and a seven-day average of 192,059 payments a day. Settled value all time: 5,932.51 XRP and 4,450.44 RLUSD (XRPL AI Hub). The live feed on the same page shows what a typical payment looks like: 0.0005 to 0.0014 RLUSD, a few hundredths of a cent, paid to an inference router that resells model calls.
Read those two facts together. Millions of payments, a few thousand dollars of value. That is not a failure; it is what per-call pricing at machine speed looks like, and it is the point of the design. But it means the market being built is one of counts, not volumes, and anyone quoting the transaction figure as evidence of money flowing into a token is quoting the wrong number. The ledger’s transaction cost, a fraction of an XRP destroyed per transaction, is set out in the XRPL documentation and is what makes sub-cent payments possible at all (XRPL docs, transaction cost).
Who holds the keys when the agent spends
Tether’s answer is the Wallet Development Kit. Its MCP Toolkit, in beta at version 1.0.0-beta.1 as of September 10, 2026, runs a Model Context Protocol server that exposes wallet operations, balances, sends, swaps, bridges, lending and fiat on- and off-ramps, as 35 structured tools an AI client can call, across 13 chains including Ethereum, Bitcoin, Solana and Tron. Two design choices matter. Seed phrases stay on the user’s machine, and every write operation uses an MCP elicitation, meaning the agent must get explicit user approval before a transaction is broadcast (Tether WDK docs, MCP Toolkit).
That is the safe path. CryptoSlate’s reading of Tether’s documentation for the companion command-line wallet, published in September 2026, describes a different one: the owner unlocks the wallet for a timed session, a background process holds the unlocked keys, and on macOS and Linux any other process running as the same operating-system user can request transactions from that session without fresh approval of each payment (CryptoSlate). The same report quotes Tether chief executive Paolo Ardoino’s statement when WDK was announced on November 11, 2024, describing programmable monetary systems connecting people, machines and AI agents while preserving financial control.
The lesson generalises beyond Tether. Custody (who holds the keys) and authority (which recipients, amounts and operations an automated system may sign) are separate design decisions, and toolkits increasingly leave the second one to the developer. An agent with a budget of C$20 a day and a whitelist of recipients is a product. An agent with an unlocked wallet and a prompt is a liability with a wallet address.
The Canadian rules a builder trips over
Canada has no statute on AI agents. What it has is three sets of rules written for other reasons that reach the agent economy anyway.
FINTRAC and the money services business rules. The Proceeds of Crime (Money Laundering) and Terrorist Financing Act makes a business that deals in virtual currency, meaning exchange services between fiat and crypto or between cryptos, or transfer services on a client’s behalf, a money services business that must register with FINTRAC and meet reporting, record-keeping and know-your-client obligations. FINTRAC’s own guidance adds that persons providing payment services for goods and services are engaged in remitting or transmitting funds, or dealing in virtual currency (FINTRAC, money services businesses). The line that matters for a builder is whether you move value for others. A company whose agents pay for their own API calls is a customer. A company that runs a facilitator, settling x402 payments between third-party buyers and sellers, looks a lot like a business dealing in virtual currency, and needs a written opinion before it takes its first Canadian client.
The CSA and stablecoins. Every stablecoin in this story, RLUSD, USDT and the USDC that most x402 sellers accept, is a value-referenced crypto asset in the CSA’s vocabulary. Staff Notice 21-333, published October 5, 2023, sets the terms on which a registered Canadian trading platform may let clients trade one: undertakings from the issuer, reserve and disclosure conditions, and the platform’s own due diligence (CSA Staff Notice 21-333). The practical effect for a Canadian who wants to fund an agent from a registered platform is that the stablecoin has to be on that platform’s supported list, and the lists are short and change. Our buying guide covers which platforms are registered; the law tracker carries the notice.
Securities registrants and their AI. If the company deploying the agent is itself a registrant, CSA Staff Notice 11-348 of December 5, 2024 already applies: firms are responsible for the outputs of the AI systems they use, must test before deployment, keep a human in the loop and be able to explain what the system did (CSA Staff Notice 11-348). An agent that spends client money is an output.
And one consultation to watch. The federal government’s AI transparency consultation, open July 23 to September 23, 2026, asks explicitly how the activities of AI agents should be tracked, alongside labelling generated content and reporting serious incidents (Government of Canada, July 23, 2026). We covered the wider patchwork, from the death of AIDA to OSFI’s 2027 model-risk guideline, in Canada’s AI rules in 2026. If your product gives agents wallets, the tracking question is aimed at you, and the submission deadline is thirteen days after this guide’s date.
What to build, and what to count
The honest state of agent payments in September 2026 is a working standard, real infrastructure and very small money. That is the right moment to build, and the wrong moment to believe volume charts. Count payments, not dollars, when you evaluate a rail. Price per call, not per month, when you sell to agents. Treat the wallet’s authority model as your product’s most important feature, because it is the one a customer will sue over. And if you want to meet the people building this in Canada, the country’s AI ecosystem gathers in Montréal for ALL IN on September 16 and 17, 2026, and the directory lists the Canadian companies working across AI and digital assets, several of which would like to hear from you.
