Architecture
A clean boundary between review and settlement.
Ship a review surface first, then wire settlement. It stays operator-friendly and audit-friendly as the backend evolves.
Auth
Signed wallet challenge creates a short-lived session
Review
Totals + exceptions computed consistently
Receipts
Map outcomes back to rows (tx id, confirmation)
Diagram is simplified on purpose—enough detail for reviewers, without a wall of text.
What matters
Less UI. More certainty.
User-facing clarity, with just enough technical specificity to feel credible.
Row-level validation
Built-in
Run totals
Deterministic
Receipts
Planned
Execution
Next layer
Workflow
Three states. No extra screens.
Compose → review → execute. Keep the operator loop tight.
Create
Draft invoices or payout rows via form or CSV, with inline validation before anything moves.
Approve
Review totals + exceptions and lock intent (who, what, how much) before settlement.
Reconcile
Attach outcomes (tx id + confirmations) back to rows so ops can audit without guesswork.