Most sports offers are easy to read at a glance. Welcome credits, trial bundles, ticket packages and stadium deals all arrive with a single headline figure and a small-print page that addresses one person. A code-based offer does not quite work that way. The moment the registration form asks for a refer code, the small print has to address two: the person typing it in, and the person who gave it. The headline still belongs to one party. The terms quietly govern both.
What follows is a working checklist for readers who are about to type a code into a sports-offer form, or who are about to send one to a friend. It treats the invitee and the inviter as two separate readers, each with their own eligibility, their own clock and their own redemption path, while sharing a single total-cost calculation and a single set of cancellation rules. Examples and figures below are labelled as hypothetical throughout. No current offer, price, code, expiry date or live promotion is referenced.
Why a code turns the offer into a two-sided agreement
When a registration form contains an optional code field, the offer is no longer a simple credit. The credit attaches to a relationship. The platform records who invited whom, what action the invitee took to qualify, and when the inviter's reward was paid. That record is what the offer's terms are written against, even when the marketing copy speaks only to one side.
The practical consequence is that a reader comparing two offers with codes should compare three things rather than two: the invitee's package, the inviter's package, and the joint verification step that ties them together. The third item is usually the smallest in the marketing and the largest in the small print. A reader who reads only the marketing will see two clean offers. A reader who reads the small print sees one offer that is shared across two accounts and three verification moments.
Three facts from the editorial desk frame the rest of this piece. An offer can carry eligibility and verification conditions. Expiry dates and redemption paths affect whether an offer can be used at all. A careful comparison of total cost, exclusions and cancellation terms is worth doing before any commitment. Each of those three facts is the same whether the offer is a code-based referral or a venue deal — but each one is more awkward when a code is in the picture, because two readers have to clear it instead of one.
Three ground rules before you read any offer
Before walking through the side-by-side checklist, keep three ground rules in mind. They are not offer-specific. They apply to every welcome credit, trial bundle and venue deal, with or without a code field.
- Read the published terms, not the marketing copy. Headline figures describe the best case. The published terms describe the average case. When the two disagree, the terms govern.
- Treat the offer as a filter, not a decision. An offer either clears the filter or it does not. The comparison is not "which offer do I prefer" until each offer has cleared every filter individually.
- Walk through the redemption path before signing up. Imagine clicking every required button in the order the offer describes. If the path involves three sub-menus and a customer-care ticket, the friction is real and worth pricing in.
These three rules apply to the invitee and the inviter in equal measure. They are particularly useful for the inviter, who is often one step removed from the registration screen and therefore more likely to take the headline on trust.
The invitee's checklist
The invitee is the reader typing the code into the form. Their checklist has six items. The order matters: an offer that fails item one should not be evaluated against items two through six.
- Confirm the invitee is eligible. Most code-based offers restrict eligibility to first-time account holders, to specific regions or to particular age ranges. Read the offer's own definition of a new customer before assuming the offer applies.
- Confirm the country list. A deal published for readers in one jurisdiction may not be available to readers in another. The platform's published terms will say so, and the check is faster than the support ticket that results from skipping it.
- Read whether the code field is optional. Some forms accept an empty code field. Others make it mandatory. If the field is optional, the invitee can still get the standard welcome package by leaving it blank. That choice changes which offer is being compared.
- Confirm whether the code is case-sensitive. Most platforms publish the case sensitivity of a code in the help pages rather than the offer page. A typo at registration is usually the difference between a credited bonus and a quiet loss.
- Confirm whether the code is locked once accepted. Many platforms describe the registration moment as final. Once a code is typed and the account is created, swapping it later is either impossible or handled by support on a case-by-case basis. Read what the offer says before the form is submitted.
- Confirm whether the credit pays out before or after verification. The bonus may land immediately on registration, or it may wait for an identity check. The wait changes the effective value of the credit on day one.
Run these six checks against the offer before any other filter. An invitee who is not eligible, in the wrong country, or stuck with a mistyped code is not in a comparison at all.
The inviter's checklist
The inviter is the reader who shared the code. Their checklist is shorter but more dependent on the invitee's actions. The inviter does not control whether the invitee clears each step, but they should know what the invitee has to clear before the reward is paid.
- Read the trigger for the inviter's reward. Many inviter rewards pay out only when the invitee completes a defined action: a verified account, a first deposit, a first entry, a minimum stake, or a fixed holding period. The headline number is real, but only after the trigger fires.
- Read whether the inviter's reward mirrors the invitee's. Some platforms pay both sides equally. Some pay the inviter a smaller amount. Some pay the inviter only after the invitee has used the credit. Symmetry matters because it determines whether the offer is genuinely a two-sided deal or a one-sided deal dressed up with a code.
- Read the per-household rule. Most code-based offers describe the offer as a per-household, per-device or per-payment-method arrangement. The check protects the offer from being abused by multiple accounts at the same address. The same rule also protects the inviter from a voided bonus if anyone in the household is later judged to have abused the offer.
- Read the inviter's use-by clock. The inviter's reward may have its own expiry, separate from the invitee's. A reward that lands and expires inside thirty days is not the same offer as a reward that lands and expires inside ninety.
The inviter's checklist is small but slow. The inviter cannot see what the invitee is doing in real time, and the platform's notification system is not always instant. Read the trigger language carefully so the inviter knows when to expect the reward and when to ask support about a delay.
Two expiry calendars, not one
Code-based offers carry two expiry clocks running at the same time. A reader who watches only one of them will be surprised by the other.
The invitee's calendar has three moments. The registration window is the period during which the code can be used at all. The use-by date is the period during which the credited bonus remains usable. The payout schedule describes when each instalment of the bonus is released. All three can be different. A four-week registration window with a two-week use-by and a four-week payout window is a meaningfully different offer from a four-week registration window with a four-week use-by and an instant payout. The differences are not visible from the headline.
The inviter's calendar is usually shorter. The inviter's reward may expire within thirty days of the invitee's qualifying action, or within ninety days of the original code share. It may also depend on the invitee staying active. Read the inviter's use-by language in the same paragraph as the trigger language, because the two clauses frequently appear apart from each other.
Tracing the redemption route on each side
Redemption is the path between being credited and being able to use the credit. The path on each side of a code-based offer is rarely the same. The invitee's path usually involves the platform's wallet and a contest entry. The inviter's path usually involves a notification and an account credit. Tracing both paths is what separates an offer that pays out from an offer that merely exists.
- Where does the invitee's credit land? Some bonuses credit a wallet that can be spent like cash. Others credit a fixed free entry in a specific contest, with no conversion path. Read where the credit is deposited before assuming flexibility.
- Where does the inviter's credit land? The inviter's reward is usually credited to the inviter's account as a balance, sometimes as a free contest entry, occasionally as a marketplace credit. Each form carries its own withdrawal rules.
- What must be true to redeem either side? Minimum stake, minimum deposit, minimum lineup, identity verification, or a holding period may apply. Read the conditions at the moment of redemption, not just at the moment of registration.
- Can either credit be withdrawn as cash? Welcome credits can take several forms, and the conversion rules are usually written separately from the credit rules. Read both clauses for both sides.
The practical test is the same on both sides. Imagine you want to redeem the credit on day one. Walk through every click required. If the path on either side involves three sub-menus and a support ticket, the friction is real and worth pricing into the comparison.
Cost symmetry: who pays, who earns
Headline numbers ignore the cost of accepting the offer. On a code-based offer, cost has to be calculated twice. The invitee pays whatever the offer requires to unlock the credit: a deposit, a minimum stake, a subscription opt-in, or an identity-verification queue. The inviter pays whatever the inviter-side verification requires, which is usually nothing at all but is occasionally a maintenance action on the inviter's own account.
Worked shape of a hypothetical invitee calculation, with every figure labelled as illustrative:
- Invitee headline value: €40 welcome credit (hypothetical).
- Invitee required minimum deposit to unlock: €20 (hypothetical).
- Invitee required use threshold before withdrawal: a defined figure in the offer's terms (hypothetical).
- Invitee subscription opt-in at registration: €4 per month, cancelled in month two (hypothetical).
- Invitee net day-one position, before any play: €40 − €20 − €8 = €12 (hypothetical).
- Inviter headline value: €20 referral credit (hypothetical).
- Inviter required action: invitee must clear the same use threshold (hypothetical).
- Inviter net day-one position: €0 until the invitee clears the trigger, then €20 minus any conversion friction (hypothetical).
- Joint day-one cost, both sides combined: €20 deposit + €8 subscription opt-in = €28 (hypothetical).
- Joint day-one value, both sides combined: €40 + €20 = €60, conditional on both triggers firing (hypothetical).
The arithmetic is illustrative. The point is that headline value rarely survives a full cost build on either side, and the joint value is conditional on both triggers firing inside both clocks. Repeat the build for every offer you are comparing. Only the offers with a net position you are comfortable with on day one deserve a deeper look.
Exclusions that catch referrals out
Code-based offers have a small set of exclusions that recur across platforms. They are worth knowing by name, because the offer's small print uses slightly different words for each.
- Payment-method exclusions. Welcome bonuses often exclude e-wallets and prepaid cards from the qualifying deposit. If the invitee's chosen deposit method is on the list, the credit does not pay out. Read the list before funding the account.
- Self-referral clauses. Most platforms explicitly forbid the invitee and the inviter from sharing the same household, IP range or device fingerprint. The clause is enforced retroactively when the platform's system flags the match.
- Contest eligibility. A credit redeemable in classic contests may not be redeemable in headline tournaments. The headline credit and the headline tournament may be deliberately kept apart.
- Cancellation window. The offer's terms usually describe a window during which the invitee can change their mind. Read the window carefully. If the window is shorter than your cooling-off period, factor it in before you accept.
- Bonus-abuse clauses. Platforms retain the right to void a bonus if they suspect abuse. Read the offer's own definition of abuse. It can be wider than common sense suggests, and the risk is paid in the invitee's account history, not the inviter's.
Venue deals have their own exclusion patterns that occasionally overlap with code-based offers. Ticket bundles can be non-refundable. Hospitality packages can carry a minimum spend. Read each exclusion line, then decide whether the offer still makes sense at the price you would actually pay.
A worked comparison, labelled hypothetical
Below is a side-by-side comparison of two imaginary referral offers. Both are labelled as hypothetical. Use the same shape when comparing actual offers. The point is the symmetry, not the specific numbers.
Hypothetical Offer R · €40 invitee credit and €20 inviter credit. Invitee requires a €20 deposit and a verified account. Inviter's reward triggers once the invitee clears the verification step. Use-by clocks: invitee fourteen days from credit, inviter thirty days from invitee's verification. Cancellation window: seven days from registration for the invitee. All numbers are illustrative only.
Hypothetical Offer S · €60 invitee credit and €15 inviter credit. Invitee requires a €40 deposit, a verified account and a first contest entry. Inviter's reward triggers once the invitee clears the first contest entry. Use-by clocks: invitee thirty days from credit, inviter sixty days from invitee's first entry. Cancellation window: fourteen days from registration for the invitee. All numbers are illustrative only.
For an invitee who plans a short, focused signup window, Offer R delivers a cleaner net position on day one: €40 against €20 of mandatory deposit, with verification as the only step before the inviter's reward pays. The clocks are tighter on both sides, so the offer rewards quick action.
For an invitee who plans a longer build-out and an inviter who wants a longer wait, Offer S may be worth the friction: a higher invitee credit, a longer use-by window, and a longer inviter payout window — at the cost of a higher deposit and an additional qualifying step. The headline alone would have suggested Offer S is better. The rebuilt comparison shows it is only better on specific axes.
Neither offer is real. The point of running the comparison is not to choose one. It is to demonstrate that headline figures, code-based or not, are not enough on their own. Real offers rarely publish their numbers as clearly as the two hypothetical ones above, which is why a checklist is more useful than any single number.
The same bilateral checklist applies to every code-based fantasy offer, including the one described on the Sorare invite-program chapter. Walk through eligibility on both sides, expiry on both sides, redemption on both sides, and the joint cost build before anyone types or shares a code. The framework above is meant to be reused, not memorised.
Editorial commentary only. This article is an evergreen explainer and does not name any current offer, price, code, expiry date, brand partnership or live event. Worked examples and individual figures are labelled as hypothetical throughout. Always read the platform's published terms before accepting any offer or sharing any code. The checklist above is a reading aid, not a substitute for the offer's own small print.
FAQ
Does a code-based offer change the eligibility check?
Yes. A code adds a second reader to the offer — the inviter — which means the platform has to verify both sides before paying out either credit. The eligibility check is therefore broader than it is for a code-free offer, and the verification moment is shared between the two accounts.
Can a code be changed after registration?
Usually no. Most platforms describe the registration moment as final and treat the code as locked once the account is created. Some platforms will adjust on a case-by-case basis through support. Read the offer's own language on this point before submitting the form.
What triggers the inviter's reward?
The trigger is written in the offer's terms and is usually one of: a verified invitee account, a first qualifying deposit, a first contest entry, or a fixed holding period. Read the trigger before sharing the code, so the inviter knows when to expect the reward.
Are the invitee and inviter rewards always equal?
Not always. Some platforms pay both sides equally. Others pay the inviter a smaller share, or pay the inviter only after the invitee has used the credit. Read both sides' headline numbers separately rather than assume symmetry.
Do venue deals and ticket bundles follow the same checklist?
They follow the same shape. Eligibility, expiry, redemption, total cost and exclusions apply to every welcome credit, trial bundle and venue deal. The bilateral step only matters when a code is part of the offer.
Should the invitee or the inviter read the terms first?
Both. The terms are written as one document but cover two accounts. The invitee reads for eligibility and the registration step; the inviter reads for the trigger and the payout window. Each side catches what the other misses.