Asking an assistant to find a theatre ticket or book a flight is a simple action. Authorising it to make the purchase takes us a step further: the machine must turn an intention into spending, within limits the person can understand and change. This is where the question of delegating spending authority to artificial intelligence agents begins.
Who authorises the machine to pay: delegating spending authority to AI agents
Special Issue 6B | 1 August 2026 | Approximately 5 minutes to read
1. When a request becomes spending
“Find a ticket to Rome, avoid travelling at night and do not exceed €180.” In everyday life, this is an ordinary, natural sentence. For an agent authorised to buy, it contains several decisions that remain open: which times to exclude, whether the price includes baggage and fees, which sellers to accept and how much the offer may change before confirmation must be sought again.
Searching can help make these conditions visible. Payment turns them into consequences: a charge, a contract, a possible refund. This is why the ability to find a good offer and the authority to spend must be separately identifiable. An agent may understand a request without having received permission to carry it out. Clarity matters precisely where convenience risks concealing the delegation of authority.
2. A mandate we can read
Delegated spending authority becomes manageable when it takes the form of a mandate: a verifiable description of what a person authorises. It must connect an objective to an agent, set limits on amounts and recipients, specify a duration and establish which changes require a new decision. A generic “you decide” leaves too much room for interpretations that may become apparent only after the purchase.
A spending limit alone does not resolve everything. A seller can be unreliable even within budget; an inexpensive product may have inadequate return conditions. The mandate must therefore remain tied to the context and provide for a stop when important information is missing. If a condition changes, the agent must be able to return the choice to the person instead of completing the process regardless.
🧠 Radar Insight — Capability and authority
Understanding what we want does not mean being authorised to buy it. Capability concerns the work the agent can do; authority concerns the power we entrust to it. Separating them makes it possible to recognise when a proposal is needed, when confirmation is required and when the process must stop.
3. Where the payment rule sits
Talking about programmable money can make different architectures seem identical. In an instrument with built-in restrictions, the constraint accompanies the value and limits its uses. In a conditional payment, by contrast, the service initiates the transfer when an event occurs: a delivery, a deadline or an approval. The money can remain ordinary while the rule belongs to the process that transfers it.
The ECB explicitly distinguishes these two levels in the digital euro project: it rules out money with predetermined uses and allows for the possibility of conditional payments. The distinction helps us ask a concrete question: who defines the condition, who verifies that it has been met and who intervenes if the verification is wrong? Programmability moves a decision into an infrastructure; that decision continues to require accountability.
4. A signature does not guarantee a good choice
To accept an agent, a merchant must be able to recognise the origin of the request. Digital signatures help verify that a message comes from a recognised key and has not been altered. Payment credentials can also be restricted to an amount and a recipient. These are important protections because they reduce some of the ways delegated authority could be misused.
Identity verification does not, however, assess whether the purchase is a good choice or demonstrate that the intention has been understood. A transaction can be technically authentic and wrong for the person’s needs. The agent, platform, shop and financial network control different stages: even if each sees only its own part, it must still be clear who takes up a problem and helps the person resolve it.
5. The same transformation reaches the banks
Programmability also enters coordination between financial institutions. The Bank for International Settlements’ Project Agorá explores wholesale cross-border payments through a prototype that brings together central bank reserves and tokenised commercial bank deposits. Tokenisation means digitally representing a form of value on an infrastructure capable of transferring it according to defined rules.
Among the possibilities being studied is atomic settlement: the parts of a transaction are completed together or not at all. It is a way to address the risk of disconnected steps, but still requires choices about law, system governance and operational functioning. An institutional prototype, a consumer purchase and a digital currency project belong to different levels. Keeping them distinct helps us understand where innovation is taking place and which safeguards remain to be built.
📖 Further reading — One chain, different responsibilities
The mandate sets the boundaries of delegated authority; recognition verifies the agent’s origin; payment moves the value; recourse reopens a disputed decision. None of these stages automatically encompasses the others. The quality of the whole also depends on the connections between responsibilities.
6. The right to reopen the decision
Good automation preserves a way back. Before the purchase, it makes the amount, recipient, duration and shared data clear. During execution, it checks that the context has not changed. Afterwards, it retains a receipt that can connect the request, proposal, authorisation and result. Revoking delegated authority should not require people to reconstruct the entire technical chain on their own.
These are design conditions proposed by the Radar analysis, to be checked in actual services. Not every infrastructure allows the same kind of refund or correction: this is precisely why the limit must be understood before entrusting the action to the agent. The machine can reduce the work needed to pay. The right to determine how much power it receives, stop it and ask an accountable person to examine an error must remain identifiable even when everything happens very quickly.
Read the full issue
This article presents selected passages from Radar Special 6B. The full dossier contains the complete discussion and further analysis from the original edition (1 August 2026).
© 2026 Barbara Gattobigio · Gruppo Radar
Comprendere oggi. Costruire domani · by effettoantropico.life
All rights reserved on original content. Free access does not authorise reproduction or republication without consent, except as permitted by law. Third-party materials remain the property of their respective owners. To share this issue, use the link to the article.
Continue reading
Understanding Today. Building Tomorrow: the project and the Radar collection.
The invisible infrastructure: who can enter the network.
From chat to desk: governing the work of AI agents.
Cover in focus

