Security you can inspect, not just read about
Every sensitive action is authenticated, authorised, validated and logged. This page describes what is enforced in the platform, and what a production deployment would add on top.
Controls in force
Authentication
Password hashing handled by the platform, with optional TOTP two-factor and single-use recovery codes issued at setup.
Authorisation
Every customer route resolves the signed-in user to their own customer record. Ownership is checked on read and on write.
CSRF protection
All state changes are POST requests carrying a single-use nonce. A forged request fails before it reaches business logic.
Input validation
Amounts are parsed as integers in minor units. Anything that is not a plain decimal is rejected rather than coerced.
Audit logging
Logins, transfers, card changes, profile edits and admin actions are appended with actor, IP and timestamp.
Session handling
Sessions expire. Any device can be revoked. Administrative areas are separate from the customer area.
A ledger that refuses to be wrong
Double-entry is not decoration. Balances are derived from balanced postings, transfers lock the account row before reading it, and a partial write rolls back completely. If the two sides do not sum to zero, nothing is stored.
- Atomic postingsDebit and credit are written in one database transaction, or not at all.
- Row lockingConcurrent payments against one account serialise, so a stale balance cannot authorise a second debit.
- Invariant checkA reconciliation routine proves the sum of all ledger entries is zero and reports the result.
Account security
ProtectedLast sign-in today, 09:12 · San Francisco, US
What this build does and does not claim
Being precise about the boundary is part of taking security seriously.
| Money movement | Double-entry ledger with atomic postings | Balances derived from postings, never stored |
|---|---|---|
| Identity checks | Document upload and manual review | Accredited KYC/AML provider with sanctions screening |
| Account access | Two-factor authentication on every account | Session controls and login alerts |
| Card security | Freeze and unfreeze instantly | Spend limits and per-card controls |
| Infrastructure | Hardened hosting | Segregated environments, WAF, monitored backups |
Found something? Tell us first.
We welcome reports from researchers and will credit responsible disclosure if you would like us to.