How to build a token architecture for financial products that ship on web, iOS, Android, and email — all from one source of truth.
A fintech product's colors appear in web apps, native mobile apps, transactional emails, and PDF statements. Each platform has different color rendering. Define tokens in a platform-agnostic format (JSON) and transform them for each target: CSS custom properties for web, Swift/Kotlin constants for native, and inline styles for email. ColorArchive exports in all major formats to bootstrap this pipeline.
Financial products need more semantic states than typical SaaS: positive, negative, pending, processing, failed, cancelled, and informational. Each needs a foreground, background, and border variant. Structure these under a feedback namespace in your tokens — feedback.positive.fg, feedback.positive.bg, feedback.positive.border — so they don't collide with your brand color namespace.
In regulated industries, color changes can affect compliance. Version your token files with semantic versioning and require design team approval for major changes. ColorArchive's token export includes metadata comments so reviewers can see the source palette and contrast ratios at a glance. Store tokens in a shared package that all platform teams consume as a dependency.
Move from the guide into a concrete palette lane
Guides explain the use case. Collections prove the taste. Packs handle the export and implementation layer.
