01 / WEBSITE + ADMIN APPLIVE

HealthEdge Solutions

A 35-page marketing site, plus the admin app behind it: pay schedules, PayMongo payouts, encrypted bank details and three separate logins.

WEB APPPAYROLLCLOUDFLARE

VISIT THE SITE

Full-page capture of the HealthEdge Solutions homepage on desktop. — PUBLIC SITE · 35 PAGESLIVE CAPTURE

The HealthEdge admin dashboard: next payment date, active clients and employees, who is clocked in now and the estimated payroll, with demo data. — ADMIN APP · REAL UIDEMO STAFF · SANDBOX

Clearview, the payroll section: PayMongo wallet in sandbox mode, how funding works, top-up sources and the payment schedule. — PAYROLL & TRANSFERSSANDBOX

Upcoming payroll runs with demo employees selected and the Pay selected and Pay all buttons. — PAY SELECTED · PAY ALLDEMO NAMES

Timekeeping: who is clocked in, hours over the last 14 days and recorded shifts, with demo employees. — ATTENDANCEDEMO SHIFTS

The employee workspace for a demo employee, Jane Roe: a live clock-in timer, clock-out button and hours this week. — CLOCK IN · CLOCK OUTJANE ROE · DEMO EMPLOYEE

The same employee workspace on a phone, with the live timer and clock-out button. — SAME APP ON A PHONELIVE TIMER

WHAT IT IS

HealthEdge is a US healthcare-operations company whose team's pay gets set in seven currencies. The public site is 35 pre-rendered pages. Behind it sits the admin app, with a payroll section called Clearview where schedules get built, hours get clocked, and an admin hits Pay. All of it runs on one Cloudflare Worker and one D1 database, hand-built and lean.

WHAT I BUILT

Payroll schedules: weekly, biweekly, semimonthly, monthly, with the next pay date computed automatically.
PayMongo payouts: pay selected or pay all, one transfer per person, with a wallet-balance check before anything moves.
Webhook confirmation plus a 15-minute reconciliation cron so no transfer is left in limbo.
Rates, bonuses and deductions in seven currencies (PHP, USD, EUR, GBP, CAD, AUD, SGD), converted at the ECB rate stored the moment they're set.
Bank accounts encrypted with AES-GCM; the UI only ever sees the last four digits.
Job roles, organizations, bonuses and deductions, with an audit trail on admin edits.
Employee workspace: clock in and out with a live timer, 14-day history, avatar, payout account, address. A separate client login with its own workspace.
Three logins with signed HttpOnly cookies and rate limiting, PBKDF2 for employee and client passwords, plus Playwright scripts that click through the main flows.

THE HARD PART

Paying people exactly once.

Payouts are the one place where a retry is worse than a failure. Every transfer is idempotent, so a double-click or a dropped connection can't double-pay anyone. Webhooks aren't trusted on their own: each status gets re-verified against the PayMongo API before it's written down. And a cron sweeps open transfers every 15 minutes so anything that went quiet gets reconciled instead of forgotten.

STACK

CLOUDFLARE WORKERSD1CRON TRIGGERSPAYMONGOPLAYWRIGHTVANILLA JS