Credential modernization becomes difficult when the old path is embedded in systems that cannot pause.
Security certainty and processing continuity can demand incompatible levels of caution near a fixed cutover.
Who you’d be doing this for
“I support removing the old secrets, but a surprise cutover failure would hit every seller.”
Eva Jansen · Director of Payments Infrastructure
Runs infrastructure for a global marketplace whose authorization and payout workflows depend on uninterrupted worker processing.
What is at stake
27% of payment workers still pull credentials from the legacy path, and the generated dependency maps list consumers with no owner. You have to decide how much of that evidence to trust before the old path is turned off.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- secret elimination vs. payment continuity
- automated inventory vs. verified evidence
- fixed cutover vs. narrow recovery windows
- security urgency vs. outage tolerance
Why Stripe
At Stripe, this tends to matter where credential boundaries support services that process payments and move funds continuously.
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.