Technical controls protecting financial records, ledger integrity, and public attestations.
System transactions generate a versioned canonical payload and a cryptographically secure 256-bit random salt. The resulting SHA-256 hash is published to XRPL testnet. The salt and private event payload remain stored safely in internal encrypted storage.
All financial operations are governed by an append-only double-entry ledger database schema. Total debits MUST equal total credits for every posting, preventing silent balance drift or tampering.
Endpoints require strict Zod schema validation, CORS allowlists, HTTP security headers via Fastify Helmet, idempotency key hashing for mutation endpoints, and mandatory bearer tokens (OIDC/JWKS).
The staging environment operates strictly with mock consumer data, synthetic credit scores, and test accounts. Real SSNs, bank credentials, or consumer debt records are strictly prohibited in development and staging.