Token presence
Open the account screen and confirm the referral panel exposes a token. The token is the unique identifier; the desk treats its presence as the rule, not a marketing placeholder.
Home · Refer code
Referral categoryJackpotnow refer code: what a referral page can verify
A refer code is a category on a rummy operator's account screen, not a published numeric coupon. This page describes what the operator publishes about its referral category, what the desk cannot publish about a live code, and where to verify a code on the operator's own page rather than on a third-party listing.
What the category is
Three things the operator publishes about referrals
- The referral category lives on the account screen, on a settings panel the desk calls the referral panel.
- The referral panel exposes a unique shareable token for the reader's account. The token is the operator's own identifier; treat it as the audit trail.
- The referral panel exposes the rule by which a referee is credited. The rule is the operator's own publication; the desk does not paste the exact rule because the operator rotates it.
This publication does not paste a specific jackpotnow refer code in any visible copy. The desk's editorial position is that the live code is the operator's own publication on the account screen; pasting it on a third-party site creates a category misuse, not a service to the reader.
Verifier clauses
A
B
C
D
Three clauses the reader can run on the operator's page
Rule reading
Read the rule the operator publishes next to the token. The rule may rotate; the rotation is the operator's contract with the reader.
Audit trail
Take a screenshot of the rule on the date of the read. The screenshot is the audit trail if a later dispute arises; the desk treats the screenshot as the reader's responsibility, not the operator's.
Third-party check
A third-party listing that advertises a refer code is a marketing listing, not an editorial record. The desk recommends the operator's own page as the only audit trail.
Family-side framing
Where a family member's read differs
Where a family member is reading this page rather than the reader, the practical next step is identical to /responsible-play/'s family-side framing: ask the reader to open the account screen and confirm the referral panel exposes a token. The token is the audit trail; the family-side habit is the same as for any other account setting.
The desk does not list a generic "use this code" recommendation. A generic code is the marketing pattern the family-side read is meant to displace. The family-side read is the audit trail, not the marketing copy.
What this page does not publish
Two patterns the desk treats as off-page
- A specific jackpotnow refer code in any visible copy. The desk publishes this page as the category walk, not as a code listing.
- A specific bonus or commission value for a successful referral. The operator's own publication rotates; the desk keeps the rule reading on the operator's own page, not on the desk's.
Related reading
The audit trail is the operator's own page
The referral panel is the operator's own publication. The desk recommends the reader open the account screen and confirm the panel's token presence, rule reading and audit trail.
Read the bonus-code walk
Three asks the refer-code page answers
The reader asks the deck answers
Where is my token?
On the account screen, on a settings panel the deck calls the referral panel.
What is the audit trail for a refer rule?
A screenshot of the rule on the date of the read. The reader's screenshot is the audit trail.
What is a third-party listing?
A marketing listing, not an editorial record. The desk recommends the operator's own page as the only audit trail.
Frequently asked
Three questions the page answers
QWhere does the referral panel live?
On the account screen, on a settings panel the deck calls the referral panel.
QWhat does the panel expose?
A unique shareable token for the reader's account, and the rule by which a referee is credited.
QWhat does the deck not paste?
A specific jackpotnow refer code. The deck publishes this page as the category walk, not as a code listing.
The audit pattern
Three clauses the reader runs on the operator's page
A
Token presence
Open the account screen and confirm the referral panel exposes a token. The deck treats the panel's presence as the rule.
B
Rule reading
Read the rule the operator publishes next to the token. The rule may rotate; the rotation is the operator's contract with the reader.
C
Audit trail
Take a screenshot of the rule on the date of the read. The screenshot is the audit trail if a later dispute arises.
Family-side framing
Where a family member's read differs
- Ask the reader to open the account screen and confirm the referral panel exposes a token. The token is the audit trail.
- The family-side habit is the same as for any other account setting: keep the audit trail on the reader's own device, not on the desk's.
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.