The originations pause protects the bank partner while platforms still need a truthful account status.
Blocking every new partner request prevents further exposure, but changing an in-flight workflow can leave applicants with conflicting records.
Who you’d be doing this for
“My ops lead has three sellers asking why the same application says pending, failed, then pending again.”
Inyoung Lim · Payments Product Manager
Owns the account-opening experience for a marketplace that embeds financial accounts for its sellers.
What is at stake
The bank partner received account requests after its pause, while applicants see conflicting statuses. You must weigh an immediate hard stop against the integrity of every application already in flight.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- partner pause vs. platform onboarding continuity
- immediate containment vs. in-flight record integrity
- API simplicity vs. workflow correctness
- fast shipping vs. auditable evidence
Why Stripe
Treasury financial accounts depend on partner-bank integrations that must keep money-moving products explainable when originations stop.
Written with these in mind
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.