Skip to main content
The payments portal exposes a number of design tokens which we can customise to suit the branding needs of your application. Under the hood, these are set as CSS variables and piped into Tailwind CSS for use in our components.
To create or edit your theme, reach out to your Axle representative. For new clients, we’ll action this as part of your onboarding.

Design tokens

All tokens are optional. Unset tokens fall back to our default theme.

Colour tokens

Colours are expressed as CSS colour strings. The codebase prefers OKLCH for perceptual uniformity, but hex and HSL are also supported. Tokens are organised into base/foreground pairs. The base token (e.g. --primary) controls a surface colour, and its matching -foreground token (e.g. --primary-foreground) controls the text and icon colour that sits on that surface. Set them together so that content remains legible against each surface.

Brand

Surfaces

Feedback

Borders & focus

Radius

A single --radius value drives the entire corner-radius scale. The derived values --radius-sm, --radius-md, --radius-lg, --radius-xl, and --radius-2xl are all calculated from --radius, so components scale proportionally — set the base value and everything from inputs to cards to sheets stays in tune.

Typography

Font customisation

We support three font strategies.

1. External fonts

We support the use of Google Fonts for externally hosted, publicly licensed fonts.

2. Local fonts

We support the use of custom fonts. You can provide us with font files, which we host alongside the embed. Themes that rely on brand fonts typically use this path, with one or more weights defined and preload enabled for primary weights.
When using custom fonts, make sure you have the licences needed to use them in the app.

3. System fonts

Themes may also choose not to ship any font files, instead using a system font stack.