Why there is no public referral code on this product profile
The affiliate record and the rewards page disagree. We explain why we will not publish either number until the source is reconciled.
Visitors arriving at indiaslotsapp.com often ask about a public referral code. The brand app supports invite-based rewards inside the lobby, but the website does not publish a code. This short article explains why, what the staged sponsor record actually shows and what changes when a code becomes verifiable.
What the staged record shows
The staged sponsor record lists a single field for invite-based rewards, but the field is empty in the snapshot captured for this build. The affiliate partner reference includes a code field, but it does not match the snapshot value. Until the two sources agree, the website treats the absence of a verifiable code as the operational truth.
Why we do not invent a value
Publishing a guessed or stale code is worse than publishing none. A visitor who types a stale code loses the reward; the brand loses trust. The conservative choice is to display the absence honestly and explain the gap.
What the Code page does instead
The Code page is a safe-check list: what to look for inside the in-app lobby, how the invite-based reward is described in the official in-app screens and what to do when the in-app lobby surfaces a code. The page does not display a code string. It points to the in-app source.
What changes when a code becomes verifiable
If the sponsor snapshot and the affiliate reference agree on a single code, the Code page will publish it with a verification timestamp. Until then, the page remains a safe-check list and the website footer continues to link to it.
How to verify inside the app
After install, open the rewards section of the in-app lobby. If the in-app rewards screen surfaces an invite field, the value shown there is the operational truth. The website never overrides the in-app lobby.
If you arrived here from a third-party post
If you reached this page from a third-party blog or social post that quotes a code, treat that code as unverified until the in-app lobby shows the same string. Posts can be recycled; the in-app lobby refreshes on every load.
What the partner dashboard records
The partner dashboard is the affiliate-facing record. It records milestone rewards as a sum of two sub-rewards: ₹30 credited when a referred friend signs up, and ₹80 credited when the friend deposits and plays. The two rewards are independent, but the dashboard sums them into a single milestone value for reporting purposes. The sum is ₹110.
The dashboard's purpose is reporting, not marketing. It exists so the affiliate can see how many friends they have referred and how much they have earned. The milestone values are operational, not promotional; they are not designed to be pasted into a social-media caption.
What the rewards page records
The rewards page lives inside the in-app rewards tab. It publishes the milestone value as ₹400 - a single number, not a sum. The ₹400 figure includes sub-rewards not present in the dashboard, which is why the two numbers diverge. The rewards page is the surface the player sees; the dashboard is the surface the affiliate sees. Both are correct from their own perspective.
The conflict is editorial, not operational. The dashboard and the rewards tab do not disagree on what an account is credited - they disagree on how to describe the milestone in a single number. Until the operator resolves the description, neither number belongs on the brand profile.
Why the brand profile does not pick one
Picking the higher number (₹400) would overstate the milestone for the majority of accounts, which only receive the dashboard sum (₹110). Picking the lower number (₹110) would understate the milestone for accounts that qualify for the rewards page total. Either choice biases the visitor.
The brand profile is not in a position to bias the visitor. The editorial contract on this product profile is that every number ties back to a single source row, and the source row for the milestone reward is in conflict. Publishing either number without disclosing the conflict breaks the contract.
What visitors should do in the meantime
Treat the in-app bonus tab as the source of truth for what a specific account can claim. If a code appears in the bonus tab, the milestone reward for that code is published in the same card, with the conditions spelled out in plain language. If a code does not appear in the bonus tab, no amount of social-media copying will surface it.
For visitors who arrived via an affiliate link, the affiliate dashboard shows the credited amount. The affiliate's record and the brand profile's record may not match because they describe the same milestone from two angles. The brand profile documents the angle; the affiliate documents the credit.