SECURITY
Built for control, visibility, and mature support.
Security language should stay clear and measured. Users need to understand what is protected, what they can review, and where support begins when something needs attention.
PRINCIPLES
A serious product surface starts with product discipline.
Good security communication avoids exaggeration. It gives users clear expectations, useful controls, and visible status.
Clear balances
Users should always understand what they hold, what is available to spend, and which actions are supported.
Visible transaction status
Quotes, payments, and wallet actions should communicate progress, completion, and availability without ambiguity.
Support by design
Recovery and support guidance should be easy to find, written calmly, and grounded in real operational paths.
WALLET AND TRANSACTION SAFETY
Clear guidance around account, payments, and recovery.
The interface should help users understand sensitive actions without forcing them to decipher technical detail.
Account protection
Use strong credentials, supported recovery methods, and clear device hygiene. Sensitive actions should be easy to review before approval.
Transaction visibility
Balances, confirmations, and pending states should be visible without reading through dense technical detail.
Support and recovery
When something goes wrong, users need clear escalation paths, identity checks where required, and transparent timing expectations.
SUPPORT AND DISCLOSURE
Availability depends on region, account status, and supported routes.
This v1 intentionally avoids making claims beyond what the product can support. Users should see availability, confirmation states, and support next steps before taking action.
Risk and availability disclosure
Wallet features, supported payment methods, and swap availability may vary by region, account requirements, and supported infrastructure. The product should say so directly.
Recovery and support route
Support should verify identity where required, communicate timing clearly, and avoid making guarantees the system cannot keep.
SUPPORTER-READY V1
Start with one balance.
Supporter v1 keeps the scope credible: prepaid credits, visible ledger activity, and EarnRM redemption into real usage rights.