← Stripe
Complex day at Stripe

Commit the price-change handoff before merchants limit agent purchases

You’re the software engineer. Your team is in the room. Printed Oct 19, 2026.

The price-change handoff must preserve shopper control without opening a route around authentication controls.

Fast completion protects agent-driven purchases, while strict verification protects merchants from bad actors.

Who you’d be doing this for

“My agent found the item, then the price changed and I got bounced back to a blank checkout.”

Tsehay Ndungu · Retail Shopper

Uses saved payment details through an AI agent to complete purchases at participating merchants.

What is at stake

Approved agent purchases with changed prices are failing during authentication. You have to weigh faster completion against a control path that bad actors could exploit.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • shopper completion vs. authentication integrity
  • agent convenience vs. direct consumer consent
  • rapid merchant expansion vs. irreversible control changes
  • observed failures vs. inferred abuse patterns

Why Stripe

Link’s saved credentials and agentic purchase experience put shopper trust and merchant checkout completion in the same transaction path.

Written with these in mind

security-minded full-stack engineerpayments reliability engineerproduct infrastructure engineer

Not your kind of problem? 88 more at Stripe, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.