I’m putting together a production-ready membership platform and need a developer who can take it from architecture to deployment. Membership Engine First priority is bullet-proof form validation. Every registration step must fail gracefully and surface clear messages, whether the user is uploading a photo, scanning an Aadhaar, or submitting personal details. Once validated, each member receives an auto-generated code whose uniqueness is guaranteed—not just “very unlikely to collide,” but mathematically collision-free across time. Payment Gateway Razorpay is the processor of choice. The integration already exists in sandbox, but I need rock-solid callback logic that records only confirmed transactions, handles retries idempotently, and verifies every signature sent from Razorpay before updating our ledgers. Commission Split After a successful payment the amount is divided across five levels—Block, Dist, State, Kosh, and Total. The split percentage is already mapped out; what’s needed is an easily editable rules engine so I can tweak the percentages without code changes. All calculations must be accurate to the paisa and fully auditable. Multi-Level Admin Two roles to start: Super Admin and District Admin. Each view and every endpoint must respect role-based access, keeping district data siloed while allowing the Super Admin global oversight. Analytical Dashboard Charts built with Chart.js will show real-time stats filtered by district, date range, and payment status. I expect clean, reusable components and lazy-loaded data for performance. Payout & History Every transaction moves through a status flow—initiated, paid, UTR posted, acknowledged. I need a searchable ledger with export options and an ACK system so finance can mark payouts reconciled. Deliverables • Source code (preferably Node.js + React or similar modern stack) • Database schema and migration scripts • Postman collection / API docs • One-click deployment script or guideline • 14-day support window after go-live for bug fixes only Acceptance Criteria 1. Registration fails on any invalid field and leaves no partial records. 2. 100,000 simulated sign-ups produce zero duplicate IDs. 3. Payment callbacks are idempotent across 3 repeated hits. 4. Commission ledger matches sample Excel to the paisa. 5. Role-based access passes OWASP ZAP scan with no High findings. 6. Dashboard renders <1 s on a 3G throttle with 50k rows in DB. If this sounds like your wheelhouse, tell me which framework you’d use for the rules engine and how you’d test ID uniqueness at scale.