Identity document upload
The KYC form asks for a single identity document. The form's accepted list is the audit trail; the operator's review of the document is the gate.
Home · Wallet and KYC
Payment and verificationJackpotnow wallet and KYC: what the desk publishes about the process
Wallet and KYC are a process story, not a guarantee story. This page walks the document checklist, the wallet flow and the failure modes the reader may encounter before a first deposit and a first withdrawal. The desk does not paste a numeric withdrawal window; the operator's own publication is the rule.
Document checklist
Six document classes the operator publishes on the help centre
- A single identity document; the operator publishes the accepted list on the help centre. The desk treats the list as the audit trail.
- A single address document; the operator publishes the accepted list on the help centre. The desk treats the list as the audit trail.
- A single payment instrument; the operator publishes the accepted rails. The desk treats the rail list as the audit trail.
- A single session limit; the operator publishes the limit panel on the account screen. The desk treats the limit panel as the rule.
- A single deposit cap; the operator publishes the cap panel on the wallet screen. The desk treats the cap panel as the rule.
- A single self-exclusion length; the operator publishes the exclusion panel on the account screen. The desk treats the panel as the rule.
Where the operator's help centre does not publish one of these six classes, the desk treats the class as unpublished. The reader's audit trail is the operator's own publication; the desk does not invent a class on the reader's behalf.
The walk
1
2
3
4
Four steps from a fresh account to a first deposit
Outcome banner
The wallet page shows a status banner. Green means the wallet flow opens; anything else is a /customer-care/ ticket before any further deposit.
Payment rail
The wallet page exposes a single payment rail per region. The reader picks the rail; the operator's contract with the rail is the audit trail.
First deposit
The first deposit lands on the wallet page; the operator's receipt page mirrors the rail. The receipt is the audit trail.
Failure modes
A
B
C
D
Three failure modes the reader can plan for
Mismatch
A name or address mismatch between the document and the registration is the most common KYC failure. The operator's review surfaces the mismatch on the banner; the desk recommends a /customer-care/ ticket with the help-centre article number.
Pending review
A pending review that does not turn green within the published window is a /customer-care/ ticket. The desk treats the published window as the audit trail.
Rail failure
A payment rail failure on a first deposit is a rail-side issue, not an operator issue. The desk treats the rail-side failure as a rail-side audit trail.
Three clauses
The summary of the three clauses is the audit trail. The reader's screenshot is the audit trail; the operator's reply is the rule.
What the desk does not publish
Two patterns the desk treats as off-page
- A numeric UPI or IMPS window in any visible copy. The operator's own publication is the audit trail; the desk does not invent a window.
- A numeric deposit-rail multiple in any visible copy. The operator's own help-centre article is the rule; the desk does not paste a multiple.
Related reading
Process story, not guarantee story
The KYC walk is the desk's three-step read on the verification flow; /safety/ holds the broader account-integrity context.
Read the safety walk
Three asks the wallet-kyc page answers
The reader asks the deck answers
Where is the KYC walk?
In the three-step walk from identity document to outcome banner.
Where is the payment rail?
On the wallet page, on a single rail per region. The rail is the operator's contract.
Where is the failure mode?
On the KYC banner. The banner is the audit trail; the deck treats the banner as the rule.
Frequently asked
Three questions the page answers
QWhat is the wallet walk?
Two tabs on the wallet page: deposit and withdrawal. The tabs are the audit trail.
QWhere is the KYC banner?
On the wallet page. Green means the wallet flow opens; anything else is a /customer-care/ ticket.
QWhat is the audit trail for a failure mode?
A screenshot of the operator's banner on the date of the read. The deck treats the screenshot as the audit trail.
Document checklist
1. Identity document
2. Address document
3. Payment rail
4. Session limit
5. Deposit cap
6. Self-exclusion
Six document classes the operator publishes
A single document the operator publishes the accepted list of. The deck treats the list as the audit trail.
A single document the operator publishes the accepted list of. The deck treats the list as the audit trail.
The accepted rails the operator publishes. The deck treats the rail list as the audit trail.
The limit panel on the account screen. The deck treats the panel as the rule.
The cap panel on the wallet screen. The deck treats the cap panel as the rule.
The exclusion panel on the account screen. The deck treats the panel as the rule.
Failure modes
Three failure modes the reader can plan for
- Mismatch. A name or address mismatch between the document and the registration. The deck recommends a /customer-care/ ticket with the help-centre article number.
- Pending review. A pending review that does not turn green within the published window. The deck treats the published window as the audit trail.
- Rail failure. A payment rail failure on a first deposit. The deck treats the rail-side failure as a rail-side audit trail.
A deeper read
What this page is for, and what it is not
This page is the contextual read; the operator's own help-centre article is the rule. The contextual read and the rule are aligned when the operator publishes the rule on the help centre. The contextual read and the rule are unaligned when the operator does not publish a rule on the help centre; the desk treats the unaligned case as the audit trail.
The contextual read sits between the reader's own jurisdiction and the operator's own publication. The reader's jurisdiction is the rule the reader is actually making the decision on; the operator's own publication is the rule the reader is binding to. The two are aligned when the reader's jurisdiction is one of the published rules; the two are unaligned when the reader's jurisdiction is not. The desk's habit is to assume the reader's jurisdiction is one of the published rules; the reader's audit trail is the operator's help-centre article number on the date of the read.
The contextual read and the regulator's publication interact in the rule shape: the regulator's publication is the central framing the desk aligns with; the contextual read is the desk's reading of the operator's help-centre article. The two are aligned when the operator publishes the rule on the help centre and the regulator's publication is unchanged; the two are unaligned when either side rotates.
Where the audit trail sits
The audit trail is the operator's help-centre article on the date of the read. The reader's screenshot is the audit trail; the operator's reply on the /customer-care/ ticket is the rule. The two are aligned when the screenshot matches the reply; the two are unaligned when the screenshot shows a different rule. The desk's habit is to assume the screenshot is the audit trail and the operator's reply is the rule; the reader's audit trail is the screenshot and the reply together.
The audit trail and the central framing interact in the rule shape: the central framing is the Promotion and Regulation of Online Gaming Act 2025; the audit trail is the operator's help-centre article. The two are aligned when the operator publishes the rule on the help centre and the central framing is unchanged; the two are unaligned when either side rotates.
The audit trail and the per-state rule interact in the rule shape: the per-state rule is the regulator's own publication; the audit trail is the operator's help-centre article. The two are aligned when the regulator's publication is unchanged and the operator publishes the rule on the help centre; the two are unaligned when either side rotates. The desk's habit is to assume the per-state rule is the regulator's own publication; the reader's audit trail is the per-state rule itself.
What the desk does not paste
The desk does not paste a numeric withdrawal window. The operator does not publish one; the desk does not invent one. The reader's audit trail is the operator's help-centre article; the regulator's publication is the audit trail for any per-state eligibility.
The desk does not paste a per-operator licence. The regulator's own publication is the audit trail. The desk does not paste a per-state eligibility list; the reader's jurisdiction is the audit trail. The desk does not paste a "guaranteed" claim; the central framing is the audit trail.
What changes between operators
The contextual read is the same across operators; the operator's publication differs. The contextual read sits between the reader's own jurisdiction and the operator's own publication. The desk's habit is to assume the contextual read is the contextual read; the reader's audit trail is the operator's help-centre article number on the date of the read.
The contextual read and the operator's publication interact with the central framing: the central framing is the Promotion and Regulation of Online Gaming Act 2025; the contextual read is the desk's reading of the operator's help-centre article. The two are aligned when the operator publishes the rule on the help centre and the central framing is unchanged; the two are unaligned when either side rotates.