The marketplace must leave its current provider without turning seller payouts into an unprovable balance calculation.
The commercial exit date protects the marketplace’s costs, while verified seller balances protect trust in every payout.
Who you’d be doing this for
“Our finance lead asked why one seller’s refund showed up before the charge, and I had no clean answer.”
Adrien Van den Berg · Payments Engineer
Owns the marketplace’s payout and refund integration for European sellers.
What is at stake
Seller balances cannot yet be explained consistently when refunds and multi-currency payments arrive out of order. You must weigh the provider exit date against the proof finance needs before funds move.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- provider exit date vs. seller balance proof
- broad migration vs. controlled cohort release
- eventual consistency vs. payout certainty
- engineering change window vs. finance sign-off
Why Stripe
Stripe Connect sits at the center of the marketplace’s seller onboarding and payout architecture, so an inaccurate migration reaches every seller awaiting funds.
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.