Lifestyle Marketplace
A complete commerce and offers experience that lives inside your app. The customer taps "Shop" and arrives in a marketplace — already signed in, themed to feel like part of your product.
Available Android · Available iOS · Available Hosted
The problem it solves
Publishers want an offers destination, but building one means sourcing merchants, negotiating commercials, running a catalogue, handling vouchers and settling with brands. That is a business, not a feature.
This module is the whole destination, delivered as a component you launch.
What's inside
From Cheggout's platform capabilities:
| Area | What the customer gets |
|---|---|
| Popular store icons | Quick access to top brands and retailers |
| Personalised offer banners | Tailored promotions alongside your own branded banners |
| Discounted e-vouchers | Redeem vouchers bought at exclusive discounts |
| Local and hyperlocal deals | Offers personalised to the customer's location |
| Dining discounts | Savings at partner restaurants |
| One-Rupee Store | Selected products for ₹1 |
| Travel bookings | Flights and hotels with discounts |
| Gift cards | Brand gift cards, with additional discounts on selected brands |
| Post-transaction scratch cards | Surprise rewards after a transaction |
Deals span 600 or more online and offline retailers.
How it fits into your app
Both routes use the same single sign-on: your backend mints a session, you pass it at launch, and the customer never sees a Cheggout login.
SDK or hosted?
| Native SDK | Hosted microsite | |
|---|---|---|
| Feel | Native screens inside your app | Web experience |
| Effort | Roughly 2–3 weeks | Roughly 1 week |
| Ships with | An app release | Server-side, no app release |
| Offline | Partial | No |
| Best for | Banks and wallets making this a core surface | Fastest path to launch, or a web-first publisher |
The effort figures are estimates from comparable integrations, not commitments.
You can start hosted and move to the SDK later — the session contract is the same, so the integration work carries over.
What you build
Less than you might expect:
- A launch point — a "Shop" icon, an offers tile, a menu item.
- A session mint on your backend, after your own authentication.
- The launch call, passing
virtualIdandsessionId. - The return handling — what happens when the customer comes back.
Everything the customer sees inside the marketplace is Cheggout's.
Optional additions
| Feature | What it adds |
|---|---|
| Cashback badge | The customer's points balance on your own screens |
| Deep payment | Payments executed by your app rather than by Cheggout |
| Banners and stores | Marketplace content rendered natively on your home screen |
| Scratch cards | Rewards that land in the same marketplace |
Theming
The experience is configured per publisher, so it carries your brand rather than Cheggout's.
TBD Publisher-configurable theming is not self-service. Branding, imagery and which modules appear are configured by Cheggout for your channel during onboarding. There is no published theming API or design-token contract. Agree your requirements early.
Before you start
- Signed-envelope authentication implemented
- A
virtualIdscheme decided and stable - A Virtual ID generation service available to Cheggout and your app vendor
- SDK artifacts received, if you are going native
- Hosted launch URLs provisioned, if you are going hosted
- Branding requirements agreed with Cheggout
- A decision on session-close behaviour — see Return handshake
Next
- Session & SSO — the authentication flow, end to end.
- Deep payment
- Cashback badge
- Android · iOS · Hosted