2025Full-Stack Web App

PayUp

A group expense tracker that calculates one net balance per person, with live tab updates and camera receipt scanning.

One balance replaces messy group debts, and receipt photos turn into itemized bills instantly.

GoGinPostgreSQLsqlcReact 19TypeScriptTailwind CSSNeonDB
PayUp overview
My role
  1. 01Designed a shared ledger that nets each member's balance against the group, recording settlements as transfers to keep history intact.
  2. 02Synced active balances across open tabs in real time, so any added bill or approved payment updates everyone's phone immediately.
  3. 03Added receipt scanning using visual OCR to parse items and totals from photos into draft expenses, skipping manual typing.
  4. 04Built the backend in Go and PostgreSQL with sqlc for compile-checked queries and predictable financial transactions.
  5. 05Secured accounts with encrypted sessions, password protection, and API rate limits.
  6. 06Built a responsive mobile interface with fast expense entry and instant screen updates.
Details

The shipped client, running against seeded data. Add an expense and the balances move; approve a settlement and they move back.

One net position per person, with the group total and your share.
Reminders stay collapsed until tapped; the message is one tap away.
Manual entry, an even split, or a scanned receipt.

Captured from the running client at 360×740.

PayUp architecture: a React PWA talking to a Go API over HTTPS, with Server-Sent Events pushing balance updates back, and the API proxying Postgres, Gemini OCR, object storage and Web Push.React 19 PWATanStack Querysession-scoped JWTinstallable, offline shellGo · GinJWT HS256 + rotationbcrypt passwords4 rate-limit tiersper-group SSE hubGemini OCR proxyproof uploadsPostgresNeon · sqlc12 goose migrationsGeminireceipt → itemsStorage · PushCloudinaryWeb Push (VAPID)HTTPS /v1SSE · event streampgxserver keysigned

System topology. The API is the only component holding credentials, which is why OCR and uploads go through it.

Ledger model: each expense credits whoever paid and debits each split, so a member ends up with one net number. In the worked example A is owed 500, B owes 100 and C owes 400; two transfers clear the group.ExpensesNet positionA paid ₱1,200split ₱400 each+500.00B paid ₱600split ₱200 each−100.00C paid ₱300split ₱100 each−400.00Each member holds one number. The set always sums to zero.Cleared by two transfers:B → A ₱100 · C → A ₱400

The ledger model behind the balance screen, worked through with three members and three expenses.