Every event sells on exactly one of two rails, chosen per event. They are genuinely different products, not a settings toggle, and the difference is where the money lands.
Razorpay gateway
The buyer pays through Razorpay. Razorpay tells us the moment it succeeds, the ticket is issued and emailed within seconds, and the money settles into your Razorpay account on their schedule.
Choose this when you want it to run without you.
Detail: Getting paid through Razorpay about getting paid through razorpay.
Direct UPI
The buyer pays your own UPI address. The money goes buyer → you and never passes through us. There is no gateway account and no settlement wait.
The cost is that a UPI address has no webhook and no verification API. Nothing tells us the payment happened. The buyer types in the 12-digit reference their payment app gave them, you read your own bank app, and you approve it. Until you do, they do not have a ticket.
Choose this when you would rather have the money immediately and are willing to check each one.
Detail: Getting paid to your own UPI id about getting paid to your own upi id and Verifying a UPI payment about verifying a upi payment.
Picking, and changing
The rail is a field on the event, set when you create it. Your organization also has a default rail for new events in Settings — it seeds new events only, and changing it never moves an event that already exists.
Decide before you publish
Orders record the rail they were placed on, so old ones stay coherent whatever you do later. But changing the rail on an event that is already selling changes the payment method under buyers who are mid-checkout.