Your agent now has a wallet, a spending cap and an approved merchant list.
None of those three things is a signature.
On 4 August Cloudflare announced Wallets and cloudflare.pay — a stable identity for an agent, and a balance it spends from. Handles open now; wallets and per-agent Virtual Wallets come "in the coming months". The controls are what you'd design: a cap, an approved merchant list, a maximum transaction size.
Now hold that against European payments law.
If the stablecoin is an e-money token, MiCA Article 48(2) deems it electronic money, and PSD2 counts electronic money as funds. The EBA's opinion follows through: transferring them for clients is a payment service, and a custodial wallet that pays third parties is a payment account.
That drags in Article 97 — strong customer authentication when the payer initiates an electronic payment transaction, dynamically linked to a specific amount and a specific payee.
A cap does not link to an amount. An allowlist does not link to a payee. They authenticate a policy once, and every later payment inherits it.
The part that should change your architecture: the exemption that makes agentic spending workable is trusted beneficiaries, and its rule is one sentence. Providers shall apply strong customer authentication where a payer creates or amends the list of trusted beneficiaries.
The security-critical event is the config change. Not the payment.
And the law puts liability behind it. Article 73 refunds an unauthorised transaction by the end of the next business day, and in C-70/25 the Advocate General went further: refund first, argue later. Whoever proves authorisation afterwards proves it from logs.
What I'd do Monday:
1. Treat allowlist and cap edits as privileged operations — signed, reviewed, logged separately from the payments they authorise.
2. Never let an agent widen its own limits. An injected agent that amends its allowlist has done the one thing the rule exists to prevent.
3. Ask your wallet provider in writing whether the token is an e-money token and who holds the licence. Cloudflare's release names no stablecoin and says nothing about custody, KYC or the EEA.
4. Log per transaction: which instruction, which amount, which payee, which approval it inherited.
The wallet is months away. The logging decision is this sprint.
Could you show, three months later, who authorised one specific payment to one specific payee?
#AgenticAI #PSD2 #MiCA #AIEngineering #Berlin
AI disclosure: the narration voice and the cover art in this video are AI-generated. The script, the claims and the source checks are mine.