A shared visual system becomes costly to change once it reaches every payment surface.
Recognition, local relevance, accessibility, and consistency can demand different answers from the same asset.
Who you’d be doing this for
“We can’t keep patching icons market by market and hope buyers still know what they’re choosing.”
Riyad Chamoun · Product Design Manager
Leads checkout experiences for a marketplace operating across several payment-method markets.
What is at stake
An audit found 78 of 186 merchant-facing surfaces using outdated or inaccessible payment marks, and production starts before a fixed launch date. What you lock will be hard to unwind once shared surfaces adopt it.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- global consistency vs. local obligations
- distinctive expression vs. payment recognition
- launch speed vs. verified conformance
- shared-system durability vs. surface-specific needs
Why Stripe
At Stripe, it often matters because payment representations travel across merchant and buyer moments in many regions.
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.