A required infrastructure change can be technically ready before its operational equivalence is proven.
The pressure to leave a retiring system can conflict with the cost of disrupting legitimate payment traffic.
Who you’d be doing this for
“A maintenance window is manageable; blocking our payment traffic isn’t.”
Veronica Reyes · Director of Payments Engineering
Leads a commerce platform whose checkout and payout services depend on uninterrupted API access from several regions.
What is at stake
The old policy engine loses support soon, and 0.7% of shadow-tested requests still differ on client IP handling. Each segment moves one way only, so you decide how much proof is enough before cutting over.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- retirement deadline vs. proof of equivalence
- access control vs. payment availability
- generated policies vs. human verification
- maintenance certainty vs. merchant continuity
Why Stripe
At Stripe, this often matters because network controls and payment availability are experienced as the same moment by an API caller.
Written with these in mind
Not your kind of problem? 17 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.