Human present or not: two kinds of agent purchase
Some agent purchases happen while the customer watches; others run later, on their own. Why the difference changes authentication, evidence and risk.
Agent purchases fall into two broad kinds, and the Agent Payments Protocol's documentation is organised around them: its samples cover human-present and human-not-present transactions, with cards and with x402.
Human present. The customer is in the conversation when the agent finds the item. The customer can review the final checkout and authenticate it at that moment, for example on a trusted surface. In AP2 terms, a closed mandate captures approval of one finalised checkout and amount.
Human not present. The customer set the goal earlier and is absent when the purchase happens, for example "buy these tickets when they go on sale, up to this price". The authority must already exist: in AP2, an open Checkout Mandate and open Payment Mandate carry the constraints, such as allowed merchants, items, budget and recurrence. Visa describes a similar idea: the customer authenticates a payment instruction with a passkey in advance, and the platform later checks credential requests and authorisations against it.
Why it matters:
- Authentication. Present purchases can use SCA at checkout. Absent ones need authentication at set-up and a basis, such as an exemption or an authenticated instruction, for the later payment.
- Evidence. Absent purchases depend on proving that the purchase matched what the customer set up.
- Risk. Prices and availability change while the customer is away, so limits should be explicit and narrow.
This is general information, not legal advice.
Sources: Agent Payments Protocol (AP2) documentation, Agent Payments Protocol (AP2): Checkout Mandate, Agent Payments Protocol (AP2): Payment Mandate, Visa Developer: Visa Intelligent Commerce