The team-builder decision is over. The captain pick is locked, the role buckets are filled, the credit cap is respected, and the contest entry fee is ready to be funded from the wallet. At that moment a second decision arrives in the form of a welcome bonus, a free-credit push notification, or a season-ticket bundle forwarded by a friend. Each of those offers behaves like a small financial product rather than a marketing sticker. The rules that gate who can claim it, the clock that decides how long it survives, the path that turns the credit into a contest entry, the rupee amount the team-builder ultimately pays, the fine-print exclusions that quietly void the credit, and the cancellation terms that decide what happens when the plan falls apart — those six conditions are what differentiate a real bonus from a banner.
The six questions below are not a checklist to memorise. They are a sequence to run, in order, the first time a bonus lands on a welcome screen and the second time, when a different bonus replaces it. Eligibility prunes the offers the team-builder cannot use, expiry prunes the offers that will expire before the team-builder uses them, and the remaining four questions decide which surviving offer is actually the best deal. A bonus that survives all six is worth taking. A bonus that fails any one of them is worth skipping, regardless of how clean the headline number reads on the banner.
The signup moment is when the offer stops being free
The marketing copy on a fantasy cricket welcome screen reads like a gift. The terms of service read like a contract, because they are one. Between the two, the team-builder holds the decision: tap the signup button, enter the bonus code, fund the deposit, and the headline number is yours to use or lose. Every welcome screen on the Indian fantasy cricket market is built to collapse the time between seeing the bonus and committing the deposit, and the collapse is the product. The framework inverts that collapse. The notes you take before the welcome screen opens are the notes that decide whether the bonus is worth the deposit it unlocks.
For an Indian fantasy cricket team-builder, the comparison is also bound by a layer that other sports offers do not face. State rules fix which contests are accessible, age rules fix who can fund a wallet, and KYC rules fix who can withdraw any winnings the bonus helped earn. Any offer that ignores that layer is an offer the team-builder cannot use, regardless of how clean the headline reads. The Indian fantasy cricket desk on Exchange22 India treats that layer as the first filter in every comparison, before the welcome screen opens and before the bonus code is typed. The check is mechanical, and it removes the most expensive class of comparison errors before the small print is read.
Eligibility: which offers even apply to your account?
Eligibility decides whether the offer reaches the wallet at all. For a digital sign-up bonus, eligibility is a chain of small conditions: state, age, KYC status, payment instrument, and prior account history. The team-builder who passes all five is eligible. The team-builder who fails one is not, and the welcome screen will not flag which one failed. The eligibility chain is the first place the offer either arrives in the wallet or fails silently, and silent failure is more common than the marketing copy admits.
For a trial credit on the same platform, eligibility is narrower still. The credit is locked to a single PAN, a single Aadhaar, a single device fingerprint, and a single payment instrument. A previous account on the same platform voids the credit. A device shared with a previous claimant voids the credit. A repeat-KYC mismatch voids the credit. The credit is non-transferable, so the eligibility list is one name, and that name has to match the PAN, the Aadhaar, the device, and the payment instrument exactly. For a venue deal, eligibility moves to a different chain: a named attendee, a photo ID at the gate, a group size for hospitality, a calendar of matches that may overlap with another commitment. The eligibility check is the cheapest of the six questions, and skipping it is the most expensive mistake a team-builder can make.
Expiry: find out where the clock starts before you click
Expiry windows are where most bonuses quietly go to die. The countdown clock for a fantasy cricket offer can start from one of three trigger points: the moment the account is registered, the moment the first deposit clears, or the moment the first contest entry is submitted. A bonus that reads "valid for 14 days" on a welcome screen without specifying the trigger is a marketing decision dressed up as a transparency feature. Trial credits that start counting from registration frequently expire before a new user finishes KYC, because PAN verification alone can take 24 to 48 hours and Aadhaar linking another 24 hours on top of that. The credit sits live in the wallet but is already past its use-by date by the time the team-builder is ready to enter a contest.
The rule the fantasy cricket desk applies is simple: the validity window has to be at least three times the realistic onboarding window before it becomes worth claiming. Onboarding that takes 48 hours means a 6-day minimum. Onboarding that takes 72 hours means a 9-day minimum. A 48-hour trial credit is almost never worth claiming because onboarding eats most of the redemption window. A 14-day trial credit leaves enough headroom to use the credit deliberately, after the captain pick is locked and the contest fee is funded. For a venue deal the unit changes from hours to fixture dates: a season-ticket bundle should be measured against the matches the team-builder will actually attend, not the matches the team-builder would theoretically like to attend.
Redemption: how the bonus turns into contest entries
Redemption is the question that exposes bonuses hiding behind identical headline numbers. The mechanics vary by offer shape. A fantasy cricket welcome bonus usually lands in the wallet the instant the deposit clears, but the redemption route then runs through a wagering multiple, a list of eligible contest types, and a minimum team-size requirement before any withdrawal unlocks. A trial credit on a ticketing site can be tied to a single stand block, a single match, or a single price tier, with no path to upgrade to a better seat. A stadium hospitality pack can demand pre-ordered catering, a separate travel booking, and a photo ID check at the gate. Redemption is the second test of whether the offer is actually usable, and it catches more team-builders than the eligibility check does.
The practical test is short. For digital offers, ask whether the bonus fires automatically or needs a code, and whether the wagering multiple applies to the deposit or to the bonus value. For venue deals, ask whether the redemption window sits inside the bundle or requires a follow-up booking, and whether the bundled hospitality is refundable on partial use. For trial credits, ask whether the credit is consumed in one contest entry or split across several, and whether it funds contest entry directly or only credits the wallet. The more transparent the redemption path, the tighter the gap between the banner number and the amount the team-builder actually keeps. The more opaque the path, the wider that gap grows, and the more the comparison needs to lean on the headline-to-wallet delta rather than the headline alone.
Total cost: what you actually pay in rupees
Total out-of-pocket cost is the question that converts a comparison into a single rupee number. Take the headline bonus, deduct the minimum deposit needed to unlock it, deduct the wagering requirement expressed as a percentage of the deposit, add whatever the bank or wallet charges as a payment-instrument fee, and add the time cost of completing the bonus conditions. The output is the real rupee cost of the bonus. Two offers with identical headlines can sit 20 to 40 percent apart on that single number once the full calculation is done. The widest gaps usually show up where one offer needs a single deposit and another demands recurring top-ups, or where one offer allows any contest and another locks the bonus to a specific contest category, because a recurring deposit cycle or a restricted contest re-prices the cost across every matchday of the season.
For venue deals the arithmetic is the same but the line items differ. Start with the ticket price, deduct the value of the bundled food and beverage, deduct the value of any included parking or transit, add the booking fee, add any non-refundable component, and then deduct the implicit cost of attending the match itself, including travel time and time off work. A season-ticket bundle that covers a T20 in the team-builder's city delivers more value than the same bundle tied to matches the team-builder would skip, even when the headline price is identical. The cheapest offer is the one where every line item is something the team-builder would have paid for anyway, with the bonus as a bonus rather than as a budget. The most expensive offer is the one that pulls the team-builder into a recurring deposit cycle to clear a wagering multiple, or into a bundle that forces attendance at matches the team-builder cannot reach.
Exclusions: where the bonus quietly stops working
Exclusions are eligibility written backwards. Where the offer will not work is almost always longer than the list of where it will work, and almost always hidden deeper in the small print. Most readers scroll past the exclusions section because it reads like boilerplate, and that is exactly where the offer quietly fails. On digital fantasy cricket platforms the common exclusions run along these lines: contests whose entry fee sits above a stated ceiling, any withdrawal submitted before the wagering multiple is cleared, accounts that have already redeemed a sister-platform bonus in the same window, and specific payment rails such as netbanking, prepaid wallets, or cards issued outside India. For venue deals the exclusions usually cover high-demand fixtures, seats outside the selected price tier, and add-ons like hospitality catering or parking that are priced separately on the day.
Reading the inclusions and the exclusions side by side on a single page is the cleanest way to keep the comparison honest. A match-day pass that excludes a marquee fixture is a different product from one that includes it, even when the price tag is the same. A welcome bonus that excludes contests above a threshold is a different offer from one that includes premium contests. A venue bundle that strips out parking is a different bundle from one that includes it, even when every other line of the package looks identical. Most of the disappointing experiences with sports offers trace back to a clause that was visible on the page but never read. Pulling the exclusions list onto a notepad before the signup button is tapped cuts that error rate sharply, and forces the comparison to be a like-for-like exercise rather than a banner-to-banner one.
Cancellation: what happens if the plan falls apart
Cancellation terms decide what happens when the plan changes after the deposit has cleared. The most team-builder-friendly offers let the user opt out without forfeiting the deposit, but most offers fall short of that bar. At the strict end of the scale, the bonus is voided the moment the user cancels, and any portion of the bonus already used is reversed against the wallet balance. Mid-tier digital sports offers usually sit in the middle: the bonus itself can be cancelled, but the deposit stays locked until KYC and a withdrawal-waiting period have both cleared. Venue deals almost always carry non-refundable components, particularly for marquee fixtures and weekend derbies, and a small number of bundle transfers require a notarised request that takes longer than the contest window allows.
The cancellation question sits last in the framework because it is the one that only matters once something has already gone wrong, but it is also the one that decides what the offer costs the team-builder in the worst case. If a work shift pulls the team-builder away from a match, can the ticket be transferred to a friend or family member? If a fantasy contest is cancelled for rain, does the bonus return to the wallet or stay locked? If the offer's terms are revised mid-window, can the deposit be withdrawn without losing the credit the team-builder has already earned? Reading these lines before signup feels excessive, almost paranoid, but it is the single best defence the team-builder has against losing both the deposit and the credit. The offers that pass the cancellation check are almost always the same offers that pass every other check, and that cross-check is the most reliable signal of all when three or four offers are being compared in the same sitting.
Three worked offers, side by side on the six questions
The snapshot below sketches what the six answers look like for each offer shape in practice. The numbers are illustrative — every operator publishes its own terms, and the small print at the moment of signup is the only place that matters. Treat the snapshot as a prompt for the questions to ask, not as a substitute for the actual answers in the fine print.
Imagine a welcome bonus on a fantasy cricket app landing in early March, before the IPL 2026 season starts. Eligibility narrows down to state rules plus age plus KYC plus the payment instrument on file; expiry usually runs seven to thirty days from the first deposit; redemption fires automatically once the deposit clears and the wagering multiple is met; total cost has to absorb the minimum deposit and the 1x to 3x wagering requirement on top; exclusions typically carve out contests above a stated entry ceiling and certain payment rails; cancellation usually returns the deposit but voids any unused credit. Compare that with a trial credit push notification tied to a marquee IPL or Test match: eligibility is the same chain but tighter, redemption happens in a single contest entry, expiry shrinks to three to seven days from notification, and the credit disappears the moment it is consumed. Compare both again with a venue bundle arriving through a franchise ecosystem: eligibility shifts to a named attendee and a photo ID, expiry is the fixture calendar in the bundle, redemption requires a separate booking through the box office, total cost adds travel, food, and time off work, exclusions often carve out the marquee fixture the team-builder wanted most, and cancellation is almost always non-refundable after the lock-in window.
When the calendar around the offer matters as much as the offer
The cricket calendar decides which offers are realistic to compare in any given week, and that shapes the framework more than most team-builders realise. IPL welcome bonuses usually land in the weeks before the new season begins, so the comparison is genuinely between competing deposit-match offers from rival platforms. Trial credits and free-entry pushes tend to arrive mid-season, attached to a marquee IPL or Test match, so the comparison is between a free credit and the contest entry fee the team-builder was going to fund anyway. Venue bundles tend to arrive through the franchise ecosystem, with the team the team-builder supports offering hospitality passes, charter experiences, or season-ticket renewals for matches in the team-builder's city, so the comparison shifts to whether the bundle matches the matches the team-builder will actually attend. Running the six-question framework against each of those calendar windows is the difference between a bonus that lands cleanly in the wallet on a Saturday night and a credit that expired while the team-builder was still verifying a PAN.
The same framework holds for shorter windows elsewhere in the cricket calendar. The Hundred in July and August triggers trial credit pushes on platforms that run UK-style contests. The T20 World Cup in 2026 produced a wave of cross-platform offers, with some platforms reserving bonus credits for tournament-built squads only. The Asia Cup and the bilateral series produced single-match trial credits that lasted 48 to 72 hours from notification. None of these offers is worth chasing on the headline number alone. The framework is the same regardless of the format, and the framework is what decides whether the offer is worth using or worth skipping, regardless of when the calendar delivers it.
What a clean comparison looks like the next time a welcome bonus lands
A clean comparison produces a single rupee number, not a list of pros and cons. Convert every offer into that single number by subtracting the expected reward from the estimated deposit across a realistic usage window, then adding the verification cost, the payment-instrument fee, and the time cost of meeting the conditions. The number that survives the conversion is the real value of the offer. Compare the real values, not the headlines, and the choice falls into place without the marketing team in the room.
The four-step normalisation is the cleanest way to run that conversion. Step one, standardise the duration: if one offer is fourteen days and another is thirty days, convert both to a per-day value before comparing. Step two, standardise the requirements: if one offer needs a single deposit and another needs a recurring deposit, convert both to a single-deposit equivalent. Step three, standardise the exclusions: if one offer excludes premium contests and another does not, subtract the premium value from the headline before comparing. Step four, standardise the cancellation: if one offer returns the deposit on cancellation and another does not, subtract the cancellation value from the headline. The number that survives all four normalisation steps is the number that should drive the choice, and the team-builder who follows the four steps usually finds the headline bonuses collapse into a much narrower band than the welcome screens suggest.
Before you tap the signup button tomorrow
Run the six questions in this order before committing to any bonus on a fantasy cricket welcome screen: eligibility, expiry, redemption, total cost, exclusions, cancellation. The order is not a stylistic preference; it is a filter chain, where each question prunes the offers that fail it. If any one of the six returns an answer that turns the bonus into something the team-builder would not have chosen deliberately, the offer stays on the table and the comparison moves on. The strongest offer is the one that survives all six checks, because surviving all six means the bonus is not the reason the team-builder signed up: the team that was just locked is.
The simplest final check is the one that catches the marketing team every time. Would the signup button get tapped if the bonus were ten percent smaller? If the answer is no, the bonus is doing the decision-making, and the team-builder should not be making decisions that a welcome bonus can move on the team-builder's behalf. A clean comparison leaves the choice with the team-builder, not with the operator that built the offer. The same rule applies to the credit push notifications during a Test series, to the franchise bundle sitting unread in the inbox, and to the welcome screen that opens the moment a new app launches. The framework is the same. The headline is the last input, never the first.