Evolving a payment checkout to support multiple payment methods, user scenarios and regulatory requirements without passing that complexity to the user.
What started as a relatively linear payment journey evolved as new payment methods, user scenarios and technical requirements were introduced.
The challenge was not simply adding new features, but keeping the experience understandable as the system behind it became increasingly complex.
The first version handled authentication, company information, and bank selection as separate steps. Overall, the experience was fragmented and lacked a clear design direction. The main goal at that stage was simply to make each part work, rather than designing them as pieces of a cohesive product. As the checkout evolved and became more complex, this approach made it increasingly clear that a more structured and unified experience was needed.
As the product evolved, new payment methods, user states, fallbacks and business rules created multiple interconnected journeys.
Mapping them helped me understand where complexity belonged in the system, and where it shouldn't reach the user.
The checkout gradually moved from a single payment journey towards a more flexible experience able to accommodate different methods, payment conditions and user contexts.
The current experience brings payment information, user identification and available payment methods into a clearer structure, while adapting the journey to the user's context and selected method.
Payment experiences sit at the intersection of user needs, technical capabilities, business requirements and regulation.
I worked closely with product, engineering and compliance to translate those constraints into interactions users could understand and trust.
What began as an existing checkout became a more flexible experience designed to support different scenarios without exposing the complexity behind them.