Which number do you believe when a referral invite lands in a chat: the figure on the splash tile, or the figure that posts to the wallet three weeks later? The two are almost never the same, and the gap between them is what an investor needs to measure before any invite is sent or accepted. This evergreen read walks seven numbers a program can quote without breaking advertising law, four reconciliation checks that turn the tile into a wallet figure, and one final question that converts the whole exercise into a single send, decline, or defer decision.
The operational walk for applying, tracking, and disputing a code lives on the referral code guide. Everything below is portable. It works on any invite the reader meets next because the contract anatomy is the same across products, league cycles, and budget cycles. Examples throughout are clearly hypothetical. No live referral string, expiry date, payout figure, or platform offer is named. Verify every detail on your own device, under your own verified account, before any code is treated as a budget line.
What this read covers
- Why the splash tile is the marketing ceiling, not the wallet floor
- Seven numbers a referral program can legally quote
- Four reconciliation checks that convert a tile into a wallet figure
- The single question that turns any invite into a decision
- How to apply the same checks when you are the invitee, not the inviter
- A one-page checklist for the next invite that lands in a chat
Why the splash tile is the marketing ceiling, not the wallet floor
Two faces sit behind every referral invite. The first face is the splash tile: the banner, the social card, the chat preview. The second face is the contract: the program page, the terms link, the dispute policy. The two faces answer different questions. The tile answers the question "should the reader click." The contract answers the question "will the credit post." The answers are routinely different, and the difference is measured in numbers, not adjectives.
The gap is not accidental. A marketing team is paid to make the tile the highest number the program is willing to print in plain text. A finance or compliance team is paid to make the contract the smallest number the program is required to pay. Both numbers are true in their own place. The reader who reads only the tile accepts the ceiling as the floor. The reader who reads the contract accepts the floor as the ceiling. The investor reads both, writes down both, and treats the difference as the cost of believing a marketing claim.
That difference is the subject of the rest of this read. The seven numbers below are the figures a referral program can quote without breaking advertising law in most consumer jurisdictions. The four reconciliation checks are the bridge between the quoted figure and the wallet figure. The single closing question converts the bridge into a budget decision.
Seven numbers a referral program can legally quote
Each of the seven numbers below is something an investor will see in plain text on a splash tile, in a social card, or in a chat preview. Each one is true at the moment it is printed. Each one is also partial, and the partial nature is what makes the tile useful for marketing and useless for budgeting.
Number 1, the headline credit. The biggest figure on the tile. It is the maximum the program is willing to print in plain text, not the maximum the program will pay. A tile that reads "credit up to ₹X" is a ceiling, never a floor. The word "up to" is the marketing team's escape hatch, and it appears in nearly every referral splash tile in the category.
Number 2, the per-invite bonus. The figure attached to one successful invite. It is usually a fraction of the headline credit, and it is usually the only number the program contractually commits to paying. Read this figure next to the headline. A ratio of one to ten between the per-invite bonus and the headline credit is a common range across the category.
Number 3, the lifetime cap. The maximum the inviting account can withdraw from referrals across the program's life. The cap may equal one per-invite bonus, in which case every additional invite converts to a smaller tier, an in-product perk, or a marketing badge. The cap may equal three per-invite bonuses, in which case the fourth invite begins to shrink. Read the cap before the headline.
Number 4, the qualifying action probability. The share of invites that complete the contract's qualifying action. The tile never publishes this number. The number is whatever the invitee actually does. If the qualifying action is "first deposit above ₹X" and only one in three invitees deposits, the realised probability is one third of the per-invite bonus, before any cap or window rule.
Number 5, the window length. The period between invite acceptance and qualifying action completion. A window of thirty days is generous. A window of seventy-two hours is tight. A program that publishes no window has reserved the right to expire the credit at its discretion, and that moment is rarely the reader's preferred moment.
Number 6, the fund treatment. The kind of money that posts. Withdrawable cash posts as balance. Bonus funds post as locked credit that converts only after a playthrough rule is met. A marketing badge posts as a label with no balance behind it. The three look identical on the splash tile, and the difference between them is the difference between money you can withdraw and money you cannot.
Number 7, the dispute response time. The period between a written dispute and a verified answer. A program that answers in under forty-eight hours with a verbatim quote from the contract resolves disputes quickly. A program that answers in seventy-two hours with a generic template deflects them. A program that does not answer at all has shown what it will do in a dispute, and the choice is rarely in the reader's favour.
Read the seven numbers in order. Screenshot each one before any invite is sent. The screenshot gives the reader something to compare against later if the credit does not post, and it catches subtle shifts: a banner that read "credit up to ₹X" yesterday may read "credit up to ₹X for new users only" today, and the addition is the difference between the tile and the contract.
The seven numbers above are the figures a tile can legally print. The four checks below are what separate those figures from the figure the wallet will actually receive.
Four reconciliation checks that convert a tile into a wallet figure
The seven numbers are inputs. The four checks below are the arithmetic that turns the inputs into one realised figure, the kind of figure an investor can put into a budget row. Each check is portable, and each check takes under five minutes when the contract is open in another tab.
Check 1, cap versus invites sent. Divide the lifetime cap by the per-invite bonus. The result is the maximum number of paid invites the account can convert. Any invite sent beyond that number converts to a smaller tier or a marketing badge. An investor who plans to send more invites than the cap allows is planning to do work the program will not pay for.
Check 2, qualifying action versus invitee history. Apply the contract's qualifying verb to the invitee's known behaviour. If the verb is "first deposit" and the invitee is unlikely to deposit, the realised probability is zero. If the verb is "first verified play after KYC" and the invitee does not intend to complete KYC, the realised probability is zero. Be honest about the invitee. A discount rate of one hundred percent is the same as a credit of zero.
Check 3, window versus contact cadence. Compare the window length against the realistic time between sending the invite and the invitee acting on it. A seventy-two hour window is fine for an invitee who already planned to sign up. A seventy-two hour window is fatal for an invitee who needs a week to consider. A program with no published window is fatal for any invitee who needs more than a day.
Check 4, fund treatment versus withdrawal plan. Decide what the credit is for before the invite is sent. If the credit is meant to be a free contest entry, bonus funds with a playthrough rule may be acceptable. If the credit is meant to top up a withdrawal-eligible balance, only withdrawable cash counts. A program that posts bonus funds when the reader needed withdrawable cash has posted the wrong number, and no marketing copy will convert it.
Run the four checks in order, in a single sitting, before any invite is sent. The result is a single realised figure: the wallet number the program is likely to post, given a realistic invitee, a realistic window, and a realistic use of the credit. That figure is what goes into the budget. The headline figure goes nowhere.
The single question that turns any invite into a decision
The seven numbers and the four checks collapse into one question. The question is portable. It works on any invite the reader meets next, because the contract anatomy is the same across products.
Question, is the realised wallet figure still worth the social cost of asking a friend. Multiply the headline by the cap, the qualifying action probability, the window, the fund treatment conversion, and the probability that a dispute will resolve in the reader's favour if it arises. The product is the realised wallet figure. Compare it to the time it takes to ask a friend, the social cost of asking, and the time it takes to test the dispute surface before the invite is sent. If the realised wallet figure is positive and the social cost is acceptable, send the invite. If either side fails, decline politely and keep the friendship intact.
The question has one useful side effect. It forces the reader to test the dispute surface before the invite is sent, because the dispute probability is one of the multipliers. Open the program's customer-care channel. Send a short, polite question about the qualifying action, the window length, or the fund treatment. Time the response. A program that answers in under forty-eight hours with a verbatim quote from the contract passes the test. A program that does not answer in seventy-two hours, answers with a generic template, or refuses to confirm a written term in writing has shown what it will do in a dispute, and the choice is rarely in the reader's favour.
Run the question once, in a single sitting, before any invite is sent. A program that passes the question is a program worth the time. A program that fails the question is a program that has shown what it will do when the credit does not post, and the choice is rarely in the reader's favour.
A program that cannot answer one written question in three days cannot resolve a credit dispute in three weeks. The asymmetry is simple: a missed referral is recoverable, a disputed credit inside a hostile support channel is not.
How to apply the same checks when you are the invitee
The same seven numbers and the same four checks work in reverse. An invitee who has been asked to apply a code can run the same audit, on the same contract, on the invitee's own device, before any deposit. The qualifying verb becomes a check the invitee can actually meet. The window becomes a check the invitee can act inside. The fund treatment becomes a check on whether the credit will convert to cash the invitee can withdraw or remain locked in a playthrough the invitee does not intend to complete.
The invitee audit has one extra check. The invitee should ask whether the invite is real. Programs that publish no verifiable program page and no working customer-care channel are routinely used as pretexts for phishing, sideloaded APK installs, and identity-document harvesting. A reader who is being asked to install an app from outside the official store, to share an OTP, or to forward an identity document is being asked to participate in something that is not a referral program. Decline, screenshot the ask, and report it to the platform that hosted the invite.
The invitee who runs the same audit protects the same friendship from the same expensive surprises. The audit does not depend on the headline number, the platform name, the season, or the contest format. It depends only on the seven numbers a program can legally quote, the four checks that convert those numbers into a wallet figure, and the one question that converts the wallet figure into a send, decline, or defer decision.
A one-page checklist for the next invite that lands in a chat
Read the tile once. Screenshot the seven numbers. Open the contract. Screenshot the seven lines that bind the program. Send one polite question to the dispute surface. Time the reply. Run the four reconciliation checks. Decide on the basis of the realised wallet figure, not the headline. The whole loop takes fifteen minutes and protects both sides of the invite from the small, expensive surprises that referral programs are designed to hide.
The checklist works because the contract anatomy is portable. A reader who runs the audit on one program can run the same audit on the next program without relearning the frame. The audit does not depend on the headline number, the platform name, the season, or the contest format. It depends only on the seven numbers a program can quote without breaking advertising law, the four checks that turn those numbers into a wallet figure, and the one question that converts the wallet figure into a send, decline, or defer decision.
Next step
Take the seven numbers and the four checks to the next referral invite you receive, or to the program page of the next code you are asked to share. The operational walk for applying, tracking, and disputing a code lives on the referral code guide.
18+ only. Sponsored when commercial. Verify every detail on your own device.
Questions readers ask
Is the headline credit the same as the wallet figure?
Almost never. The headline credit is the figure the marketing team is willing to print. The wallet figure is what the contract commits to paying after the cap, the qualifying action, the window, and the fund treatment are applied. Run the four reconciliation checks on the contract before any code is treated as a budget line.
How long should a referral audit take?
About fifteen minutes for the first program. The seven numbers and the four checks are the same shape across products, so the second program takes less. The dispute-surface test takes the largest share of the time, and it is the check that catches the most expensive surprises.
What if the program page is silent on the lifetime cap?
Treat the missing cap as the program's worst-case interpretation. A program that has not published a cap has reserved the right to set one at the moment of withdrawal, and that moment is rarely the reader's preferred moment.
What if the household rule is silent?
Default to the most aggressive reading. Any shared IP, device, payment instrument, or browser fingerprint can collapse two accounts into one. Decline the invite unless both accounts are known to pass the strictest possible household test.
Does the qualifying action vary across programs?
Yes. The qualifying action is the single most variable line on the contract. Some programs count a free contest; others count only a paid contest; others count only KYC completion. Read the line, screenshot it, and treat the splash tile as decoration.
What if the credit posts as bonus funds?
A credit that posts as bonus funds is a budget line with conditions. Read the playthrough rule, the eligible-contest list, and the dispute window before treating the credit as withdrawable cash. A bonus-fund credit that does not complete the playthrough expires at zero realised value.
What if the customer-care channel does not reply in seventy-two hours?
Decline the invite. A program that cannot answer one written question in three days cannot resolve a credit dispute in three weeks. The asymmetry is simple: a missed referral is recoverable, a disputed credit inside a hostile support channel is not.
What if the invitee is in a restricted state?
Do not invite. The MeitY framework on online gaming and the Public Gambling Act, 1867 with state amendments still govern the legal landscape, and a referral credit cannot post on an account the product has blocked at the jurisdiction level.