Security at Timebank isn't a page on a marketing site โ it's the database engine itself. Row-level locks, idempotency keys and two-entry ledgers mean money behaves predictably even when networks don't.
Every transfer writes two ledger entries โ one debit, one credit, each stamped with balance before and balance after. Reconcile any wallet, on any day, down to the paisa.
Both wallets are locked deterministically โ lowest ID first โ before any balance change. Two concurrent transfers can't race each other into a negative balance.
Every send carries a unique key generated client-side. Retry on bad Wi-Fi and you get the same receipt back โ not a duplicate transfer.
One debit row, one credit row โ each carrying balance before, balance after. The whole wallet can be reconstructed by replaying its rows.
RLS policies gate every read and write to your own wallet. Money moves only through audited RPCs โ never raw table updates from the client.
Live QR tokens rotate every 60 seconds. A screenshot from yesterday won't drain your wallet today.
Per-wallet send velocity is capped and visible. Anomalies โ sudden bursts, unusual recipients โ trigger a hold the user can release in-app.