A mandate is easier to understand by looking at where it says no. As long as the agent does what it was asked, all systems look alike, and the difference shows when it tries to do one thing more, by mistake or because someone talked it into it.
These five cases are scenarios, built on the rules Plenipo applies today in the public sandbox: invented names, a simulated bank, real refusal codes.
The household bills
Luca authorises his assistant to pay electricity and water. On his phone he reads two suppliers, 150 euros at most per operation, 300 in total, one week of validity, and he approves.
The electricity bill for 84.30 euros goes through. The water bill, which reached 180 after an adjustment, is refused with the code LIMIT_PER_OPERATION, and the assistant goes back to Luca to explain that a wider permission is needed. Nobody made a mistake, the limit did its job.
The email asking for a refund
Same mandate, a few days later. A message lands in Luca's inbox that looks like it comes from the water supplier and asks for 38.75 euros to be paid to a new account, with an almost identical name. The assistant falls for it, because the text was written for it.
The bank does not. That payee does not appear in the mandate and the request comes back with COUNTERPARTY_NOT_PERMITTED, while the payment to the real supplier is executed. It is one of the scenarios in the public demo and the one I find most instructive, because anyone who works with agents knows that persuading them to deviate is easier than we would like.
A small company's purchases
A workshop with six employees uses an agent to reorder consumables. The owner signs a mandate towards three wholesalers, with a cap per order and a monthly one, and leaves every other expense out.
When the agent finds the same product cheaper from a fourth seller it cannot buy it, and this time the refusal has a cost. The owner decides whether to widen the list, knowing that every extra name is a place money can go without her looking.
A trip booked by more than one agent
To organise a business trip, Marta's assistant hands the hotel to a specialised agent. Marta's mandate allows sub-delegation only with narrower powers, so the second agent receives a permission for that hotel, those dates and that amount, and nothing else.
If the mandate said that delegation to other agents is not allowed, as in Luca's case, the handover would be refused and the main assistant would have to complete the booking itself.
A parent's errands
This is the case I care about most. A daughter helps her eighty-year-old father with the pharmacy, bills and subscriptions, and today she does it with his passwords, which means with the whole account in her hands.
With a mandate the father approves a precise list of things from his own phone, sees it written down, and can revoke it whenever he wants without changing credentials and without having to explain anything to anyone. After revocation the bank stops accepting it within about a minute, and at expiry it stops anyway.
Read together, these cases have one thing in common: the refusal always comes with a reason a person can read. A "no" that says why can be discussed and corrected, and that seems to me the minimum basis for letting software act in our place.