ForgeRivalBefore you pay
Payments are disabled. The draft fee is ₹2,000 per person for two to five members. If the browser-game reward is offered when registration opens, one verified reward reduces the team subtotal by 10%. The current quote is a preview. Tax treatment, invoice identity, included services, event dates, venue, refund windows and processing timelines must be finalised and shown before payment. No extra charge may be introduced only after a customer pays.
Cancellation or non-delivery by the organiser
Proposed policy for approval: if the event is cancelled or the organiser cannot provide the contracted entry, offer a refund of the unprovided service rather than mandatory credit. If dates, venue or format change materially, provide clear notice and a fair choice to accept or withdraw under published refund terms. Force majeure is not an automatic right to keep all fees. Treatment of any separately delivered course must be disclosed and assessed fairly.
Withdrawal, rejection and no-show
Before paid entries open, publish a dated withdrawal schedule, the outcome if an application is rejected, and proportionate treatment of late withdrawal or no-show. There is no blanket “all fees non-refundable” rule in this draft. Any retention or deduction must be disclosed, justified and lawful. Substitutions require eligibility and fresh individual documents. Travel, accommodation and equipment are not supplied by the organiser; statutory remedies for the organiser’s own conduct remain unaffected.
Inspection, disqualification and unavailable testing
Correctable inspection holds, misconduct, valid official containment-test failures and organiser inability to provide testing are different situations. Each needs its own published financial outcome before a team pays. A valid failure under Technical Draft 0.4 T10.6 disqualifies the entire event entry; a replacement machine cannot reinstate it under that draft. An invalid or incomplete test requires documented review under T10.8. That draft is not an issued rulebook, and no fee-forfeiture rule can be inferred from it.
Failed, duplicate and disputed payments
An unsuccessful payment attempt does not confirm registration. Once connected, the server must verify the payment provider’s result before updating entry status. Duplicate successful payments must be reconciled and the excess returned through an appropriate verified route. Never request a UPI PIN, card PIN or OTP to process a refund. Refund requests, acknowledgement dates, decisions and transaction references must be tracked. Support contact, request window and initiation/settlement timelines are pending and must be disclosed before checkout is enabled. Statutory remedies and payment-provider dispute options remain available.
Document owner: Liftor Software and Technology Pvt Ltd. Review status: draft; not effective for paid entry.