A padel super app for Pakistan, where a court can only ever be sold once.
Hassan is the lead full-stack engineer, through Xeltec, and its primary committer: 139 of 206 backend commits and 151 of 167 on mobile.
- Client
- PadleX
- Sector
- Sports booking
- Scope
- FastAPI · Flutter · Payments
- Live at
- Behind a login

ProofPadleX
Pakistan's padel players wanted one app for the whole game: finding and paying for a court, joining open matches and tournaments, booking coaching, and seeing where they rank. The courts' owners needed the other side of it.
That a court slot paid for with real money is taken once: locked, paid, checked in, and played, with nothing in between left to chance.
Four parts built to one contract: a player app and a facility-owner app in Flutter, an admin panel in Next.js, and a FastAPI backend of 31 modules.
- 01
The booking core
lock(slot) → pay → check_inAtomic slot locking in Redis Lua, feeding a lock, pay, check-in, and result lifecycle, so no court is sold twice.
- 02
Five ways to pay
pay(provider)PayFast, Stripe, EasyPaisa, JazzCash, and SadaPay behind one pluggable interface.
- 03
The money audit
audit(money)Led the security and money audit: fixed a P0 payment bypass and an OAuth role escalation, and moved every amount to integer minor units.
- 04
Tests & releases
pytest --cov 70%1,873 backend tests behind a 70% coverage gate, with iOS TestFlight and Play Store release engineering.
Next came Maidaan, PadleX's multi-sport evolution: padel, badminton, table tennis, futsal, and cricket from a config-driven sport registry instead of code forks, with every phase gated on the padel regression suite.
Figures
fig. 2, a sketch
Taking bookings for Pakistan's padel players, today.
Next exhibit · HHealthcare
Concierge


