Delegated payments: consent given once, used within limits
Payment law already lets consent travel through a payee or an initiation service. Protocol tokens and mandates add limits that the payment provider can enforce.
A delegated payment is one the customer authorises in advance, so that someone else, here an agent, can complete it later within limits.
What payment law already allows. Under PSD2 Article 64, a payment is authorised only if the payer has consented, in the form agreed with the provider. Consent may be given before or, if agreed, after execution, and it may be given via the payee or a payment initiation service provider. Consent can be withdrawn.
How protocols express the limits.
- In the Agentic Commerce Protocol, the payment provider issues a vault token under an allowance: maximum amount, currency, checkout session, merchant and expiry. The provider enforces the limits.
- In the Agent Payments Protocol, an open Payment Mandate carries constraints such as allowed payees and instruments, an amount range, a budget and agent recurrence; a closed mandate binds a specific amount to a finalised checkout.
What makes delegation safe is where the limits are enforced. If the limit is held only inside the agent, a fault or an attack on the agent can exceed it. If the payment provider, issuer or bank checks every payment against the mandate, the agent cannot.
Questions to settle before launch: who records the customer's consent and in what form; who checks each payment against it; how the customer revokes it; and what evidence each party keeps if the customer later says a payment was not authorised.
This is general information, not legal advice.
Sources: Directive (EU) 2015/2366, PSD2 (EUR-Lex, archived), Agentic Commerce Protocol: delegate payment, Agent Payments Protocol (AP2): Payment Mandate