Awarded referral: how it works in practice

What is a referral rewards program?

Referral rewards is a mechanism in which one person recommends a company to another and receives a reward if the referral meets the stated conditions. In some programs, the referred person also receives a benefit. The reward should not be granted solely because an invitation was sent: usually it is necessary to identify the source, register the referred person, confirm a qualifying action and wait for validation.

In practice, the flow connects four elements: the referring participant, the referred person, a reference that links the two — such as a code or link — and a rule that defines when the conversion is valid. Registration, purchase, confirmed payment, account activation or minimum retention are examples of possible qualifying actions.

How does a referral rewards program work?

The operation can be summarized in eight steps:

1. The participant joins the campaign: they meet the eligibility criteria and accept the applicable rules.
2. The system generates a reference: a code, link, QR Code or invite identifies the referrer.
3. The reference is shared: the participant sends the invitation through the allowed channels.
4. The referred person is identified: they access the link, provide the code or enter through another traceable flow.
5. The referred person completes the qualifying action: they perform the event defined in the terms.
6. The referral goes through validation: the program verifies eligibility, payment, duplication, cancellations and signs of fraud.
7. The reward is released: after approval and the stipulated period, the benefit becomes available.
8. The participant uses or redeems the benefit: according to the campaign’s format, validity and restrictions.

Between steps, the status may be “sent”, “registered”, “pending”, “under validation”, “approved”, “rewarded”, “cancelled” or “rejected”. Names vary, but they must represent objective events so participants and the team understand what happened.

Code, link or invite: how to identify the referral

The referral code is an identifier associated with the referrer. When the referred person provides that code during registration, purchase or another permitted moment, the system records the relationship between the two people.

A referral link contains that reference in the URL itself. By clicking it, the referred person is directed to a page or flow where the source can be registered automatically. The QR Code usually points to the same type of link, while an invitation sent via a form can associate the referral to an email, phone number or other identifier.

Each format has attention points:

• Code: works across different channels, but can be mistyped or forgotten.
• Link: reduces manual input, but can lose attribution if the user switches devices, blocks tracking or completes the action by another path.
• QR Code: facilitates in-person use, but still depends on the destination flow and the same attribution rules.
• Contact invite: records the intent before conversion, but requires care with privacy, consent and unsolicited communications.

The terms should explain which reference prevails when more than one person refers the same contact. The first invitation, the last link used or another documented criterion may apply. Without this rule, two people might expect a reward for the same conversion.

What makes a referral valid?

A valid referral is one that simultaneously meets the criteria defined by the campaign. Sending a link or code alone is usually not enough.

Rules may check:

• whether the referrer is eligible and properly registered;
• whether the referred person is truly new or meets the reactivation criterion;
• whether the reference was recorded within the deadline;
• whether the qualifying action was completed on the channels, product and period provided;
• whether payment was approved and not refunded;
• whether the data does not match the referrer’s;
• whether the referral respects limits per person, campaign or period;
• whether there is no duplication, manipulation or violation of the terms.

The qualifying action should reflect the outcome the company intends to recognize. For a store, it can be the first paid purchase; for a recurring service, the subscription followed by a minimum active period; for a platform, account activation with a usage action. Registration is not synonymous with a customer, and an authorized payment is not always synonymous with definitive revenue.

When should the reward be released?

The reward should be released after the qualifying action can be confirmed and the main reversal risks have been addressed. The exact timing depends on the business cycle.

An e-commerce may wait for payment confirmation and the period necessary to identify cancellations or returns. A subscription may require a minimum retention. A B2B operation may validate contract, onboarding or first invoice. The important thing is that the waiting period is proportional to the risk and communicated before the referral.

Release can occur in two phases:

1. Pending reward: the action was recorded, but still awaits confirmation or the safety period.
2. Available reward: the referral was approved and the benefit can be used or redeemed.

Showing a pending balance helps provide visibility without preempting a benefit that may need to be cancelled. Communication should indicate the reason for the wait and the applicable estimate, avoiding promising a date that depends on events not yet completed.

Rules for cancellation, chargeback and expiration

