INDEPENDENT RESEARCH

Dated evidence · commercial links labelled · 18+ · no winning or recovery promise

CASINOCHECKINDIA / भारतहिन्दीVISIT A CHECKED CASINO · 18+
PORTAL / EVIDENCE DIRECTORY / 29.08.2026

How to Check a Gaming Merchant VPA on UPI in India

en-INPUBLISHED: 29.08.2026PAYMENT DECISION GUIDE
VISIT A CHECKED CASINO OPTION · 18+PAYMENT DECISION CHECK · INDIA

UPI, bank or card evidence · no recovery promise · no traffic-light verdict

A UPI payment can show a merchant name that looks familiar, but that display should be treated as one transaction detail rather than conclusive proof of a gaming operator’s legal identity. The practical check is to compare the merchant VPA, displayed merchant or sub-merchant name, transaction status, amount, date, UTR and beneficiary bank information. Record those details before deleting notifications or closing a payment screen.

This guide is prepared by the CasinoCheck India Evidence Desk and editorially reviewed by the CasinoCheck India Standards Desk. The method uses dated primary records only. It does not test deposits, withdrawals or complaint outcomes, and it does not determine whether an online money game is authorised in India.

What a UPI merchant VPA can show

NPCI’s merchant-onboarding circular identifies merchant name, sub-merchant name, payee VPA and merchant category code as relevant merchant data fields. That primary record, checked on , supports treating the VPA and displayed name as important identifiers. It does not support treating a displayed name alone as proof of the underlying legal identity, ownership or Indian authorisation. NPCI merchant circular, checked 29 August 2026.

DetailWhy save itWhat it cannot prove alone
Merchant VPA or payee UPI IDHelps the payer PSP, beneficiary bank and complaint team locate the payee instruction.It does not by itself prove a legal entity, licence or ownership.
Displayed merchant or sub-merchant nameAllows comparison with the name presented during payment.A matching display name is not conclusive identity proof.
Merchant category codeMay be part of merchant-onboarding data.It is not, by itself, an approval or legal classification for a gaming service.
UTR, amount, date and statusCreates a precise payment record for a bank or platform query.These details do not guarantee reversal or recovery.

What to check before approving a payment

Open the final UPI confirmation screen in your payer PSP and read the payee details instead of relying only on a gaming app’s label. Check whether the VPA and displayed name are consistent with the payment instruction you intended to make. Do not enter a UPI PIN merely to inspect a request, and do not share the PIN, one-time password or full banking credentials. NPCI’s safety guidance, checked on , supports checking transaction details and protecting the UPI PIN. It does not authenticate a merchant or guarantee recovery. NPCI safety guidance, checked 29 August 2026.

StageRecordPrivacy precaution
Before approvalVPA, displayed name, amount and the payment purpose shown by the app.Do not publish the screen or expose account balances.
After approvalUTR, date, time, status, payer PSP, beneficiary bank and any reference number.Redact account numbers, phone numbers, QR images and personal addresses before sharing.
If a problem appearsApp messages, error text and correspondence with the bank or payment platform.Keep originals privately and share only what the receiving channel requests.

18+ — visit a checked casino option after reviewing the payment details

Keep a payment record without publishing identifiers

A useful record normally includes the exact merchant VPA, displayed merchant name, UTR, amount, date, time, status, payer PSP and beneficiary bank. If the payment was initiated through a QR code, retain the original transaction record rather than reposting the QR image. A screenshot can be kept for a complaint, but public posting can expose information that helps identify or target the payer.

Do not describe an unverified VPA as fraudulent merely because the name differs from an app label. A mismatch is a reason to pause, preserve the details and ask the relevant payment provider for clarification. The dated NPCI merchant record establishes the existence of these onboarding data fields; it does not establish the identity behind a particular VPA.

Authorised merchant dispute or unauthorised debit?

The distinction affects the complaint route. An authorised merchant dispute is a payment you approved, but the balance, service, refund or recipient is disputed. An unauthorised debit is a transaction you did not approve or initiate. Do not relabel an approved gaming payment as unauthorised simply because the result or service was unsatisfactory.

RBI’s dated primary record, checked on , covers reporting and liability rules for unauthorised electronic banking transactions, including remote online channels such as internet and mobile banking. It does not convert an authorised merchant dispute into an unauthorised transaction and does not guarantee recovery. RBI unauthorised electronic transaction guidance, checked 28 August 2026.

