Standardize global payment-state representation
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.
“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 pulls against what
- global consistency vs. local obligations
- distinctive expression vs. payment recognition
- launch speed vs. verified conformance
- shared-system durability vs. surface-specific needs
What is at stake
Inconsistent payment assets are now a launch-readiness problem, not a cosmetic cleanup. The selected system will be difficult and expensive to unwind once shared surfaces adopt it
Why Stripe
At Stripe, it often matters because payment representations travel across merchant and buyer moments in many regions.
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.