StripeAna AndresExplainer
Agentic payments for marketplaces: How a smart fridge can shop safely
Summary
GreenMart’s smart-fridge scenario addresses how an agent can turn a detected grocery need into an authorized order without receiving unrestricted access to household card or wallet credentials. GreenMart uses Stripe Agentic Commerce Suite to expose its catalog and checkout through a hosted Agentic Commerce Protocol (ACP) endpoint, while retaining responsibility for inventory, pricing, fulfillment, and order operations. A fridge agent discovers products and creates a checkout, and a companion app evaluates the final checkout against deterministic household rules covering items, totals, delivery, substitutions, and budgets. After approval, Link can provide bounded payment authority, while direct Shared Payment Tokens (SPTs) support lower-level Stripe integrations; virtual cards are described for eligible non-Stripe merchants. The design emphasizes auditable policy decisions, explicit escalation or denial, idempotent retries, webhook reconciliation, and stopping when changes exceed the household’s authority.
Context
The architecture addresses how a fridge sensor signal can lead to a trusted grocery order while allowing an agent to act autonomously within household-defined limits. It focuses on the commerce flow after the fridge detects that something needs to be bought, including product discovery, checkout, policy evaluation, delivery choices, substitutions, and payment authorization without exposing reusable household card credentials.
Approach / What changed
GreenMart connects its catalog and commerce data to Stripe Agentic Commerce Suite, which provides a hosted ACP storefront and checkout surface. The fridge agent and companion app use ACP, while the app evaluates each final checkout with deterministic household policies. Approved checkouts receive bounded payment authority through Link or, for lower-level integrations, Shared Payment Tokens; payment and order processing then proceed through the supported Stripe or virtual-card path.
Takeaways
Household policy evaluates the final checkout, including merchant, items, quantities, total, currency, fulfillment, delivery details, substitutions, and budget already spent; its result is approved, requires approval, or denied.
Link can abstract Shared Payment Token mechanics for the agent, while direct SPT integrations remain available when the agent, wallet, or marketplace needs explicit token control. The agent receives bounded authority rather than a card number.
If a substitution raises an order beyond policy, the agent must find another option, remove the item, choose a different delivery window, request approval, or cancel; it should not silently accept the change.
Source and freshness
- Source
- stripe.dev
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.