Paysafe
Designing and developing mobile payout experiences for the global leader in digital payments.
// Project Goals
To help evolve two strategic product initiatives within Paysafe’s broader payments ecosystem: a flexible, white-label wallet platform designed to adapt to different partner brands, and consumer wallet experiences focused on simplifying onboarding, increasing trust, and making everyday financial actions easier to complete.
This spanned Paysafe Wallet (the white-label foundation), PagoEfectivo (a Peru-market wallet built on top of that white-label system). The goal was to turn complex financial infrastructure into intuitive, scalable, and commercially relevant digital experiences — through product thinking, UX architecture, branded customization systems, mobile interface design, and user testing.
// The Result
We can’t share every metric or internal outcome, but the key results we can disclose are enough to show the impact — and to give a clear picture of what changed.
+19%
User activation rate
245%
Monthly active users
380%
Transaction completed
4.6
Customer satisfaction
From Wallet to Scalable Product Platform
The Paysafe project started with a broader challenge than designing a single financial product. The goal was to create a wallet experience that could work across different brands, markets and business contexts without rebuilding the product from scratch every time.
I worked on defining how the wallet could become a reusable platform rather than a one-off interface, while still feeling coherent and trustworthy to end users. That meant balancing brand flexibility with product consistency and making sure that changes made for one partner would not compromise usability, accessibility or the underlying structure of the experience.
The work gradually shifted from designing individual screens toward defining a product system that could scale across multiple implementations.
Designing Controlled Flexibility
A white-label financial product needs to feel recognizably different for each partner without becoming fragmented or difficult to maintain. I focused on creating a controlled customization model where partners could influence high-impact elements such as identity, logo and brand colors, while the product itself retained responsibility for hierarchy, interaction patterns, accessibility and core behavior.
The principle was to give partners enough control to make the wallet feel like their own product without allowing arbitrary decisions to weaken the experience.
This required thinking beyond visual styling and defining how brand choices should translate into semantic roles across actions, surfaces, feedback, states and reusable components throughout the wallet.
Turning Design Decisions Into Product Architecture
As the platform grew, even small design decisions started to have wider consequences. A color choice was no longer just a visual choice; it could affect buttons, transaction states, navigation, alerts and accessibility across every future implementation. I therefore treated the interface as a system of relationships rather than a collection of screens.
Brand inputs needed to map into semantic roles, those roles needed to drive reusable components, and those components needed to work consistently across dashboards, payments, cards, transactions and profile experiences. This shift made the design work less about styling individual surfaces and more about defining rules that could remain stable as the product expanded into new brands and use cases.
Applying the System to a Real Market
The platform thinking became more concrete when applied to PagoEfectivo in Peru, where the challenge moved from scalability to user activation and financial onboarding. The experience had to balance identity verification, fraud prevention, eligibility rules and security with the user’s need for speed, clarity and confidence.
I focused on reducing unnecessary friction without weakening the controls required by a regulated financial product. Rather than treating onboarding as one long compliance process, the journey was structured around progressive commitment, where users understood what was being asked, why it mattered and what would happen next.
Edge cases, verification outcomes and alternative paths were designed as part of the system from the beginning rather than added after the happy path was complete.
Designing for Scale, Trust and Measurable Impact
The strongest outcome of the project was not a single interface but a product model capable of balancing brand, business, technology, regulation and user needs at the same time.
Research helped refine how users understood customization, especially around primary and secondary brand colors and the relationship between configuration and final product behavior. The work contributed to measurable improvements (you can see the metrics in the beginning of this case study). More importantly, it reinforced a broader design principle: when a financial product becomes a platform, every design decision becomes more consequential because it can shape not one experience, but many.
The best fintech systems do not eliminate complexity from the business; they absorb that complexity so the user does not have to.
