[email protected]

Money correctness
is a first-class invariant.

Below: the engineering and operational controls behind every wallet, every deposit address, and every withdrawal. We publish more detail than most platforms because security through obscurity isn't a strategy we believe in.

How the wallet works.

Every user has a dedicated wallet row. The wallet's balance is not authoritative on its own — it is reconstructed and verified against an append-only ledger of credit/debit transactions where every row stores balance-before, balance-after, amount, and direction.

Investments, deposits, plan subscriptions, and withdrawals all flow through a single service (WalletService) which wraps the write in a DB transaction and a row-level lock. Concurrent writes are serialised at the database level; you cannot double-spend a wallet balance even under racing requests.

Reconciliation is continuous. A scheduled job recomputes wallet balances from the ledger and surfaces any drift. To date, the system has zero recorded reconciliation discrepancies.

wallet_transactions
├── user_id
├── wallet_id
├── type           (deposit | withdrawal | investment | …)
├── direction      (credit | debit)
├── amount         DECIMAL(18,8)
├── balance_before DECIMAL(18,8)
├── balance_after  DECIMAL(18,8)
├── reference      UNIQUE
├── status         (pending | completed | failed | reversed)
└── created_at, metadata

Every wallet write produces exactly one row. Reads recompute balance = sum(credits) − sum(debits) and reconcile against wallets.balance.

Per-deposit HD addresses, expiring windows.

01

User opens a deposit

A fresh address is derived from the chain's master xpub at the next HD index. The address has never been used and will never be reused.

02

Address registered with Tatum

We subscribe to incoming-transaction notifications for that specific address. The webhook URL contains a secret token in the path; requests with the wrong token return 403.

03

User sends funds

They have 30 minutes to broadcast. The page shows a countdown and polls the backend every 10 seconds.

04

Webhook fires

Tatum POSTs to our webhook with the address, amount, and tx hash. We verify the URL token, then independently fetch the transaction from Tatum to confirm it actually happened (defence in depth).

05

Credit

The wallet is credited atomically via WalletService. The deposit address is marked confirmed. The Tatum subscription is unsubscribed to stop incurring notification load.

06

Expiry

If the user does not send within 30 minutes, the address is marked expired (sweep job runs every 5 minutes). Late-arriving funds require manual recovery.

Two-factor authentication

TOTP via authenticator app. 8 recovery codes generated at enable-time, encrypted at rest, single-use. Mandatory for admin accounts. Strongly recommended for investors. Configure at /investor/2fa.

KYC verification

Identity verified once across all providers. Government ID + selfie standard; proof of address + source-of-funds for enhanced due diligence above thresholds in our AML policy. Daily screening against OFAC, HMT, EU, and UN sanctions lists.

Anti-fraud controls

Withdrawals require prior investment activity. Admin review on every withdrawal. Two-person rule above high-value threshold. Velocity checks for unusual patterns. Provider-side review for unusual fund-flow signatures.

Independent review, on schedule.

Annual

Big Four firm — full balance and process audit, year-end.

Biannual

External penetration tests by independent security firms.

Ongoing

SOC 2 Type II controls. Report on request to institutional clients.

Continuous

Wallet reconciliation job runs daily; any drift triggers an internal alert.

Biannual

Transparency report published twice yearly: complaint volumes, regulatory correspondence, material outages.

On demand

Independent board oversight on regulatory matters and material business decisions.

If something goes wrong.

Our incident-response process is documented and rehearsed. Material incidents are disclosed within 24 hours via an in-app banner and an email to affected users.

Where the incident is regulatory, we notify the relevant authority per applicable law. Where the incident involves a breach of personal data, notification follows the cadence required by GDPR / UK GDPR / equivalent local law.

The biannual transparency report enumerates material incidents and our response, including root cause and remediation.

We operate a coordinated vulnerability disclosure programme. Email [email protected] with details. We acknowledge within 24 hours and aim to remediate critical findings within 7 days. We do not currently operate a paid bug bounty but credit researchers publicly with their consent.

Do not publicly disclose vulnerabilities before our remediation timeline; doing so puts users at risk and may forfeit credit / future engagement.

Have questions?

For institutional security due-diligence requests, contact our team.

Contact Security