The terms need to anticipate what happens when the conversion is reversed. If the referred person cancels the purchase before approval, the referral may be closed without reward. If the reward has already been released and the transaction is later charged back, the campaign must define whether the balance will be reversed, blocked or handled otherwise as permitted.

Some situations that deserve an express rule are:

• full or partial cancellation of the purchase;
• product return or service withdrawal;
• payment failure, dispute or chargeback;
• plan change or reduction of the contracted amount;
• referral approved due to operational error;
• account closure or suspension for fraud;
• reward validity and destination of expired balance;
• end of the campaign with referrals still pending.

Expiration should also be visible. The participant must know how long they can use points, credits, coupons or other benefits and receive notice compatible with the operation. Changing conditions after participation without addressing ongoing referrals can cause conflict and loss of trust.

How to reduce self-referral, duplication and fraud

Self-referral occurs when someone attempts to act as both referrer and referred to receive the reward. Duplication appears when the same person, account or transaction is attributed more than once. Frauds can also involve fake identities, multiple accounts, simulated purchases, automations, mass sharing or use of third-party data.

Controls can include:

• comparison of CPF, CNPJ, email, phone, payment account or other appropriate identifiers;
• unique reference for referral and transaction;
• blocking rewards for existing customers, when that is the rule;
• limits per participant, referred person, device, period or campaign;
• safety period before release;
• review of spikes, repeated patterns and related registrations;
• change logs and approval for manual adjustments;
• possibility to suspend and review cases without presuming guilt automatically.

More control does not mean collecting data indiscriminately. The company must use information necessary and compatible with the purpose, restrict access, define retention and inform the processing of personal data. If the participant provides third-party data to invite them, the flow needs to be assessed with special care.

How to communicate status to participants

A good referral campaign does not only communicate the final reward. It informs progress and allows the person to understand why a referral has not yet been approved.

Portal, app, email, WhatsApp or other channels can be used depending on the operation and applicable permissions. Regardless of channel, messages should use the same terms as the terms and conditions. If the interface says “approved” and support says “under review”, the program loses credibility.

Hypothetical example of a complete flow

Consider a fictional company called Example Store. The numbers and conditions below are illustrative only and do not represent Smartbis rules or recommendations for any business.

1. Customer Ana accepts the terms and receives the unique code ANAEXEMPLO.
2. Ana sends her referral link to Bruno.
3. Bruno accesses the link, creates a new account and the source becomes associated with Ana.
4. The terms determine that the referral will only be valid after the first paid purchase that is not cancelled during the validation period.
5. Bruno makes the purchase. Ana’s dashboard shows “pending referral”, without releasing the benefit immediately.
6. The system verifies payment, link, duplication, eligibility and any cancellations.
7. When the period ends and the purchase remains, the referral changes to “approved”.
8. Ana receives the defined benefit, with information about validity and usage.
9. If Bruno cancels within the stipulated period, the status changes to “cancelled” and the reward is not released.

The example shows why linking code, event and status matters. Without it, the company cannot explain the decision or reconcile the reward with the conversion.

Referral rules checklist

• Who can refer?
• Who can be referred and what does “new customer” mean?
• How will the code, link or invite be attributed?
• Which referral prevails when multiple invites exist?
• What action turns the invite into a valid referral?
• What is the deadline for the referred person to complete that action?
• How long can validation take?
• What reward applies to each participant?
• When and how is the benefit released?
• What is the validity and where can it be used?
• What happens in cancellation, return or chargeback?
• What limits apply per person and period?
• How will self-referral, duplication and fraud be handled?
• Which data will be used and how will privacy be protected?
• Which statuses will be displayed and how to dispute a decision?
• What happens to pending referrals at campaign end?

This checklist covers the mechanics. To define objectives, audience, budget, incentive and launch, consult the guide on how to plan a referral program.

A clear flow protects the experience and the reward

A referral rewards program works when the company can link a participant to a referred person, recognize the qualifying action, wait for validation and release the benefit according to rules previously communicated. Code and link facilitate attribution, but do not replace eligibility criteria, chargeback handling, fraud prevention and status communication.

If the operation needs to centralize invites, registrations, benefits and tracking, learn about Smartbis’s referral program solution. Available features depend on program configuration; the platform supports the flow, while rules and outcomes remain tied to the company’s decisions.