Retire legacy worker secret paths
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.
“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 pulls against what
- secret elimination vs. payment continuity
- automated inventory vs. verified evidence
- fixed cutover vs. narrow recovery windows
- security urgency vs. outage tolerance
What is at stake
A fixed migration requires eliminating a legacy credential path without interrupting money movement. The evidence is rich but not fully trustworthy, so every dependency claim must be verified before cutover
Why Stripe
At Stripe, this tends to matter where credential boundaries support services that process payments and move funds continuously.
Written for
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.