Stop Making Your Customers Click Approve - Emil Chetty, Wise
Loading slides…
Read the talk
What did the customer actually approve? Inside Wise’s design for agent payments
Emil Chetty follows a $775 supplier payment run from a business owner’s request to the service that moves her money, showing where an agent can choose its own steps and where it needs her decision.
From a talk by Emil Chetty
At a glance
Ideas worth remembering
Use read-only preparation to resolve suppliers, bank details, amounts and fees before asking the customer to approve an exact version of the job.
Derive worker access from the confirmed job, the platform’s policy for agents and the customer’s current rights. Check the terms again at the service that moves the money.
Use shared execution state to resume interrupted payments. Bring a changed quote or recipient back to the customer for a new decision.
An assistant that keeps asking for permission
A coding agent wants approval to run a command. ChatGPT asks permission to scrape a website. Hermes wants to read from an MCP the user remembers giving it permission to read. Emil Chetty opens with a frustration familiar to engineers, then asks what that experience would feel like to someone who adopted an assistant on the promise that it would simplify their life. The work arrives back on their desk as a queue of requests. To get any value out of the assistant, they have to keep servicing the queue.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Three products share a payments network and a duty to explain
Chetty leads data and AI product at Wise. The Wise Account helps individuals manage money across borders, including spending and saving locally. Wise Business gives small and medium-sized businesses a way to operate internationally from day one. Wise Platform gives banks and other financial institutions access to the payments infrastructure Wise has built since 2011, so they can offer that experience directly to their own customers.
Behind all three is one global payments network. It works with more than 90 local banks and payment providers and connects directly to domestic payment schemes. Chetty says Wise moved more than $243 billion across borders last year and serves nearly 19 million active customers. Wise holds more than 80 licenses worldwide. The requirements that apply to a payment can vary with the currency, country, regulated entity and product.
A customer can enter an instruction in a chat bar, but Wise still has to establish what that customer authorized, control what happens to their money and explain the outcome to a regulator. Any autonomy Wise gives an agent has to leave the company able to answer for a particular payment after it goes through.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Eight interruptions to handle one week’s suppliers
Consider a small-business owner who asks an assistant to handle this week’s approved suppliers, reconcile the results and bring back the exceptions. She has specified both the work and when she wants to hear about it. Looking up an account and checking the status of a payment are part of the work she expects to hand over. An exception that needs her judgment is a reason to interrupt her.
Chetty’s example breaks the job into eight steps. The assistant asks whether it may look up payment account details and whether it may scan a PDF to understand an invoice. With time between requests, the owner has to remain available even for the parts she wanted to delegate. And her permission to read an invoice tells Wise very little about whether she agrees to send the amount on it to a particular bank account.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
What coding agents solved, and what a payment still needs
Engineers used to watch a terminal for much the same reason. Running tests needed a click. Fetching the latest documentation from Confluence needed another. Chetty points to Anthropic’s auto mode as a meaningful reduction in friction. Permission rules let routine actions proceed, classifiers assess proposed actions, and a sandbox limits what an agent can affect. Those controls give an engineer a basis for letting work continue without having to watch for a command that might delete a production database.
For payments, Chetty puts the question precisely: “Did this customer authorize this payment to this recipient on these terms?” A payment can look routine to a classifier while the intended recipient is still in doubt. Evals can assess the agent’s behavior, and a harness can embed controls over its execution. Chetty expects to need both. Neither supplies the missing customer decision. If the only evidence for sending the money is the model’s account of what the customer wanted, Wise has allowed the model to authorize its own interpretation.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Turn intent into an agreement the payment service can enforce
Wise’s design starts with the vague request and uses trusted software to establish a specific proposed outcome. The customer inspects that outcome and confirms the bounds within which the agent may operate. Wise then records the agreement in its trusted stack and uses it to provision authority. The agent can plan how to do the work. When it asks a service to execute a payment, that service can check the request against the same agreement. Results and exceptions go back to the customer.
The agreement also settles who gets to make the next decision when circumstances change. The agent can revise a plan that still delivers the agreed payment on the agreed terms. A change to those terms requires a revised proposal and a customer decision. That distinction lets Wise lock the customer’s instruction while leaving the sequence of operations open.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Sarah reviews three suppliers, $775 and an allowance for fees
Chetty works through a hypothetical run for Sarah, the business owner. The agent starts with her credentials and existing account setup and explores with limited read-only access. Trusted software attached to the account resolves the suppliers, their bank details and the amounts from the underlying records. At this point the system has enough information to prepare a proposal. Reading the records gives the agent no authority to move the money.
Sarah sees a draft covering three suppliers, $775 in payments and an allowance for fees. The draft also has to make the delegation intelligible. Which decisions is she comfortable handing over, and which does she want brought back to her? Any missing or conflicting details have to be settled while she can still revise the draft. Leaving a supplier ambiguous here would leave the agent to decide later who gets paid.
The job has two views. Sarah reads a promise in ordinary language. The services receive a machine-readable promise specifying the bounds they can verify when a payment request arrives. Sarah clicks Approve, confirms and authenticates. Wise records her decision against that exact version. Only then does the draft become an immutable, authorized job.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Three constraints determine what the workers can do
A trusted provisioning platform derives access deterministically from the intersection of three things. The confirmed job specifies what Sarah agreed to on this occasion. Wise’s policy specifies which actions an agent may perform. Sarah’s current rights specify what she herself has authority to do. Her ability to pay other suppliers cannot broaden a job covering three, and including an action in a proposal cannot put it within either Wise’s policy or Sarah’s rights.
The platform provisions limited access for execution, with a payment worker and a reconciliation worker handling the two parts of the job. The agent still decides how to achieve the result, including how to follow up on payment status and reconcile what happened. Sarah can delegate those decisions because a change in the workers’ plan leaves the confirmed agreement intact.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A restarted worker follows the payment; an expired quote goes back to Sarah
Suppose a Kubernetes pod restarts, or the app crashes on Sarah’s phone and she restarts the job. The agreement establishes what may happen, but the recovering worker also needs to know what has already happened. The services share payment state and can look up what has been executed. The worker follows the existing payment job. If the first attempt already moved the money, restarting the work does not create a second payment.
Now suppose the worker discovers that a quote has changed or expired. Sarah approved that specific quote. Looking up the existing job can establish what she agreed to, but it cannot extend her decision to a replacement price. The agent prepares an updated proposal, shows Sarah what changed and asks her to agree to the new version. Once she does, execution can continue under the revised agreement.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Follow a payment call through the gateway
Chetty describes the implementation at Wise as a rough sketch of what the team has built so far. Calls to LLM providers follow controlled routes. An agent gateway provides a place to register tools and record evidence of their use. Following one payment through the system makes the division of responsibility clearer. The worker checks which tools it can use, then calls the payment service through the gateway. The service checks the requested payment against the immutable job record.
The distinction matters when a worker legitimately has access to a payment tool. That access explains how it can submit a request. To decide whether to move money, the service still needs the terms of Sarah’s job, including the recipient she approved.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Assume the prompt injection persuades the agent
Chetty tests the design with a message claiming that a supplier’s payment details have changed. Grant the attacker a successful prompt injection. The agent believes the message and tries to pay the new recipient. Its belief changes the request it sends, but the agent has no authority to rewrite Sarah’s confirmed job. At the service check, the new payee fails to match the agreement.
The protection depends on the downstream service actually checking and enforcing the recorded terms. Wise can draw on the payment software it has been building since 2011 to stop the request even when the model misses the scam. The failed attempt illustrates why enforcement belongs at the point where the money would move.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Reconstruct the decision after the run
For any payment, Wise wants one chain of evidence connecting who authorized the job, what authority the workers received and what the payment service executed or stopped. That gives Wise a way to establish responsibility and assess whether the agent did the work it was given. For Sarah, it gives an approval request a particular meaning. A worker can recover from a crash on its own. When it comes back with a changed quote, there is a new decision about her money worth her attention.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Full transcript
Loading transcript…