VecnetBuild Spec for Dropout Capital

An orchestration, reconciliation & settlement layer over two payment rails — a Tonder-derived double-entry finances engine, rebuilt on Supabase/Postgres.

Start with the architecture

The big shift (§4)

Build phases (M1–M8)

🔌

Acquirer-as-plugin

Tonder (online/CNP) and Menta (in-person/CP) are two rails behind one abstraction. A third rail is a row + a Listener adapter — no schema or core-flow change.

🧮

Double-entry on Postgres

One atomic transaction replaces Tonder's FIFO queue + ADD operator + version counter. Balance integrity is enforced, not warned about.

🧾

14-table data model

accounts, journals, ledger_entries, fee_rules, transactions and the operator registry — keyed on one correlation ID per transaction.

💸

Finances flows, ported

Orchestrator, fees, posting, settlements, rolling reserve, daily ledger and the T+0/T+1/T+2 cycle engine — Tonder's semantics, Supabase plumbing.

📊

Three surfaces

Merchant Dashboard (RLS-scoped), the 11-module Vecnet Admin operator platform, and the payer-facing Hosted Checkout.

🛡️

Out of PCI scope

Card capture is delegated to the Tonder Lite SDK v2.0 + Skyflow tokenization. Vecnet stores tokens only — never a raw PAN.

What this site is

This is the executable form of the Vecnet master build spec (v0.1). The original 1,199-line document is reorganized into focused pages, and ~16 diagrams are added (architecture, full ERD, per-flow sequence diagrams, the settlement cycle model, and the M1–M8 milestone map) so the engineering team can build against it directly.

Source of truth: VECNET_BUILD_SPEC_for_Dropout_Capital (2).md. Where this site conflicts with the architecture PDF or vecnet_citizen_flow.mmd, the build spec wins.

Two load-bearing principles

Acquirer-as-plugin — the finances engine treats each rail as an ACQUIRER entity. Adding a rail must never require schema or core-flow changes.
One correlation ID per transaction — every payment carries a single correlation ID from the rail notification, through the Listener, into the journal, the ledger entries, and the settlement record. It is the thread that makes reconciliation tractable.

Hard constraint: Vecnet does not use MongoDB or DynamoDB. The entire data layer is Supabase (Postgres). Tonder's finances engine is the blueprint; the storage and eventing primitives are replaced.