Industry

Fintech / Payments / White-label SaaS

Client

Computop

Payment page alignment. Designing for scale, not just for now

Situation

One designer, multiple diverging templates

Following an acquisition, Computop became part of a major European payment group. Our payment page templates had grown organically into multiple coexisting variants, each with its own technical constraints, client dependencies, and maintenance cost. As the sole designer, every template variant meant separate decisions, separate documentation, separate development effort.

Task

A customization brief hiding a strategic window

The brief was to create a white-label version of our card payment page for our new parent company, a contained customization request. I saw a larger opportunity in it.

Action

Making the case before anyone asked

Working directly with the parent company's team, which included a full design function and dedicated UX researchers, I noticed their template was simply better than ours. More refined, better researched, evolved by a larger team over time. I brought a case to my manager unprompted: align our payment pages to theirs and inherit their design investment for free. Every improvement they make benefits us automatically. Every piece of UX research they conduct applies to our product at zero cost. Future changes get implemented once, not across diverging parallel templates. My manager took it to the CEO. It became a formal requirement ticket. I am now working with our front-end developer to map the structural and component-level differences and define an implementation path that minimises disruption to existing merchant integrations.

Result

One template system, zero parallel maintenance

Project in active progress. The outcome is a unified payment page template system: one structural foundation, white-label flexible, maintained in alignment with the parent company's design evolution. This eliminates the long-term cost of parallel template maintenance and removes a compounding source of design and development overhead for a one-person design function.