Interactive journey
Referral is easier to understand as a story than as a set of endpoints. The walkthrough below runs a complete referral end to end — the referrer finds their code, shares it, the friend receives it, applies, gets activated, and both sides land their reward.
Use Next to advance, Restart to start over.
Open the walkthrough full screen ↗
The walkthrough is a self-contained animation. The bank, the app, the customers and the referral code in it are fictitious, and nothing it shows calls a real Cheggout environment. It illustrates the sequence — not the exact screens your channel will be provisioned with.
What each step maps to
| Step | What you see | What is actually happening |
|---|---|---|
| 1 | The referrer opens Refer & Earn in the app | Your app deep-links into the Cheggout SDK, carrying the authenticated customer — see Entry points |
| 2 | The referral centre shows a code and a share link | Cheggout resolves the customer's code for your channel and programme |
| 3 | The referrer shares by WhatsApp, SMS or anything else | The share sheet is the customer's own device — nothing here is Cheggout-specific |
| 4 | The friend receives the link | The link carries referralCode as a query parameter into your apply flow |
| 5 | The friend applies for a product | Entirely your funnel. Persist the referral code against the application |
| 6 | The application is processed and activated | Your origination and KYC systems. Cheggout has no visibility here |
| 7 | Your backend calls the referral API | RegisterEvent with eventType: "Referral" — this is the conversion signal |
| 8 | Cheggout assigns rewards to both sides | Attribution, eligibility and payout run against your campaign configuration |
| 9 | Both customers see their reward | The referral centre, on either the SDK or the microsite surface |
The one step that is yours to build and easy to get wrong is 7. If activation happens and
RegisterEvent never fires, the referral silently never converts — no error surfaces to either
customer. See Event integration for the retry and idempotency guidance.
Next
- Entry points — how a customer gets to step 1
- Event integration — how you deliver step 7