Introduction
Cheggout is a user engagement and commerce platform for publishers — banks, fintechs, wallets, e-commerce platforms, super apps, telecom apps, loyalty programmes and media properties.
You bring the audience and the moment. Cheggout brings the offer inventory, the reward decisioning and the merchant network — deals from 600+ online and offline retailers, gamified rewards, coupons, dining discounts and an e-voucher marketplace.
What you can build
The platform is modular. Very few publishers integrate everything; most start with one module that fits a moment they already own.
| Module | The moment it fills | Typical publisher |
|---|---|---|
| Scratch Cards & Rewards | Right after a payment, order or content milestone | Banks, UPI apps, news sites |
| Advertisement | Home screen, dashboard, article page | Any app with attention to monetise |
| Lifestyle Marketplace | A "Shop" or "Offers" tab inside your app | Banks and wallets |
| Coupons & Deals | A rewards store where users burn points or coins | Fintechs with a coin/points economy |
| Refer & Earn | Invite and referral loops | Growth-led apps |
How you integrate
Four integration surfaces, all backed by the same server-side decisioning:
Headless API
You build and control the entire experience and consume Cheggout APIs server-to-server. No Cheggout UI anywhere.
Ready-made UI components
Lightweight native components for publishers without the engineering or design bandwidth to build the experience themselves.
JavaScript / Web
A single browser script renders Cheggout-powered rewards on your website, connected to the same APIs.
Hosted experience
Authenticate your user, hand off to a Cheggout microsite, get them back. The fastest path to launch.
Architectural principles
These hold across every module and every surface. They explain why the APIs are shaped the way they are.
Cheggout's backend is the source of truth. Campaign targeting, eligibility, coupon issuance, inventory decisions, fraud controls, frequency caps and reporting are all decided server-side. A client never decides whether a user deserves a reward — it asks, and renders the answer.
You integrate placements, not campaigns. Your app declares where something can appear (a banner slot, a post-transaction moment) and what happened (a payment completed, an article was read). Cheggout decides what to put there. Campaigns can then be launched, retargeted and retired without you shipping an app update.
UI components stay lightweight. The ready-made components are rendering layers over the same APIs. They are not a second application inside your application, and they are designed to feel like part of your product rather than an embedded Cheggout experience.
API-first publishers need no Cheggout UI. Every reward and coupon that a Cheggout component can render is also available as JSON. If you want to draw your own scratch card, you can.
Experiences should open fast. Catalogue and inventory responses are explicitly cacheable, and tokens are long-lived enough to pre-fetch. See Environments for the caching guidance per endpoint.
About this documentation
Cheggout's published integration documents are the contractual source of truth. This hub reorganises them into a developer portal and, where the source documents were silent or inconsistent, marks the gap rather than guessing.
Every page uses these markers:
- Available — documented and confirmed.
- Beta — usable today, contract may still change.
- TBD — awaiting confirmation from Cheggout engineering. Do not build against a TBD without talking to us; it is listed on the Open Items page with an owner.
- Not available — appears in older documents but is not currently offered.
Where a behaviour was not documented, this hub says so instead of filling the gap. If you find a page that leaves you guessing, that is a documentation bug — please tell us via Support.
Next steps
- How Cheggout works — the platform in one diagram.
- Core concepts — identity, channels, placements, events.
- Integration models — pick the combination that fits you.
- Onboarding — what to exchange with Cheggout before you write code.