Something new at Stripe

Shape agent handoffs while shoppers lose their checkout context

Published Oct 23, 2026

You’re the program manager. Your team is in the room.

The setting

's is a digital wallet that stores payment details for people who shop online. It fills them in at checkout so customers can pay quickly at participating merchants.

The agent can begin a purchase, but the shopper must still finish the decision.

Checkout continuity protects conversion, while authentication and fraud controls protect the shopper and merchant.

Who you’d be doing this for

“My agent got me to the payment screen, then I had to start the whole checkout again.”

Takeshi Yoon · Online Shopper · a character in this brief

A returning shopper using an AI agent to purchase from a merchant that offers Link.

What is at stake

Eligible agent purchases lose momentum when authentication or price changes send shoppers back into checkout. You must weigh a fast, coherent shopper handoff against fraud, identity, and support readiness.

Why it isn’t already fixed

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

  • checkout continuity vs. shopper authentication
  • agent purchase growth vs. fraud exposure
  • first-market learning vs. support readiness
  • shared launch rhythm vs. independent workstreams

Why Stripe

Link connects saved credentials, shopper identity, and payment completion across merchant checkout surfaces.

Written with these in mind

cross-functional launch operatorpayments programme managerconsumer experience programme leader

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

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Stripe. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • Technical Program Manager, Link · no longer posted
    • Link spans multiple interconnected workstreams, including payment methods, money movement, fraud and authorization, consumer accounts and identity, and consumer preference, and a TPM here plays a critical role in keeping those threads aligned and moving forward at velocity.
    • Understand the technical challenges across Link's systems, payment flows, identity infrastructure, fraud and risk models, money movement, and partner closely with engineering leads to define the most effective path to delivery
  • Operations Program Manager, Consumer Support (opens in a new tab)
    • Lead or partner with cross-functional teams, including Product, Engineering, Legal, Compliance, Support, Operations Technology, and Vendor Management, to define operational requirements for new Link, Stripe Managed Payment, and Crypto Onramp products, features, and experiments
  • Brand Producer, Link · no longer posted
    • Can manage the operational business of the team — budgets, resourcing, and program rhythm — while maintaining a clear point of view on where the program is headed and what it needs to get there
    • Have a strong strategic acumen for developing complex program roadmaps and cross-functional processes in a fast-paced environment

Reporting read before this brief was written

The pieces closest to the situation in this brief.

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.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these is about money moving incorrectly, late, or twice.

The same setting, from another role

Each is set around Stripe’s Link, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to make complex payment systems feel dependable in the exact real-world moment someone needs to complete one.