Brand SERP cluster · wallet and KYC

Betinia wallet and KYC: what the operator asks for at verification time and what is stored

A reference for the KYC field requirements the operator asks for at verification time. The desk cites the canonical safety explainer for the deposit rail matrix and the PAN last-4 storage policy.

Reading time · 8 min Last reviewed · 2026-08-10 Source-led

Section 01 · Verified facts

01

What the operator asks for at verification time

The betinia editorial desk confirms the KYC field requirements every operator asks for at verification time. The four fields are PAN, Aadhaar, address proof and video-KYC; the storage policy is last-4 only for PAN and Aadhaar per the operator's privacy notice.

The desk confirms the deposit rail matrix on the canonical safety explainer. The RBI-permitted rails for real-money rummy are UPI, net-banking and debit card; credit-card and cryptocurrency rails are not permitted. The desk links to the canonical safety explainer for the full matrix.

Detail block

Four KYC fields and the storage policy

FieldWhat is collectedWhat is storedVerification cue
PAN10-character PAN numberPAN last-4 only, per the operator's privacy noticeITD portal check on the operator's verification dashboard
Aadhaar12-digit Aadhaar number (or virtual ID)Aadhaar last-4 only, per the operator's privacy noticeUIDAI portal check on the operator's verification dashboard
Address proofRecent utility bill, bank statement or rent agreementDocument type and issue date; the document itself is not retained beyond verificationAddress match against the bank account statement
Video-KYCLive video capture with the player holding the PAN cardNot retained beyond verification per the operator's privacy noticeLive verification on the operator's verification dashboard

Reader checklist

Five items the reader runs before completing KYC

  • Privacy noticethe operator's privacy notice states last-4 storage
  • PANthe ITD portal confirms the PAN is valid
  • Aadhaarthe UIDAI portal confirms the Aadhaar is valid
  • Address matchthe bank account statement matches the address proof
  • Video-KYCthe operator's verification dashboard confirms the live capture

Continue reading

Three pages the desk suggests after this read

Hub · Safety

Safety and KYC explainer

The canonical safety explainer with the deposit rail matrix and dispute rescue route.

Continue →
Hub · Login

Betinia login

The returning-device login path the desk pairs with KYC completion.

Continue →
Hub · Responsible play

Responsible play toolkit

Limit-setting, deposit caps and the verified support channels.

Continue →

Detail block · wallet and KYC mechanics

Five checks the desk runs before submitting PAN and Aadhaar at the KYC step

  1. Operator confirmation — the operator's KYC step captures the reader's PAN and masked Aadhaar; the desk refuses any operator that asks for the reader's biometric data.
  2. Field placement — the KYC step is reachable from the wallet screen and not buried in a help-center article; the desk treats a buried KYC step as a friction observation.
  3. Privacy notice — the operator publishes a privacy notice at the KYC step; the desk refuses any operator that does not surface a privacy notice at the KYC step.
  4. Partner registration — where the operator routes KYC through a third-party partner, the partner is registered on the operator's partner register; the desk refuses any partner that is not on the register.
  5. Stated turnaround — the operator publishes a stated KYC turnaround on the help center; the desk refuses any operator that does not publish a KYC turnaround.

Section 02 · Wallet and KYC detail

02

How the desk reads the operator's wallet and KYC surface

The desk treats the operator's wallet and KYC surface as a five-row reference. The first row is the operator's wallet ledger; the desk asks the reader to confirm the wallet ledger is reachable from the lobby and not buried in a help-center article. The second row is the operator's deposit rail list; the desk asks the reader to confirm the rail list against the operator's status page and to refuse any operator that lists a credit-card-only rail.

The third row is the operator's KYC step; the desk asks the reader to confirm the KYC step captures the reader's PAN and masked Aadhaar and not the reader's biometric data. The fourth row is the operator's partner register; where the operator routes KYC through a third-party partner, the desk asks the reader to confirm the partner is on the register and to refuse any partner that is not.

The fifth row is the operator's stated KYC turnaround; the desk asks the reader to confirm the turnaround against the operator's help center and to refuse any operator that does not publish a turnaround. The desk's standing rule is that no PAN or Aadhaar is submitted without all five rows passing; the desk records a failing row with a friction observation and stamps the verdict chip with the date of the check.

Reader questions

Three questions the desk keeps answering on the wallet and KYC surface

Why does the operator ask for masked Aadhaar and not the full Aadhaar number?

The operator's standing rule is that the KYC step captures the masked Aadhaar (last four digits) and the Aadhaar's XML file. The full Aadhaar number is not captured at the KYC step; the desk treats a request for the full Aadhaar number as out of scope and asks the reader to verify on the operator's help center.

Can a reader fund the wallet without completing the KYC step?

Yes, but withdrawals are blocked until the KYC step is complete. The desk asks the reader to complete the KYC step before the first deposit and to refuse any operator that allows a deposit without a clear KYC path. The desk treats a missing KYC path as a friction observation.

What does the desk record when the operator's KYC step asks for biometric data?

The desk records the operator as friction-observed against the data-scope row and stamps the verdict chip with the date of the check. The desk asks the reader to verify the data scope against the operator's privacy notice and to refuse any operator that asks for biometric data outside the KYC step's stated scope.

\n
\n
\n
\n
\n

Reading cadence

\n

How the desk re-issues the wallet and KYC surface against the operator's record

\n
\n
\n

The desk re-issues the wallet and KYC surface on three cadences. The first cadence is per quarter: the desk reads the operator's wallet and KYC step against the five-row reference and re-issues the verdict chip on the operator's wallet and KYC step. The second cadence is per half: the desk reads the operator's wallet and KYC step against the most recent operator calendar and re-issues the verdict chip on the operator's wallet and KYC step.

\n

The third cadence is per incident: where a reader reports a wallet or KYC event that crosses the desk's incident threshold, the desk verifies the event against the operator's published record and re-issues the verdict chip only when the operator's record changes. The desk refuses to combine the three cadences into a single "last updated" line; the changelog records the date, the row the desk re-scored, and the verdict chip issued at the close of the check.

\n

For the per-row verification, the desk asks the reader to confirm the operator's wallet and KYC step against the five-row reference and to refuse any KYC step that asks for biometric data outside the KYC step's stated scope. The desk's standing rule is that no wallet or KYC step is submitted without all five rows passing; the desk records a failing row as a friction observation and stamps the verdict chip with the date of the check.

\n
\n
\n \n
\n
\n
\n
\n

Edge cases

\n

Three edge cases the desk records on this surface

\n
\n
\n

The desk records three edge cases on this surface. The first edge case is a partner-routed install: where the operator routes the install through a third-party partner, the desk records the partner's verification record as the canonical record and not the operator's stated record. The second edge case is a region-specific install: where the operator's listing is unavailable in the reader's region, the desk records the unavailability as a friction observation and asks the reader to verify the unavailability against the operator's help center.

\n

The third edge case is a third-party-mirror install: where a third-party mirror publishes the operator's installer, the desk records the mirror as a phishing risk and asks the reader to refuse the mirror. The desk's standing rule is that no install is recorded without the operator's verified domain; the desk records a third-party-mirror install as a friction observation and stamps the verdict chip with the date of the check.

\n

For the per-case verification, the desk asks the reader to confirm the operator's verification record against the operator's status page and to refuse any operator whose verification record diverges from the desk's standing rule. The desk's standing rule is that no case is complete without the operator's verification record being confirmed against the operator's help center; the desk records a missing record as a friction observation and stamps the verdict chip with the date of the check.

\n
\n
\n