Two design systems, one product: merging OFX and Paytron
OFX, a global money transfer platform, acquired the fintech Paytron, and with it a second design system. As Design System Lead, I merged the two into one system for the web app, built on OFX’s brand: 400 design tokens, 33 components, 5 patterns and 12 screen templates.

- 2 → 1
- design systems merged after OFX acquired Paytron.
- 400
- design tokens: 217 primitives, 156 color tokens and 27 spacing tokens.
- 33
- components, plus 5 patterns and 12 screen templates, all built on the same tokens.
Problem and goal
After OFX acquired Paytron, the web app ran on two design systems with two different UI styles. The same patterns existed twice, and screens from the two sides didn’t look like one product.
The goal was one system for the whole web app: keep OFX’s UI direction and branding, bring over everything only Paytron had, and give designers and developers a single source of truth.
Key decisions
- A plan before the pixels. Before any design work, I presented the plan to the team and stakeholders: what the work would cover, which stages it would go through and what each stage would deliver. Everyone knew what was coming and when.
- Audit, then map every component. I audited both systems and mapped every component: what stays from OFX, what comes over from Paytron, what replaces an OFX component and what needs a redesign. OFX’s UI direction and branding stayed, but where Paytron’s version worked better for the product, it won. Fully outlined OFX inputs, for example, gave way to underline-only fields.
- Two layers of tokens. 217 primitives hold the raw values, and 156 color tokens give them meaning: background, text, border and states. Components use only the semantic layer, so Paytron components only had to be pointed at OFX’s semantic tokens to take on OFX’s look, instead of being repainted one by one.
- Three connected libraries. The system lives in three linked Figma files: Foundations, Components and Templates. Foundations feed components and components feed templates, so a change made in one place flows through the whole system.
- Same names in design and code. Developers rebuilt the system from scratch in Storybook. I worked with them so tokens and components carried the same names in Figma and in code, and we reviewed components together before they were released.

Primitives: the raw color values behind the system.

Color tokens give primitives a meaning, so components never use raw colors.

One button component, configured through properties instead of separate copies.

Every state designed and documented.
What I designed
- Foundations. 400 design tokens (217 primitives, 156 color tokens and 27 spacing tokens), typography, borders, elevation and effects, a grid, and assets: brand, illustrations, flags, payment methods and icons.
- Components and patterns. 33 components, from buttons, forms and tables to progress trackers and tooltips, each with its variants and states, plus 5 patterns: drawer, modal, navigation, sidebar navigation and widgets.
- Templates. 12 screen templates rebuilt on the merged components, including payments, creating a payment, the quote widget, budgets, onboarding, balances and recipients.
- Documentation. Detailed usage documentation for the most used components (buttons, dropdowns, forms and their fields, and tables), so designers and developers could use the system on their own.

Typography: every text style backed by tokens, so sizes and weights stay consistent.

Four elevation levels, from flat cards to dialogs.

The underline-only input that replaced OFX’s outlined fields, in all its states.

Alerts for success, warning, error and info, built on semantic color tokens.

File upload, from an empty drop zone to progress and errors.

Button documentation: anatomy, variants, sizes and states, each with a note on when to use it.

The dashboard template, assembled only from system components.

Treasury management: charts, cards and tables from the same library.

The quote widget, a template product teams reuse across flows.

Recipient details, built from the shared list and card components.

Balance transactions, using the system table with filters and statuses.
Impact
- The two design systems were fully merged into one, with OFX’s branding across the whole web app.
- Every Paytron component without an OFX equivalent was mapped and added, so no feature was left without a home.
- The system lives in Storybook as well as Figma, so design and code share one source of truth, reusable across the entire app.
- The design system is still in use today, on a platform used by over a million people in 180+ countries.
Next up
Explore more projects
- 01Trackable: one platform for dental marketing and patients
- 02Creator tools for Passion.io’s no-code app builder
- 03Clearer trading decisions on Avant Garde’s AI platform
- 04One app for charging Circle K company cars



