The Universal Money Address (UMA) open-source standard combines human-readable Lightning Addresses and enhanced messaging services with the Lightning Network’s real-time, global payment rails to make sending money as easy as sending an email. It connects regulated financial institutions and payments providers across borders and uses the Bitcoin’s Lightning Network for global settlement with messaging to support endpoints in any currency.
Design Analysis
This design language explains a payment-address protocol through large, simple visual objects. The interface should feel open, trustworthy, and obvious: a white canvas, bold address syntax, blue verification marks, round...
This design language explains a payment-address protocol through large, simple visual objects. The interface should feel open, trustworthy, and obvious: a white canvas, bold address syntax, blue verification marks, rounded payment calculators, and green certainty signals. Use one dominant object per screen. A giant address, a rate calculator, or a wallet card should do more work than a grid of marketing cards.
Use F9F9F9 as the primary canvas and 16171A for text and address syntax. Use 0068C9 as the verification/action color: CTAs, brackets, links, and active protocol marks. Use 35C84A only for checks and transfer-success states. Use EDEDED for calculator shells and quiet controls, and white for input fields and raised cards. Dark sections can use a near-black surface when the page needs an enterprise or wallet-stage moment.
Use a Manrope-style geometric sans. Main headlines can be large and heavy, around 64px / 72px or 56px / 56px, because the system is sparse. Section headings sit around 48px / 60px; explanatory copy can be 20px / 30px. Use uppercase spaced labels for protocol annotations, but keep them small. Do not let labels become the main hierarchy.
Use broad whitespace and contained widths. Homepage-style pages should center a single address diagram. Product pages can split into a two-column layout: benefit copy on the left and a calculator or wallet card on the right. Use bracket frames and labels to explain address parts. Use rounded panels for calculators and payment objects. Dark hero sections should be reserved for business-facing emphasis, not used as the default.
Core identity and authoring metadata from the refto.one design model.
A minimal payment-address design language with oversized address syntax, blue verification marks, rounded calculators, and optional dark business-stage moments.
Clear, protocol-like, trustworthy, and open, with bold typography and very little decorative noise.
Fields outside the primary renderer remain visible here as structured fallback content.
Primitive palettes and resolved token colors for the active preview mode.
Spacing scales rendered as tokens with a simple length specimen.
Corner radii tokens with a live surface sample.
Font families from the current design YAML, including fallback stacks and usage character.
Top-level typography scale rendered as live text specimens.
Top-level typography line-height values from the design YAML.
| Property | Value |
|---|---|
hero | 72px |
product_hero | 56px |
section_title | 60px |
subhead | 30px |
body | 30px |
control | 20px |
Top-level typography weights from the design YAML.
| Property | Value |
|---|---|
display | 800 |
title | 700 |
control | 700 |
body | 500 |
Fields outside the primary renderer remain visible here as structured fallback content.
Border tokens with resolved values.
Shadow tokens with resolved values and shadow samples where applicable.
Motion tokens rendered as resolved values for timing and personality.
Resolved border token values.
| Property | Value |
|---|---|
blue | 2px solid #0068C9 |
hairline | 1px solid rgba(22, 23, 26, 0.12) |
white | 1px solid rgba(255, 255, 255, 0.18) |
Resolved shadow token values.
| Property | Value |
|---|---|
none | none |
card_soft | 0 16px 40px rgba(22, 23, 26, 0.10) |
wallet | 0 28px 80px rgba(0, 0, 0, 0.32) |
Resolved motion token values.
| Property | Value |
|---|---|
duration_fast | 160ms |
duration_base | 220ms |
easing | cubic-bezier(.2, 0, 0, 1) |
Low-complexity component tokens rendered as design-system specimens.
Schema-agnostic optional blocks from the design YAML. New option keys render here automatically.
Schema-agnostic optional blocks from the design YAML. New option keys render here automatically.
Compact list of patterns the design system explicitly avoids.