SituationFirst practical routeImportant boundary
You approved the UPI payment but dispute the merchant, credit or service.Use the payer PSP or bank’s transaction complaint route and retain the UTR.It is not automatically an unauthorised transaction.
You did not approve or initiate the debit.Contact the bank or payer PSP promptly and report the unauthorised transaction.Eligibility and liability depend on the facts and applicable banking process.
You suspect financial cyber fraud or deception.Use NCRP and, where appropriate, call 1930 promptly, while also notifying the bank.NCRP is distinct from a bank complaint and does not itself decide a state-law classification.

Which party should receive the complaint?

Start with the payer PSP or bank because it handled the payer-side transaction record. Give it the VPA, UTR, amount, date, status and a clear description of whether you authorised the payment. The beneficiary bank may be relevant to the receiving side, but a payer should not assume that contacting it replaces the payer PSP or bank’s complaint process.

If a complaint about a regulated entity remains unresolved through that entity’s process, the RBI CMS route may be relevant. The existence of that route does not mean that every merchant disagreement is an RBI finding or that payment recovery will follow. See the RBI CMS gaming-payment complaint guide and payment reporting and complaint steps for route separation.

When NCRP and 1930 may be appropriate

The National Cyber Crime Reporting Portal provides the official cybercrime reporting route and identifies 1930 for financial fraud, according to the primary government portal checked on . NCRP is distinct from a bank transaction complaint, an RBI regulated-entity grievance and a state-law classification. A person who suspects financial cyber fraud should preserve the transaction record and report promptly through the appropriate official channel. National Cyber Crime Reporting Portal, checked 28 August 2026.

Use the 1930 and NCRP route guide for the reporting distinction. Do not promise that a report will result in a freeze, reversal, investigation or recovery. Those outcomes are not established by the dated records used here.

How to describe a suspect gaming VPA

Use neutral, precise wording: state the VPA, displayed name, date, amount, UTR and what you personally observed. Say that the details are “unverified” or that there is a “name mismatch” rather than asserting fraud without an official finding. Avoid publishing a full UTR, QR code, phone number, account number or other personal payment identifier. User reports, reviews and forum posts would be contextual signals only; none are used here to establish a complaint, payment outcome or adverse finding.

For the repeatable review method and its limits, read CasinoCheck India’s methodology and about information. Corrections about a factual detail can be sent through contact, privacy and disclaimer information.

Decision checklist

  1. Read the final UPI payee screen in the payer PSP.
  2. Compare the merchant VPA and displayed name with the intended payment instruction.
  3. Stop if the details are unexpected; never disclose a UPI PIN or OTP.
  4. Save the UTR, amount, date, time, status, payer PSP and beneficiary bank.
  5. Classify the issue accurately as authorised merchant dispute, unauthorised debit or suspected cyber fraud.
  6. Contact the bank or payer PSP, and use RBI CMS or NCRP/1930 only for the route that fits the issue.

18+ — visit a checked casino option; no outcome or recovery guarantee is made

Frequently asked questions

Does the name shown in a UPI app prove the gaming merchant's legal identity?

No. The NPCI merchant record lists merchant name, sub-merchant name and payee VPA among onboarding data fields, but a displayed name alone does not prove the underlying legal identity, ownership or Indian authorisation.

Which UPI details should I save before making a complaint?

Save the merchant VPA, displayed merchant or sub-merchant name, UTR, amount, date, time, transaction status, payer PSP and beneficiary bank. Redact personal identifiers before sharing publicly.

What is the difference between an authorised merchant dispute and an unauthorised debit?

An authorised merchant dispute concerns a payment you approved but now dispute. An unauthorised debit is a transaction you did not approve or initiate. RBI’s unauthorised-transaction rules do not turn an approved merchant dispute into an unauthorised payment.

When should a suspect gaming VPA be reported to 1930?

Use 1930 and the NCRP route promptly when you suspect financial cyber fraud, while also notifying your bank or payer PSP. NCRP is separate from a bank complaint and does not guarantee recovery.

Does checking a merchant VPA guarantee that a payment is safe?

No. Checking the VPA and displayed name can help preserve and compare transaction details, but NPCI safety guidance does not authenticate a merchant or guarantee payment recovery.

Editorial record

Author
CasinoCheck India Evidence Desk
Editorial review
CasinoCheck India Standards Desk
Method
Dated source-layer review and evidence limits
Reviewed
29 August 2026
Corrections
Submit a documented correction