Tournament registration & bracket API
Table Tennis Backend
Express + MongoDB API for player registration, payment-proof upload, referral/cashback fields, tournament ops, and knockout brackets (Vercel entrypoint).
The challenge
Tournament organizers needed API-backed registration with capacity/fees, admin approval tied to payment status, referral incentives, and bracket/match endpoints—without a card processor in this repository. Without a coherent tournament registration & bracket api foundation, Table Tennis Backend stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The solution
Table Tennis Backend: Express + MongoDB API for player registration, payment-proof upload, referral/cashback fields, tournament ops, and knockout brackets (Vercel entrypoint). API foundation for tournament registration and admin ops. Tekvers delivered a maintainable tournament registration & bracket api system for Table Tennis Backend using Node.js, Express 4, Mongoose 7, MongoDB, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Approach
Registration-first domain
Players, tournaments, registrations, matches, and brackets are first-class Mongoose models with admin approval gates.
Proof-based payment
Method selection + file upload + status fields—explicitly **not** a card gateway integration.
Deploy duality
Documented CORS and mounted-route differences between local and Vercel entrypoints so ops do not assume identical surfaces.
Deliverables
- ▸Express REST API (`tabletennis-backend`) with JWT/bcrypt
- ▸User registration, referral validation, and cashback field updates
- ▸Tournament CRUD and capacity/fee/prize modeling
- ▸Match scoring and knockout bracket generation/advancement
- ▸Multer payment-proof upload on user routes
- ▸Vercel serverless entry plus local `server.js`
- ▸Ad-hoc test scripts (no formal automated suite)
Outcomes
- ▸API foundation for tournament registration and admin ops
- ▸Referral and cashback tracking fields in registration flows
- ▸Bracket and match endpoints for knockout play
- ▸Deploy path to Vercel against MongoDB Atlas-style hosting (hostnames in CORS/deploy docs)
Impact
Organizers can run registration → payment-proof → approval → brackets from one Express API—Tekvers kept claims accurate: no frontend in this checkout, no card processor, proof-upload payments only.
Tech stack
Want something similar?
I build production systems like Table Tennis Backend—from architecture through launch. Tell me what you need.
Contact me →