( 00-01 )
What I build
FlowPay is a checkout + admin console that keeps orders, payments, and refunds in one clean, traceable flow. Built to stay stable after launch, not just look good in a demo.
Core
Checkout flow: Cart → Payment → Confirmation with clear loading/empty/error states.
Order states: Pending / Paid / Failed / Refunded (no ambiguous “maybe paid”).
Admin orders: search, filters, detail view, status updates, notes, exports.
Append-only audit log: who changed what, when, and why.
Notification-ready templates: invoice + status updates (email/WhatsApp).
Support
Role-based access (Owner/Admin/Staff/Viewer).
Guardrails: confirmations + reason required for sensitive changes.
Not built
“Magic autopilot” payments.
Auto-refunds without review controls.
( 00-02 )
What Made It Hard
The hard part was keeping state consistent under real conditions: retries, double-clicks, weak networks, and admin actions happening in parallel.
Edge cases
Double-submit on checkout → idempotent updates + UI locking.
Mid-flow refresh/timeout → safe recovery without duplicates.
Refund/status edits without context → enforced reasons + full trail.
Engineering decisions
Strict state transitions + idempotency to prevent drift.
Append-only audit log with reason-required actions.
Anti-pattern avoided
Tracking changes in chats/spreadsheets instead of the system.
( 00-03 )
Why It Matters
Checkout is where confusion becomes real money problems. FlowPay makes operations clear, safe, and easy to maintain.
Clear order status reduces support back-and-forth.
Traceable changes speed up debugging and handoffs.
Guardrails prevent “quick edits” from becoming incidents.
Built with a maintain-first mindset, not ship-and-forget.
( 00-03 )
DISCOVER MORE
