Paid event booking had to stay connected.
Reservations, payments, cancellations, QR entry, and admin follow-up had to stay connected across the customer and admin journey.
Flagship proof
UTSOV Case Study
A shipped event platform where reservation status, Razorpay checkout, webhook events, cancellation/refund handling, QR attendance, and admin operations live in one product.
Reservation transactions560
Razorpay webhook events720
QR attendance scans558
Production proofPayment + fulfillment
UTSOV case study
Before. Built. Proof. What this proves.
A production event platform.
Connected reservation status, Razorpay payment lifecycle, QR attendance, cancellation paths, and admin controls.
560 reservations, 720 payment events, 558 scans.
560 reservation transactions; 351 confirmed reservations; 720 Razorpay webhook events; 558 QR attendance scans.
Paid-service software beyond checkout.
Payment status, exceptions, fulfillment, and admin operations can stay connected in one working system.
Current production proof
Reservation status, payment lifecycle, and entry tracking exist in the data.
Production metrics from the current UTSOV system. They prove MLPOINT can ship payment status, reservation lifecycle, QR fulfillment, cancellation paths, refunds, and admin controls; private-event pilots will measure quote speed, deposit follow-up, stale request value, and staff readiness next.
Reservation status history
The current migrated DB contains 1,756 reservation status rows across pending, paying, confirmed, and cancelled statuses.
560Unique transactions
351Confirmed latest status
Payment lifecycle
Razorpay checkout is backed by transaction records and webhook events for authorized, captured, and failed payment statuses.
213Transaction records
720Webhook events
Entry and fulfillment
QR attendance scans show the product continues after payment into real-world entry and fulfillment tracking.
558QR scan rows
279Scanned transactions
Build depth
The local codebase includes booking, reservation services, payment verification, webhook idempotency, cancellation/refund handling, QR service, pass resend, and notifications.
273Implementation files
25Python test files
Buyers can inspect a real public booking product, not just a private screenshot or proposal.
The product includes Razorpay checkout, payment verification, transaction records, webhook events, receipt logic, and confirmation statuses tied to the customer journey.
Cancellation previews, refund paths, policy copy, and admin actions are modeled inside the product instead of one-off support messages.
QR attendance scanning shows the product tracks entry and delivery, not only booking and payment.
What shipped
Concrete product screens, not abstract advice.
This is the proof buyers should inspect before trusting MLPOINT with a paid service operations build.
Organizer event setup
Event records, publishing inputs, capacity-sensitive details, and public presentation flow.
Customer booking path
Discovery, booking intent, attendee information, customer status, and confirmation handoff.
Razorpay payment flow
Order creation, checkout integration, payment verification, receipt, and transaction records.
Cancellation and refund handling
Cancellation preview, refund policy handling, exception paths, and customer messaging.
Back-office controls
Admin views for transactions, event status, support action, and lifecycle follow-through.
Trust and policy pages
Payment transparency, privacy, terms, cancellation, and refund language built into the product.
Reusable pattern
Why UTSOV matters for the current MLPOINT offer.
UTSOV proves the pattern MLPOINT now sells: customer action, payment status, exception handling, admin ownership, and follow-up inside one product flow.
Reservation status
Pending, paying, confirmed, and cancelled reservations are tracked as product records, not loose messages.
Payment lifecycle
Razorpay orders, checkout, verification, transaction records, and webhook events are tied to the flow.
Exception handling
Cancellation previews, refund policy handling, support paths, and customer messaging are modeled.
QR fulfillment
Entry scans prove the product continues beyond checkout into attendance and delivery tracking.
Admin operations
Back-office tools for managing customer transactions, event status, cancellation cases, and support actions.
Reusable MLPOINT pattern
The same owner/status pattern maps to paid classes, workshops, private events, memberships, and service queues.