Legal

Compliance & payments

Last updated: 28 July 2026. This page explains how money flows through MyGame and the guardrails we operate under. It is a factual reference, not a substitute for advice from your accountant or counsel.

Money flow

All payer-facing prices, convenience fees, platform commission, GST and net-to-payee amounts are computed server-side at checkout and frozen onto the payment record (rate_snapshot). Rate changes never apply retroactively to a completed transaction.

Online payments are collected via a licensed payment gateway (Razorpay). Manual UPI, bank transfer and cash receipts are verified against a UTR / reference by a platform admin before the booking or ticket is confirmed.

RBI Payment Aggregator (PA) posture

Under RBI's PA/PG guidelines, collecting funds on behalf of merchants and settling them later is a regulated activity. MyGame operates in split-at-source mode using an authorised aggregator: player payments settle directly to the venue / organizer merchant account via the gateway's Route / Easy Split rails, and only our platform commission and applicable GST land in the MyGame account. This keeps funds out of the platform's escrow and outside PA scope.

Where a merchant hasn't onboarded KYC yet, or is being paid manually, that specific transaction is handled offline between the payer and the merchant — MyGame is not a party to the fund transfer, only to the reconciliation record.

KYC for venues & organizers

Payouts are gated on approved KYC. Merchants submit legal name, PAN, GSTIN (optional up to threshold), registered address, and either UPI VPA or bank account (name, account number, IFSC). We store what's required to release payouts and audit them; sensitive fields are access-controlled and never exposed in the public API.

GST invoicing

A tax invoice is generated automatically on every captured payment with HSN/SAC 999599, GST at the platform-configured rate, and the buyer's billing name. Invoices are available under Invoices and can be saved as PDF.

Refunds & cancellations

Refunds are requested from the Refunds page against a captured payment and approved by an admin. On approval, the linked booking or ticket is cancelled and the payment is marked refunded or partially refunded. Gateway fees on refunds follow the aggregator's schedule.

Audit trail

Every rate change, payment settlement, refund decision, payout status change and KYC decision writes to an immutable audit_log. Admins can review it at /admin/audit. Webhook events are de-duplicated by provider event id so a replay cannot double-post a payment.

Data retention & privacy

Payment metadata, invoices and audit rows are retained for at least eight financial years to meet Indian tax and PA record-keeping expectations. Uploaded UTR proofs are retained for the same window and are only visible to the payer and platform admins.

Questions? Reach the platform owner at vishnu.uday@nexorasuncore.com.