Why should you care?

PostgresVerse core banking demo shows double-entry rules auditors expect before real RBI sandbox integration.

See it live — copy this example

Run in pgAdmin or psql.

CREATE SCHEMA core;
CREATE TABLE core.accounts (
  account_id bigserial PRIMARY KEY,
  customer_id bigint NOT NULL,
  balance numeric(14,2) NOT NULL CHECK (balance >= 0)
);
CREATE TABLE core.transfers (
  transfer_id uuid PRIMARY KEY,
  from_account bigint REFERENCES core.accounts(account_id),
  to_account bigint REFERENCES core.accounts(account_id),
  amount numeric(14,2) CHECK (amount > 0),
  status text DEFAULT 'completed'
);

What happened?

• Accounts hold non-negative balances.
• transfers link two accounts with UUID idempotency key.
• App wraps debit/credit ledger inserts in one transaction.

Practice next

1. Create schema and tables in PostgresVerse.
2. BEGIN transfer between two accounts with balance check.
3. Verify SUM ledger zero-sum per transfer_id.
4. SELECT FOR UPDATE on accounts during transfer.
5. Report daily SUM(amount) GROUP BY status.

Remember

Double-entry or paired debit/credit lines. UUID transfer_id for idempotent retries. numeric(14,2) for rupee precision.

PostgresVerse neobank demo

Hackathon judges test concurrent transfers; constraints prevent negative balance.

Outcome: Team wins best data integrity track.