The design system for Moment's payment gateway — three-tier tokens, a configurable brand system and a living Storybook that let one checkout wear DStv, Moment or any merchant's brand, on desktop and mobile web.
View the live Storybook ↗
The design system behind Moment's hosted checkout — tokens, components and brand themes, documented in a live, interactive Storybook.
The same checkout had to look like DStv, Moment or a merchant. Without a shared system, every brand meant restyling screens by hand and long design–dev back-and-forth.
A three-tier token architecture with one configurable brand variable, a component library in every size and state, and a Storybook both teams work from.
Desktop and mobile web shipped on one system, in light and dark, with brands switched by changing a single token.
Moment's payment gateway is white-labelled. The same checkout has to feel native to DStv, to Moment itself, and to the merchants who plug it into their own products — on a laptop and on a phone.
Before the system, each brand was a one-off. Designers restyled screens, engineers rebuilt them, and every new brand or edge case started another round of "which blue, which size, which state?"
The foundation is a three-tier token architecture. Each tier only talks to the one below it, so a change in one place flows everywhere.
--primitive-purple-700 or --primitive-green-800.--brand-primary-50, --content-success and --border-secondary.--button-success-default, --input-default, --card-background.The rules are simple: components use component tokens, component tokens reference semantic ones, only semantic tokens touch primitives — and nothing is ever hard-coded.

Brand colour runs through one variable, --brand-configurable-600. Point it at
--primitive-dstv-600, the Moment purple or the secondary blue, and every button and
brand element in the gateway updates instantly — no component changes, no rebuild.





Every token is also mapped for light and dark mode, so the same components read correctly whichever way a merchant's page is set.


Buttons carry checkout's most important moments — pay, continue, retry — so they got the most complete treatment:

Card details, phone numbers and amounts are where checkout succeeds or fails. Input fields use the same XS–XL sizing as buttons, so forms line up without exceptions, and a clear token hierarchy for feedback:
border-secondary, hover → border-tertiary, focus → border-focus with a ring, active → border-quaternary.
Type works like colour: named by role, not by size. Pre-defined styles combine font size, weight, line height and letter spacing into one class.
Each style ships as a copyable class such as typography-heading-1, so engineers
never have to translate a spec.

Four principles guide every decision: consistency, accessibility, flexibility and performance. All components target WCAG 2.1 AA — 4.5:1 contrast for text, 3:1 for large text, visible focus states and full keyboard navigation.
Usage rules sit right next to the components: one primary button per screen, destructive buttons only for irreversible actions, clear labels and the right input types on every field.

Instead of static specs, the system lives in an interactive Storybook that design and engineering share. Switch brand or mode and see every component update; copy a class or a token straight into code.
When a question comes up, the answer is a link, not a meeting.

The design system turned Moment's payment gateway from a set of hand-styled screens into a product that scales. Desktop and mobile web now build from the same foundation, and new brands arrive as configuration rather than redesign.
Change one token, rebrand the gateway.— The principle behind the system