Wallet passes vs consumer punch-card apps: count the taps

The step you can't watch

A shared punch-card app asks your customer to install software and then find your shop inside it. A wallet pass asks them to scan a code and tap Add. Same stamps, same free tenth coffee, but one path has an app-store detour in the middle and the other doesn't. That detour is where most of your enrollments die.

The reason isn't that people dislike loyalty cards. It's that the install happens on your floor, on your wifi, with a queue behind them. Your cashier can talk a stranger through a two-field form in about ten seconds. Your cashier cannot talk a stranger through a 90 MB download, a store password prompt, and an SMS verification code.

Wallet passes skip the install because Apple Wallet and Google Wallet are already on the phone. Nothing gets downloaded from a store, no account is created, and no password exists to forget. On any device that has neither wallet, Waya falls back to a web card that opens in the browser.

Count the taps: eleven steps versus four

Here is the shared consumer app, step by step, as a customer actually experiences it. One: the cashier explains what the app is. Two: the customer opens the App Store or Play Store. Three: they type the app name, and hope the first result is the right one. Four: the download runs on shop wifi. Five: Face ID or a password confirms the install.

Six: the app opens and asks them to accept terms. Seven: they create an account with an email or a mobile number. Eight: they leave the app to read a verification code, then come back. Nine: iOS asks whether to allow notifications. Ten: they search the app's directory for your shop. Eleven: they pick the right branch, and finally get the first stamp.

Now the wallet pass. One: scan the QR on the table tent with the camera that's already on the lock screen. Two: type a first name and a mobile number on one screen. Three: tap Add to Apple Wallet or Save to Google Wallet. Four: confirm on the wallet screen that appears. That's it — no account, no password, no directory search, and no chance of landing on the wrong shop, because the QR only points at yours.

Eleven steps versus four is not a design opinion. It's the count. Every step is a place where a phone rings, a friend says "let's go", or the wifi drops.

The funnel math, with the assumptions written down

Take 100 customers who get asked at the register on a normal week. Give each step a survival rate. I'm inventing these percentages as a model, not measuring your shop, and you should argue with every one of them — the point is the shape, not the digits.

Consumer app path: 70 of 100 agree to try at all, because roughly a third stop listening at the word "download". Of those 70, about 80% actually open the store, which leaves 56. About 85% finish the download on shop wifi: 48. About 80% get through account creation and the verification code: 38. About 90% find the right shop in the directory: 34 cards.

Wallet pass path: 85 of 100 agree, because there's nothing to install. About 92% finish a two-field form: 78. About 90% complete the Add to Wallet tap: 70 cards.

34 versus 70. Roughly double, from removing steps rather than persuading harder. Notice which rows disappear entirely on the wallet side: the store search, the download, the account, the verification code, the directory lookup. You can only optimize a step you own, and the app-store detour is the one step nobody in your shop controls.

What the shared-app model genuinely does better

A shared consumer app gives a customer one home for many cards. Someone collecting stamps at 12 shops sees all 12 in one list, and the app can point them at nearby shops they've never visited. That's real discovery, and a wallet pass does not do it. If you value being listed where other shops' customers already browse, that is a legitimate reason to choose one.

A real app can also do things a pass structurally cannot. It can take orders, hold a stored balance for payment, show a full menu, run a referral screen, and change its whole interface next week. A wallet pass is a card: logo, colors, a few fields, and text on the back. Apple and Google decide the layout, not you.

So the honest split is by size and by ambition. If you're a chain of 40 branches with delivery, an app makes sense and loyalty becomes one tab inside it. If you're one barber, one laundry, or a two-branch café, you're asking a stranger to install software for one shop's stamps, and the reward on offer is a free tenth cup.

Where wallet passes lose, and what Waya does not do

A pass can't run a UI. There's no ordering, no in-card game, no custom screen. If a customer deletes the pass, updates stop: you still have their first name and mobile number in the dashboard, but the lock-screen channel is gone until they add a card again. Waya doesn't send SMS, so there's no fallback message channel by design — no phone number of yours is handed to a third-party messaging app either.

Waya has no POS integration and no hardware. Staff add stamps, points, or redemptions by scanning the customer's card on an ordinary phone, either in the web dashboard or the Waya merchant app on iOS. If you want the till to add a stamp automatically when the payment goes through, Waya won't do that today. It sits beside your till, not inside it.

The free plan is 0 SAR forever with no credit card, and it stops at hard lines: up to 100 customers, 100 wallet messages a month, 1 stamp card, 1 branch, with the full dashboard and your own card design. When you hit 100 customers, enrollment of new customers stops — everyone already enrolled keeps their card and keeps collecting. Growth is 85 SAR a month (867 SAR a year) for unlimited customers, 10 cards, 3 branches, and 5,000 messages a month. Premium is 149 SAR a month (1,520 SAR a year). Annual billing is 15% off.

How this maps to the Saudi shortlist, as of 18 August 2026

If you're shopping in Saudi Arabia, you'll probably see four names. Niqati is the best-known and the leader by search share, with quote-based subscription pricing. Btaqa publishes tiers at 108, 250, and 380 SAR a month. OneCup is around 150 SAR a month. Watily is 149 SAR a month, with loyalty bundled into a wider plan. Vendor pricing moves, so check each site yourself before you decide.

Do not shortlist on wallet support. Most of these products ship Apple Wallet and Google Wallet passes, and they're competent at it. The friction this article is about belongs to the generic international "punch card app" model, where the customer downloads a shared consumer app and searches for you inside it — not to every paid vendor in the market.

The one structural difference worth deciding on is where the price starts. Every option above begins with a paid subscription. Waya begins at 0 SAR and stays there up to 100 customers, with no credit card, which means you can test the tap math on your own customers before you spend anything.

Run the test yourself in one shift

Pick one Tuesday, 4 pm to 9 pm. Put a notepad by the register and have your cashier make one tick for every customer they ask, whatever the answer. At close, compare the number of ticks to the new customers the dashboard logged that day. That ratio is your real enrollment rate, and no vendor's marketing page can tell it to you.

Then time the path with a phone that has never seen your card. Hand it to a friend, point at the QR, and count out loud until the pass is in their wallet. Do the same with any app-based option you're considering, from the store search onward. Whichever number is smaller wins on the only metric that compounds, because a card that never got saved is worth exactly nothing.

For context on the base we're measuring against: the numbers published on our Arabic homepage are 100+ shops across Saudi Arabia, 5,000+ customer cards living in wallets, and 4.9 out of 5 rated by 90 merchants. Waya is also backed by the AWS Startups program. Run your own shift test anyway — one afternoon of ticks on a notepad beats anyone's homepage.