You approve a cart for $42. Before the agent checks out, the price goes up to $48. It could try another seller. It could also send the same payment twice after a timeout. A checkout team has to decide which requests still carry the authority you gave the agent.
Reap, EveLab Insight and Pivota announced a memorandum of understanding to explore agentic shopping on November 5. That puts the approval question in a familiar setting where a recommendation can become an actual purchase. Announcement from Payward
Make the consent visible and precise
An open instruction such as “find a moisturizer under $50” and an approval of a final cart are different artifacts. If a customer approves the specific cart, show the merchant, items, total including fees, currency and expiry. Capture the cart identifier and revision alongside the approval. A change can then be checked against what the customer actually saw.
The Agent Payments Protocol describes open and closed mandates for expressing constraints and binding a checkout and payment to intent. A team adopting the protocol still needs to decide how its product handles quote changes, expired approvals and recovery from uncertain payment results. AP2 specification
Check the request at the payment boundary
The chat transcript helps explain the purchase. The payment service should evaluate structured authorization it can validate. In this lab the grant is narrow. It authorizes one exact $42 cart at one merchant before an expiry. A new merchant, a new amount or an expired grant requires another approval.
When the payment service sends an authorized charge, the provider’s answer can be delayed. Tie retries to a durable purchase identifier and use the provider’s idempotency mechanism where available. If the result is unknown, recover the existing attempt before initiating a replacement. An idempotency key also needs to be scoped to the checkout, payment instrument and relevant merchant or tenant so it cannot collide with another purchase.
Give support the same receipt the customer sees
Keep the consent reference, checkout revision and provider payment reference in one explanation. Show which amount was authorized, which amount was charged and when. A support operator should be able to explain a blocked request without seeing a full card number or the entire chat history.
Try Agent Checkout Lab
Approve the sample cart and try a price change, another merchant or an expired consent. Run the matching checkout twice and compare the receipts. The simulation uses a fictional provider and a one-time authorization. It models selected product rules with local fixtures.
What dOrg would build first. Bring one existing checkout and a concrete agent workflow. We can scope the approval screen, authorization check, retry handling and an acceptance suite that your payments and operations teams can inspect.