A practical guide for businesses
How to launch a loyalty program without an app: a guide to digital loyalty cards
An app-less loyalty program lets customers join without installing a separate app. Their branded card goes into Apple Wallet or Google Wallet, or opens in a browser. At checkout they show a QR code; a connected POS or booking system can process points automatically. Setup and availability depend on the business’s rules, devices and integration scope.
This guide covers the available formats, what drives cost, how to connect your POS, and how to launch in five steps.
What an app-less loyalty program is and how it works
An app-less program keeps the card where the customer already has one: Apple Wallet, Google Wallet or the browser. The business does not build its own app, and the customer installs nothing.
There are three formats:
- Wallet card. The customer scans a QR code or taps a link, and the card is added to Apple Wallet or Google Wallet. When points or tier change, the card updates on the phone by itself; the business can send notifications to the card.
- Web card. A personal page in the browser, accessed with a phone number. It serves as the fallback for devices without Wallet and shows balance and transaction history.
- Phone-number lookup. The cashier enters the number without a card. Combine this with a Wallet or web card so customers can check their balance.
The mechanics are the same in every format: the customer registers once (phone number + SMS verification), the QR code is scanned at the till or front desk, the connected system sends the transaction, the loyalty rule calculates points or rewards, and the card updates. From the customer’s side there is one step: show the phone. The QR code on the card is the customer’s persistent personal identifier — in effect a wallet number: it stays the same from visit to visit, contains no personal data or balance, and has no value on its own; earning and redemption happen only on the business side.
Why businesses are dropping their own app
A custom loyalty app adds installation, usage and maintenance decisions.
- The install barrier. A Wallet card avoids a separate app-store download. Test whether that makes your own customers more likely to complete registration.
- The usage barrier. An installed app still needs a reason to be opened. Wallet cards sit alongside other passes; lock-screen presentation depends on device features and configuration.
- The maintenance burden. An app requires iOS and Android support, store reviews and OS updates. Compare that budget with a hosted card service.
- Notifications. Wallet cards can support notifications, but capabilities differ by platform. They do not replace every function of a custom app.
An app can still make sense when ordering, payment and delivery belong together. For loyalty alone, compare simpler options first.
Comparison: custom app, Wallet card, plastic card
A Wallet card combines a familiar card format with digital communication. Actual costs and capabilities depend on the provider and setup.
| Criterion | Custom mobile app | Wallet / web card | Plastic or paper card |
|---|---|---|---|
| What the customer must do | Install + register | Tap a link + verify phone | Carry the card |
| Drop-off at sign-up | High | Low | None, but cards get lost |
| Time to launch | Months | Days | Print lead time |
| Upfront cost | High (development) | Low (subscription) | Low (printing) |
| Ongoing cost | Development and store maintenance | Monthly subscription | Reprinting |
| Customer sees balance | Yes | Yes | No |
| Notifications | Yes | Yes (Wallet) | No |
| Customer data and analytics | Yes | Yes | None or manual |
| POS integration | Yes | Yes | No |
| Fraud risk | Low | Low (personal QR with no personal data or balance) | High (stamps, copies) |
Launching in five steps
The order is always the same: rule first, then card, then integration, launch last. Designing the card before the rule is the most common mistake.
- Set the goal and the rule. Choose visit frequency, average ticket or the return of lapsed customers. Make the reward clear and cost it for the business — for example, 5 points per 100 units spent, 200 points for a dessert.
- Set up the card and the sign-up flow. Logo, colors, fields on the card (points, tier, name). One QR code and one link for sign-up: on the table, at the till, on the receipt, in the Instagram bio. Ask only for phone number and name; every extra field costs enrollments.
- Connect the POS or booking system. The system recording the sale or visit should send the transaction automatically: restaurant POS, salon booking software or gym membership system. Until integration is live, an audited cashier panel can bridge the gap.
- Train the team and test. Cashiers need to know three things: how to scan the QR, how to redeem a reward, and what to do when a customer says “my points didn’t register.” Run the program on your own staff for a week before the public launch.
- Launch and run the first campaign. Track sign-ups for the first two weeks. If enrollment is low, check whether cashiers offer the card and where customers stop registering. Keep the first campaign simple: welcome points for signing up.
Choosing the mechanic
The mechanic follows the business’s visit rhythm; the program that fits wins, not the one with the most features.
| Mechanic | How it works | Best for | Watch out for |
|---|---|---|---|
| Spend-based points | Points per amount spent, redeemed for rewards | Restaurants, retail; variable ticket size | Point value must be obvious (100 points = what?) |
| Visit counter | Reward on the Nth visit (“5 coffees, 6th free”) | Coffee shops, fast casual; frequent small purchases | Ignores ticket size |
| Tiers | Silver/Gold/VIP by spend or visits, perks grow | Restaurants, beauty; status matters to the customer | Top-tier perks must be tangible |
| Membership / check-in | Attendance, renewals and referrals rewarded | Gyms, courses | Reward should drive renewal |
| Rebooking | Points for booking again within a set interval | Hair, skincare, dental | Interval must match the service’s natural cycle |
Start with one mechanic; add tiers and campaigns once there is data.
Connecting to POS and other systems
A loyalty program is only as reliable as the data that drives point calculation. There are three routes:
- Direct POS or booking integration. When a sale or appointment closes, the system sends the transaction via API and points are processed automatically. The most accurate route; the cashier does nothing. Common restaurant POS systems such as iiko expose loyalty APIs for this purpose.
- Cashier panel. The cashier scans the customer’s QR, enters the amount, and points are applied. A bridge until integration is live; the owner must be able to review every transaction.
- Hybrid. Point earning comes automatically from the POS, redemption is confirmed by the cashier. This is the balance most venues settle on.
Before integration, check POS version and license access, refunds and voids. Designate one authoritative point balance; independent balances can drift apart. Plan reversal handling before launch.
Regional considerations
The mechanics travel; the details around them don’t. The following areas change from country to country and need checking before launch.
- Language. Use the languages customers read: Russian and Kazakh in Kazakhstan; consider English and Russian alongside Turkish in tourist destinations.
- SMS verification. Phone-based registration needs reliable OTP delivery. Check local provider and sender-name requirements before launch; approval times vary.
- Currency and inflation. Rules are defined in local currency — tenge, lira, euro. In high-inflation markets a fixed “100 points = 100 units” rule loses value quickly; defining rewards as products or percentages (one coffee, 10% off) protects point value.
- Data protection and marketing consent. Phone number and name are personal data everywhere. The sign-up screen needs a consent notice and a privacy policy link, and marketing messages usually require separate opt-in — Turkey’s İYS registry is a strict example. Wallet card notifications are typically a separate channel from SMS and email marketing, which is one reason the format is attractive. Confirm the specifics with your legal adviser.
General information, not legal advice.
- Device mix. Test the devices your customers use in Turkey, Kazakhstan or another market. Plan a web-card fallback where Wallet is unavailable.
- POS landscape. Check the venue’s system and API access before promising integration. For iiko, confirm the version, license and connection scope.
Common mistakes
Review design and operations as well as technology.
- The reward is too far away. Set an achievable first reward and check that its cost is sustainable.
- Too many sign-up questions. Birthday, email, address — every field lowers enrollment. Phone number and name are enough; collect the rest later.
- Cashiers don’t offer it. Give staff a short invitation script and check whether it helps customers understand the offer.
- Points are entered by hand. A source of errors and abuse. The permanent fix is POS integration.
- Data is collected but never used. The program’s value is in campaigns: an offer to whoever hasn’t visited in 30 days, birthday points, a VIP-only event. A program that only hands out points is a cost line.
- Rules keep changing. Set sustainable rules from the start; explain changes clearly.
Frequently asked questions
Do customers need to download an app?
No. The card is added to Apple Wallet or Google Wallet, or opened in the browser as a web card.
Does it work on Android?
Yes. On devices with Google Wallet the card is added to the wallet; on others the web card is used.
What if the customer forgot their phone?
The cashier can look the customer up by phone number and apply the points. The card and balance are tied to the number, not the device.
Does it connect to our POS system?
It can connect to POS and booking systems with an open API; in restaurants iiko is a common example. The scope depends on the system’s version and license and is confirmed before setup.
How long does setup take?
The card and rules are ready in a few days; with POS integration, plan a few weeks including testing.
We have several locations — is it one program?
Yes. One program applies across all locations, with reports broken down per location.
Do points expire?
The business decides: never, or after 3, 6, 12 or 24 months. Expiring points are a reminder tool that brings customers back.
What about data protection?
The sign-up screen needs a consent notice and a privacy policy link; marketing messages usually need separate opt-in. This is general information, not legal advice — check the rules for your country.
How do we move from plastic cards?
Existing customers are migrated by phone number, and old card balances become starting points. Both cards are accepted during a transition period, then plastic is retired after a few months.
