No public code is confirmed in the staged source snapshot. Destination-applied offers and welcome tiers are how this publisher rewards a new player.
Status: no public code confirmed
This route explicitly does not list a code. The staged snapshot does not publish one, and we do not invent codes on the visitor’s behalf. If a code is required to trigger an offer on the publisher’s onboarding screen, it is destination-applied and would appear inside their flow, not anywhere on this product profile.
What the source does show
Refer & Earn: two milestones (₹110 per friend across the milestones published).
Welcome bonus tiers: three deposit bands with explicit bonus and Gullak sums, displayed at /promos/.
Reward sections: cashback, VIP rewards, bonus calendar, daily, weekly, refer and leaderboard, displayed in the promotions route.
VIP auto-enrolment threshold: ₹1,000 in total bets, displayed at /vip/.
Source conflict we treat as unresolved
The snapshot lists a ₹110 paid-referral total and a separate rewards page that advertises ₹400. We display both totals and label the conflict as unresolved. We do not pick one number as the ‘truth’ and hide the other. Shortlisting visitors need to see the conflict to avoid being misled by either page.
Safe checks before you act
Open the publisher’s rewards page from the install destination, not from this domain.
Confirm the offer title and the deposit / play condition match what you expected.
If a code box is left empty at sign-up, the offer is destination-applied.
If anything else is requested, stop and use support.
This route will not invent a code on the visitor’s behalf. It will not suggest that a code posted on social media is valid. It will not redirect to a third-party code-aggregator or to a publisher’s onboarding form that requires a code we cannot verify.
Install Yono Games appDirect route. Sponsored affiliation.
Destination-applied means the offer activates when you reach the publisher’s onboarding screen and complete a qualifying action, such as a first deposit. The publisher’s screen is the source of record for the offer.
Why a public code would be useful
A public code would let visitors confirm eligibility before installing. The staged snapshot does not publish one, so this route does not invent one.
What the refer-and-earn conflict looks like in practice
The snapshot carries ₹110 across two milestones on the affiliate page, and ₹400 on a separate rewards page. We display both because an audit-minded reader needs to know the snapshot is internally inconsistent on this number.
What to do if a third-party advertises a code
Treat it as unverified. The publisher’s official page is the source. Open /contact/ if you want to send us a third-party code so we can compare it against the publisher’s own channel.
Editorial coverage
For a narrative read of the same conflict, see /news/refer-and-earn-source-conflict/.
A short visitor’s reading order
If you have thirty seconds, read the headline: no public code is confirmed. If you have three minutes, read the safe-checks list and the destination-applied explanation. If you have ten minutes, read the editorial coverage section and follow the link to the conflict article.
Why this route exists
Most publisher pages have a codes area; visitors expect a code. The honest answer at this publisher is ‘not in source’. The route exists to publish that answer rather than allow a placeholder.
Destination-applied offers in plain language
Destination-applied means the offer activates when you reach the publisher’s onboarding screen and complete a qualifying action. Examples of qualifying actions are a first deposit at a stated trigger, a first qualifying bet or a sign-up form. The publisher’s onboarding screen is the source of record.
What we will not do here
We will not invent a code on the visitor’s behalf. We will not suggest that a code posted in a third-party advert is valid. We will not link to a code-aggregator that we cannot verify.
What happens when the snapshot updates
If the snapshot later publishes a public code, the desk will republish this route with the new value and the same verify-then-ask loop. Until then, this route states ‘no public code confirmed’.
Editorial coverage
For a narrative read of the same conflict, see /news/refer-and-earn-source-conflict/. A follow-up will be published if the publisher publishes a reconciliation.
A working visitor’s checklist
If you have been shown a code by a third party, treat it as unverified before using it. Open the publisher’s rewards page from /Login/playnow and confirm the code is live. Read which trigger it relates to (first deposit, first qualifying bet, sign-up) and which conditions apply. Only then enter the code on the publisher’s onboarding screen.
What the routes do not show
This product profile does not surface codes the snapshot does not publish. The publisher may publish codes inside its onboarding flow, by email, by SMS, or by a partner’s page. None of those codes are listed on this route because we cannot verify them as part of the snapshot.
Editorial archive and audit trail
The refer-and-earn conflict between the affiliate page and the rewards page is documented in /news/refer-and-earn-source-conflict/. The article carries the underlying rows. We do not display those rows on this route because the two numbers conflict; surfacing them here would imply we have settled the dispute.
What we will not do
We will not invent a code. We will not suggest that a code posted on social media is valid. We will not link to a code-aggregator we cannot verify. The honest answer when the snapshot is silent on a code is ‘no public code confirmed’.
What happens when the source changes
If the publisher later publishes a public code in the snapshot, the desk republishes this route with the new value. Until then, this route states ‘no public code confirmed’.
Beyond this article
For welcome tiers, see /promos/. For the VIP matrix, see /vip/. For the refer-and-earn conflict, see /news/refer-and-earn-source-conflict/.
Why the routes show the affiliate disclosure
The route includes an explicit affiliate disclosure paragraph. The disclosure tells you this product profile receives compensation for installs routed through /Login/playnow, and that compensation does not change the figures on the site. This is part of the editorial discipline that applies across the verification product.
What about destination-applied milestones
Destination-applied milestones include first-deposit bonus, first qualifying bet, sign-up form completion, account verification and similar onboarding-side rewards. The publisher’s onboarding screen is the source of record for which milestones apply. We do not list milestones the snapshot does not publish.
Why the route links to the news article
The news article at /news/refer-and-earn-source-conflict/ carries the same conflict with editorial framing. The route and the article are the same story in two formats. Pick whichever helps your decision; both rely on the same snapshot row.
What about a snapshot-published code in the future
If the publisher later publishes a code in the staged snapshot, the desk republishes this route with the code’s trigger, conditions and validity window. Until then, this route states ‘no public code confirmed’.
What about seasonal codes
Some publisher programmes publish seasonal codes by email or SMS. Those codes are destination-applied and live inside the publisher’s onboarding flow. We do not list them here because we cannot verify them as part of the staged snapshot.
What the audit trail looks like
When the desk publishes this route, the editorial archive records the snapshot timestamp and the row that the route draws on. The archive is internal and audit-minded readers can match a route statement to the archive via the file name. The match is deterministic.
What the desk will not show
The desk will not show a code sample even as a format hint, because we cannot verify the publisher’s exact field structure. Use the publisher’s onboarding screen if you need the field structure to enter a code from another channel.
Cookie preferences
Strictly necessary cookies keep core site features working. Optional analytics and marketing cookies are off by default. You can withdraw consent as easily as you give it.
