Trust, with clear boundaries
Trust begins with transparency.
Know what exists, what is simulated, and what still needs to be built. This is a development preview, not a live financial service.
Our boundary today
No real funds. No wallet connection.
No audits, certifications, regulatory approval, or production readiness are claimed.
Protections in the verified application
Protected local accounts
The verified application uses hashed passphrases, protected session cookies, and request-origin checks.
Clear merchant boundaries
Merchant access is scoped. Account isolation and permission checks protect access to simulated records.
Predictable retries
Repeated requests retain their identity. An uncertain response should not create a second payment.
Evidence without settlement
Read-only Devnet observation is separate from simulated payments. It cannot sign or transfer funds.
A preview with honest limits.
- This interactive review stores fictional examples only in this browser tab, with a 24-hour retention limit.
- Login is unavailable. No credentials are collected; merchant selection is a fictional demonstration.
- Local links are not payment instructions. Simulated receipts are not proof of payment.
Further work is essential.
- Independent security review and adversarial testing.
- Production identity, account recovery, operational controls, and monitoring.
- Legal, regulatory, and financial requirements for any proposed live service.
Explore the experience safely.
Keep all accounts, amounts, and descriptions fictional.