CASE FILE 03PlatformLIVE
NeoPoints
Multi-tenant driver loyalty
A live loyalty program in two fleet parks where drivers earn points on real orders, climb ranks and redeem gifts, with every balance traceable to its ledger entries.
- Role
- Product and systems engineer
- Stack
- Next.js 16 · React 19 · TypeScript · PostgreSQL
NeoPoints is built around a balanced, append-only ledger and strict park boundaries. Each park has its own hosts, membership, wallet and activation; identity and SMS codes come from YPay, Yandex Fleet data arrives through a shared Fleet service, and support stays in YDesk.
- Contribution
- Designed and built the points economy, ledger, tenant model, gift catalogue, gamification, admin workspaces, YPay and Fleet integrations, and release pipeline.
- Constraints
- Points carry real value, so every balance must reconcile to journal entries, parks must never see each other's data, and other systems' records stay behind signed APIs.
What was built
- Next.js 16 and React 19 app with web, worker, order-board and Fleet processes on PostgreSQL, with jobs and outbox kept in the database.
- Points from qualifying completed orders, recorded as immutable, balanced journal entries with audited admin adjustments.
- Gift catalogue with stock reservations and Telegram order notifications, plus ranks, missions, seasons, leaderboards, 2x campaigns and public order tournaments.
- HMAC-signed internal APIs to YPay for identity, SMS one-time codes and challenge rewards; installable PWA in Georgian, English and Russian.
Stack
- Next.js 16
- React 19
- TypeScript
- PostgreSQL
- Yandex Fleet
- YPay
- Telegram
- PWA