CLUE
A tutoring marketplace for IB, IGCSE and A-Level students — bookings, credits and teacher payouts in one place.
Illustrative entries. 1 credit = ₹10.
The problem
Three balances. One booking. No room for drift.
A student pays. A teacher teaches. The platform keeps a fee. Every booking touches three balances, and they have to move together — or not at all.
I built CLUE as a ledger first and a marketplace second: a credit engine where 1 credit = ₹10, and every movement is written once, atomically, to all three books.
How it works
Follow one rupee through the books.
- 01 Pay
- 02 Verify
- 03 Book
- 04 Settle
Illustrative amounts. Scroll to post the entries.
The fine print
The boring parts, done properly.
Three payment webhooks
Razorpay, Stripe and PhonePe all call back. Each payload is checked against its signature before a single credit moves.
- Razorpay✓
- Stripe✓
- PhonePe✓
A referral loop that previews well
Peer-to-peer referrals, shared as links with Open Graph previews, so an invite looks like an invite.
250 lines of security rules
Firestore rules decide who can read which booking and which ledger. Clients never write a balance.
// illustrative shape
match /ledgers/{uid}/entries/{id} {
allow read: if isOwner(uid) || isAdmin();
allow write: if false; // server only
}
Accounts
What’s in the books.
- Portal
- Next.js, for students and teachers
- Admin
- A console for the team running the marketplace
- Back end
- Node 22 Cloud Functions, Mumbai region
- Data
- Firestore, guarded by 250 lines of rules
- Money
- Razorpay, Stripe, PhonePe
Receipts
Filed under CLUE.



Stack, itemised.
Built at PLXN World as the sole developer. Ask me how the credit engine stays atomic.