Computop · Fintech / Payments
Unified Merchant Customization Descriptor: Connecting two isolated workstreams into a shared product architecture before either locked its foundation.
Situation
Solo designer, full product surface
Computop's Merchant Portal is a white-label payment platform serving banks and merchants across Europe. As the sole designer, I own the entire product surface: UX, UI, documentation, and cross-functional alignment, with no design system team, no researcher, and no design manager.
Task
A contained brief with a larger problem inside
A PM brought me a contained brief: add basic email branding to the Pay by Link flow. Logo, header color, button color. Scoped, funded, and ready to move.
Action
Connecting two isolated workstreams
While mapping the problem I identified a parallel workstream: a different PM, different brief, different timeline, designing a visual editor for the payment page itself. Two features, built in isolation, solving the same underlying merchant need: "I want my payment experience to reflect my brand."
I flagged the overlap to my PM, reached out directly to the second PM, and got them on a call. A full merge wasn't possible: separate funding, separate timelines. But we agreed on something concrete: I would design the email personalization feature with future convergence in mind, laying an architectural foundation the visual editor could eventually connect to without either project being rebuilt.
The structural decisions: shared customization logic, compatible UI patterns, aligned settings architecture, were documented and communicated to both PMs and engineering.
Result
Foundation for a unified customization system
Both features are in active development on separate tracks. The foundation is in place for a unified merchant customization system: one place to define brand, propagating consistently across every customer-facing touchpoint. For a white-label product serving multiple client tiers, this reduces future design and development overhead on every customization request that follows.