ABSI-MIDCON 2027
Delegate registration and online payment for the association's mid-term conference, 6 and 7 March 2027 in Mohali.
- 2027
- Conference platform, payments
The problem
The conference needed to take money from several hundred delegates across different fee categories, and every one of them expects a receipt they can claim against an institution. A committee of practising surgeons was going to run it between clinics, so anything that required someone to watch a dashboard was going to fail.
What we did
Confirmation follows the payment, not the browser
A delegate who closes the tab on the payment screen has still paid. Confirmations are sent from a signature-verified Razorpay webhook, so the receipt is tied to the captured payment rather than to whether the browser made it back to the site. The form refuses to take a payment at all if the webhook secret is missing, rather than charging someone it cannot confirm.
Two emails, settled independently
The delegate gets a receipt and the secretariat gets a notification. They are sent together but settled separately, so one bad address cannot lose both. Each goes out as HTML with a plain-text alternative beside it, which is what text-only clients read and what spam filters expect.
A register the committee can actually open
Every confirmed registration is appended to a Google Sheet. No admin login, no training: the treasurer opens a spreadsheet they already know how to use and reconciles it against the payment dashboard.
Where it landed
Live at absimidcon2027.in, taking registrations. The fee tariff, the categories, and the convenience fee are all one file, so a committee decision becomes a one-line change rather than a rebuild.
Stack
- Next.js
- TypeScript
- Razorpay
- Nodemailer
- Tailwind CSS