RewardLoop
A Flutter Loyalty Wallet, Merchant App and Web Admin on One Backend
A concept study: we worked up this product, its architecture and its screens as an example of how we would approach it. The screens use fictional demo data and are design concepts, not screenshots of a live product, and this is not a client project.

About the Project
RewardLoop is a design concept for a loyalty system for multi-outlet local brands, such as a cafe chain, a salon group or a bakery. It is three connected products on one backend: a Flutter wallet app where customers collect stamps, points and offers, a Flutter merchant app where counter staff scan and redeem them, and a web admin where owners design the programme and read the results.
Every earn and redeem is a line in an append-only ledger, and balances are worked out from it. A stamp earned at the till can therefore appear in the customer's wallet within seconds, and any balance can be explained line by line when a customer disputes it. Customer codes rotate every minute, so a screenshot cannot be reused, and each scan carries a unique key so a double tap or a network retry never redeems twice.
The merchant app is built for a queue. It has big buttons, checks the signed code on the phone, and keeps working through a short network drop by queueing scans and syncing them later. Store credit in rupees is kept apart from stamps and points behind a switch, because whether a credit scheme counts as a prepaid payment instrument is a question for a qualified adviser.
Why This Matters Now
Market, rule and technology context for this kind of product, checked on 16 November 2026. Each item names its source.
- The Flutter documentation lists Flutter 3.50 as released on 11 Nov 2026, with the bundled Material and Cupertino libraries formally deprecated in favour of standalone packages, and readiness updates for iOS 27 and Xcode 27.Flutter documentation, 11 Nov 2026
- PassKit, a wallet pass vendor, reported that Apple's WWDC 2026 added a Poster Generic pass style and Featured Actions on all pass types, with new barcode formats and a Pass Designer tool. This is a vendor summary, not Apple documentation.PassKit (vendor blog), 15 Jun 2026
- Law firm AZB & Partners reported that the RBI's April 2026 draft on prepaid payment instruments keeps closed-system instruments outside RBI regulation, except marketplace-issued ones, and is still a draft.AZB & Partners (law firm), 1 Jun 2026
- The Flutter team's release post for Flutter 3.44 lists Swift Package Manager replacing CocoaPods as the default on iOS and macOS, plus agentic hot reload for coding tools.Flutter blog, 20 May 2026
Requirements & Objectives
- Let a customer join a brand's programme by scanning a poster code, and hold several brands' stamp and points cards in one wallet.
- Support stamp programmes (buy 9, get the 10th free) and points programmes with tiers, set per brand.
- Show a customer code that changes every minute and cannot be reused from a screenshot.
- Give counter staff a scan screen that shows the balance and eligible offers and redeems in two taps, with a clear message for every failure.
- Keep the merchant app working through a network drop by queueing redemptions, with a visible pending count and a rule for anything the server rejects.
- Record every earn, redeem, expiry and reversal in an append-only ledger with a unique key per scan, so a repeat returns the first result.
- Offer a web admin where owners build offers with days, outlets, minimum spend, a limit per customer and dates, then preview them as members see them.
- Save a card as an Apple Wallet or Google Wallet pass that updates after each visit, and keep each brand's data separate from the others.
The Engineered Solution
1One ledger behind every balance
Stamps, points and store credit are entries in one append-only table. Balances are computed from it, so the app, the wallet pass and the admin report all read the same numbers and a dispute can be settled line by line.
2A counter-first merchant app
A cashier scans, sees the balance and the offers that apply, and taps Redeem. The signed code is checked on the phone, and queued redemptions sync in order when the signal returns.
3Codes that cannot be copied
The customer's code is a short-lived signed token that rotates every minute. Each redeem call also carries a unique key, so a double tap, a second cashier or a retry cannot redeem the same reward twice.
4Offers designed once, seen everywhere
An owner sets the rules in the web admin and previews the wallet card. After scheduling, the offer appears in the app and the pass update goes out from a job queue with retries.
Design Concept Screens
Design concepts with fictional demo data. They show how the product could look and work, not a live release.
01 / 05 Customer wallet - see every card and offer in one place and add a card to the phone wallet
Engineering Process
- Map one real counter visit with a cafe or salon team, from the customer's arrival to the cashier's next customer, and note where it slows down.
- Design the ledger and the offer rules first, then write one OpenAPI file that both apps and the web admin will use.
- Prototype the wallet, the code screen and the scan screen, and test the scan flow with cashiers on a busy counter.
- Build the core loop in Flutter with shared packages: sign-in, join by poster code, rotating code, scan and redeem, and the offline queue.
- Add Apple Wallet and Google Wallet passes with updates from a job queue, and build the offer builder and outlet reports in the web admin.
- Test double redemption, offline sync, pass updates and consent and deletion flows, then run a load test for a busy sale day.
- Prepare store listings and issuer accounts, release to one pilot outlet first, and widen to the other outlets after a trial period.
Production Tech Stack
| Layer / Component | Production Technologies |
|---|---|
| Mobile apps | Flutter 3.50 with DartRiverpodgo_routerDrift (SQLite) for the offline queuemobile_scannershared packages managed with Melos |
| Web admin | Next.jsTypeScriptTailwind CSSshadcn/uiTanStack Table and Apache ECharts |
| Backend | NestJS (Node.jsTypeScript) REST API with OpenAPIBullMQ jobs on Redis |
| Database | PostgreSQL with an append-only ledger table and row-level security per brand |
| Wallet and messaging | Apple Wallet (PassKit)Google Wallet APIFirebase Cloud MessagingAPNsan SMS provider for one-time passwords |
| Cloud and delivery | Containers on AWS (ECS Fargate) in the Mumbai regionTerraformGitHub Actions with FastlaneSentry |
What the design aims for
RewardLoop aims to tie every stamp, point and redemption to one explainable ledger that the wallet, the counter and the owner all read.







