Familiar like fintech
Use clear cards, fast actions, readable status, activity feeds, and strong visual hierarchy to reduce friction.
Brand manual
Mature fintech UX, open-protocol language.
AirPay should feel simple, reliable, and fast like a modern financial app, while always communicating that it is a self-custody wallet and an offline-promise protocol with deferred clearing.
Principles
Defensible as protocol
The interface must explain signed promises, reserve capacity, and later clearing without suggesting a financial account.
Open as ecosystem
The brand should invite builders, local operators, Solana developers, and communities to reproduce, audit, and extend the protocol.
Visual system
Clean surfaces, strong accent, explicit risk signals.
The UI may use familiar financial-app patterns: white cards, a strong CTA, summary areas, and visible states. The meaning, however, stays anchored to the protocol.
Protocol green
#0E6F3B
primary action, ready state, brand
Continuity lime
#B8F35A
energy, highlight, CTA
Audit cyan
#0E9FA5
sync, claim, technical trail
Reserve amber
#B77905
capacity, caution, reserve
Risk coral
#D94A3A
block, quarantine, risk
Shell white
#F8FAF5
clean background, reading area
Use
self-custody walletlocal profilereserve capacityoffline promisedeferred clearinguser signingaudit trailopen ecosystem
Avoid
bankbank accountdepositwithdrawalguaranteed balanceoffline moneyguaranteed redemptionmainnet live
UX rules
Make it feel easy. Do not make it sound like a bank.
The visual layer can reduce anxiety with known patterns; the semantic layer must keep every action inside the domain of wallet, signature, promise, reserve, and sync.
Show confirmed SOL as an on-chain asset, not as a bank balance.
Show OffAir as promise capacity, not as available money.
Use actions such as add capacity, release capacity, and create commitment.
Use timeline and feed for receipts, claims, and sync instead of bank statement framing.
Show risk and readiness before the action, not only after an error.
Keep community language visible: protocol, operators, builders, devices, and peers.
Community and ecosystem
The brand should invite contribution, not only conversion.
Builder-ready
Documentation, demos, and public code should let another person run the MVP and understand the promise lifecycle.
Local operators
Communication should speak to people operating in events, field work, markets, campuses, and unstable connectivity.
Protocol contributors
The brand should make contribution areas clear: wallet, local transport, trust policy, journals, and Solana contracts.