How to Build a Loyalty App: Points, Tiers, Digital Cards and Wallet Passes

We are Talha Aslan and team, and we built this guide around the questions we hear most often in real projects. In short, a good loyalty app is more than a "collect points" screen. The five seconds at the register, the timing of each notification, and your fraud rules decide whether it works. Here is the roadmap:

1. Write your goal in one sentence: more frequent visits, a bigger basket, or trial of new products.
2. Choose a reward model: points, a stamp card, tiers, or a mix.
3. Check your point economics on paper with an example calculation.
4. Pick a checkout method: QR code, barcode, or phone number.
5. Decide whether you want Apple Wallet and Google Wallet passes.
6. Plan notifications, permissions, and personal data around store rules.
7. Prepare fraud rules and a measurement dashboard before launch.

Does your business really need a loyalty app?

Not every business needs its own app. For example, if a customer visits once a month, asking them to download an app just to see points is a hard sell. On the other hand, a coffee shop, bakery, hair salon, or car wash with weekly regulars can offer real convenience through an app.

Ask three questions before you decide. First, how often does a typical customer visit? Second, will the app do anything beyond points, such as ordering, booking, menus, or personal offers? Third, can your checkout recognize the customer quickly?

If the answers are weak, a lighter option makes sense. A wallet pass alone or a web-based solution may be enough; we compared these paths in our guide on choosing between a mobile app and a PWA. If the answers are strong, a loyalty app that combines points with ordering and offers becomes your direct line to customers. In projects like this, we build your app and take it through store review. Still, we recommend settling these questions together first.

Which reward model fits you: points, stamps, or tiers?

Your reward model is your answer to "why should I come back?" Therefore, choose it based on your product and visit frequency. The table below compares the four models we see most often.

In short, a stamp card is usually enough for a single coffee shop. A retail chain, however, benefits from a hybrid model that leaves room for personal offers. Once you pick a model, you need to know what each point really costs.

How do you calculate point economics?

Point economics shows how much of your margin each reward consumes. If you launch campaigns without this math, the gift you give loyal customers can quietly turn into a loss.

The example below only shows the method. The numbers do not describe your business.

• Example scenario: A coffee shop gives 5 points for every 10 dollars spent and turns 100 points into a 5 dollar item.
• The customer needs to spend 200 dollars to reach 100 points.
• Since the reward sells for 5 dollars, the share returned to the customer is 2.5 percent.
• Your real cost is lower than the menu price, so calculate the burden with product cost.

Also, some customers never spend their points. However, do not build your budget on that unused balance. Otherwise, a successful campaign can raise your cost without warning. Decide on point expiry from day one as well. If points expire, state it on the sign-up screen and in campaign copy. That way customers are not surprised, and complaints drop.

How should you design a tier system?

A tier system motivates customers with the goal of reaching the next level. For example, three levels such as Bronze, Silver, and Gold are enough for most businesses. More levels rarely stick in anyone's mind.

When you design tiers, we suggest these rules:

• Describe each tier's benefit in one sentence.
• Show the distance to the next tier on the home screen.
• Calculate tiers over a defined period and state that period clearly.
• Send a reminder before any downgrade.
• Offer more than discounts at the top tier, such as early access or exclusive items.

On the other hand, a downgrade feels like a loss. So we recommend dropping one level at a time, never two. In addition, keep the first tier easy to reach. A customer who earns an early reward keeps using the app instead of deleting it. We covered those first days in more depth in our article on why users uninstall apps in the first 7 days.

How do you scan a digital card or QR code at checkout?

The moment at the register is the most critical part of any loyalty app. If the cashier and customer wait too long during a rush, staff and customers will soon stop using it.

The three most common methods are:

1. Customer QR code: The app shows a personal QR code, and the cashier scans it with a barcode reader or tablet.
2. Register QR code: A transaction QR appears on the receipt or screen, and the customer scans it with the app.
3. Phone number: The cashier types the number. It is fast, but points can land on the wrong account.

In most projects we recommend the customer code, because the cashier stays in control. Also, if the code refreshes on every open and expires quickly, screenshots become far less useful for fraud. We collected scanning problems such as screen brightness, cracked screens, and tiny codes in our guide to QR codes that will not scan. To create test codes for your counter or tables, try our free QR code generator.

What do Apple Wallet and Google Wallet passes do?

A wallet pass lets customers show their loyalty card from the phone's wallet without opening your app. On its Apple Wallet developer page, Apple describes store cards for loyalty cards, discount cards, points cards, and gift cards. It also notes that a store card with a balance can update to show the current balance.

On the Google side, the Google Wallet loyalty cards documentation explains that a pass combines a class and an object. The class holds the shared brand design, while the object holds one customer's card. You can issue these passes from an Android app or anywhere links work, such as a website, email, or SMS.

So why add a pass if you already have an app? Because customers can pull it up quickly at checkout. As a result, scanning gets faster. Moreover, Apple notes that passes can surface based on location. A customer walking past your store gets a gentle reminder.

Is a wallet pass enough, or do you need a full loyalty app?

This depends on budget and goals. A wallet pass alone is a light start for customers who want points without installing anything. However, if you want ordering, personal offers, booking, or purchase history, you need an app.

Our practical advice is to think about both. In other words, let the app be the main channel and let the pass keep the door open for customers who never install it. That way, nobody gets turned away at the register.

How should checkout and POS integration work?

Accurate points depend on the register. That is why we plan the integration before the app screens. If your POS (point of sale) software can share data, the system posts points from the receipt total automatically. If it cannot, the cashier enters the amount on a separate screen.

Automatic integration cuts errors and abuse. On the other hand, manual entry is cheaper at first but open to wrong amounts. Therefore, if you choose manual entry, cap the points a single transaction can earn.

Google offers one more option. According to the Google Wallet Smart Tap documentation, customers can redeem a pass by holding the phone to an NFC point of sale terminal. However, your terminals must support Smart Tap. The same page asks you to update the pass after redemption, so the customer sees the new points balance. In short, if your terminals are not compatible, starting with QR and moving to NFC later is the realistic path.

How should you send campaign notifications?

Campaign notifications are how a loyalty app brings customers back. However, Apple sets a clear rule here. Under guideline 4.5.4 of the App Store Review Guidelines, push notifications for promotions or direct marketing require explicit opt-in through consent language in your app. You also need to offer an in-app way to opt out.

In practice, this means two separate permissions: the system permission for notifications and your own marketing consent. We explained the timing of that request in our post on when to ask for push notification permission. Here, we focus only on the loyalty side.

• Tie messages to point events. "One more coffee and your reward is ready" beats a generic discount.
• Limit frequency. A few meaningful messages per week beat a daily blast.
• Keep reminders about expiry or tier changes separate from promotions.
• Let users switch notification topics on and off individually.

How do notifications work on wallet passes?

Wallet passes can notify customers too, but with tighter limits than an app. Google's push notification documentation for loyalty cards describes two routes. One fires when the pass updates, for example when the points balance changes. The other fires when you add a message to the pass.

There are two important limits. First, Google caps how many of these notifications you can send in a 24 hour window. Check the current value on the official page. Second, customers must have notifications enabled for their passes. Consequently, treat wallet notifications as a channel for balances and key reminders, not as your main campaign channel.

On the Apple side, updated pass details also appear in the customer's wallet. So decide carefully what goes on the front of the card. For most businesses, the points balance, current tier, and distance to the next reward are enough. Keep campaign text short, and leave longer explanations to the app.

Can you reward customers for turning on notifications?

No, Apple explicitly forbids it. Guideline 5.1.2(i) says an app may not require users to enable system features such as push notifications, location services, or tracking. That covers access to functionality, content, or any compensation, including gift cards and codes.

We see this mistake often. For example, a "Turn on notifications and earn 50 points" screen looks like a harmless promotion at first glance. In reality, it is exactly what the guideline prohibits, and it can trigger a rejection during review.

So what can you do instead? Explain why you are asking. A benefit line like "We will let you know when your reward is ready" is more honest than a bribe. Then tie points to real actions, such as a first purchase, a completed profile, or a friend's first order. As a result, you follow the rules and every point maps to a real sale. The same logic applies to location. A customer who declines location access should still be able to join.

Which store rules apply to a loyalty app?

When we publish a loyalty app, the rules we meet most often cover payments, accounts, and minimum functionality. The points below come from the App Store Review Guidelines and Google Play policy. Rules change, so check the current text before launch.

• Physical goods and services: Apple guideline 3.1.3(e) asks you to use payment methods other than in-app purchase for physical goods and services consumed outside the app. Google Play's payments policy also says not to use Play billing for physical goods and services.
• Digital vouchers: Under guideline 3.1.1, digital gift cards, vouchers, and coupons redeemable for digital goods or services can only be sold in the app through in-app purchase.
• Account deletion: Guideline 5.1.1(v) requires apps that support account creation to offer account deletion in the app.
• Minimum functionality: Guideline 4.2 expects an app to go beyond a repackaged website.

We cover the deletion rule in more detail in our post on Apple's mandatory account deletion rule.

What does Apple require for wallet passes?

Apple also ties wallet passes to its guidelines. According to guideline 3.2.1(iv), passes can make or receive payments, transmit offers, or offer identification. The examples include movie tickets, coupons, and VIP credentials. The guideline warns that other uses may lead to app rejection and the loss of Wallet credentials.

In addition, guideline 1.5 asks that passes include valid contact information from the issuer. Passes must also carry a signature from a dedicated certificate assigned to the brand or trademark owner. In other words, issue the pass under your own brand, not under another company's certificate.

In practice, these two rules mean a loyalty pass is on solid ground as long as it carries offers and a membership identity. Add your business address, phone number, and support link to the back of the pass. Also, decide early who owns the certificate and who renews it. If it expires, issuing new passes can stall.

How do you prevent fraud and fake points?

Points behave like money, so you need to protect them. The abuse we see most often includes cashiers adding points to their own accounts, one person opening several accounts, and receipt QR codes shared online.

Here are the safeguards we recommend:

1. Make every receipt QR code single-use and expire it after a short time.
2. Generate short-lived customer QR codes, so screenshots stop working.
3. Cap the points a single transaction and a single day can earn.
4. Give each cashier a personal login and link every point entry to that login.
5. Verify phone numbers to block a second account on the same number.
6. Flag unusual activity, such as heavy point gains at midnight or repeat entries from one cashier to one account.

Also, state in your terms that you may cancel points in cases of abuse. Before using that right, though, contact the customer. A false alarm can cost you a loyal regular.

What should you know about personal data and privacy?

A loyalty app collects personal data by nature: name, phone number, purchase history, and sometimes location. So write down why you collect each item, and do not ask for data you do not need. For example, if a birth date only serves a birthday reward, the day and month may be enough.

In addition, ask for separate consent for marketing messages. We explained notices, consent, and app permissions in our guide to mobile app privacy compliance, so we will not repeat it here.

Note: this section is not legal advice. We recommend working with a legal advisor on your privacy texts.

The stores also ask for data disclosures. In the App Store privacy labels and the Google Play Data safety form, you must accurately declare purchase history and contact details. If your disclosures and the app's real behavior differ, review can take longer or an update can face rejection.

How do you measure loyalty app success?

Measurement shows whether your loyalty app actually works. Download numbers alone mislead. The real question is whether app users visit more often.

These are the metrics we suggest tracking:

• Sign-up rate: How many downloaders create an account?
• First scan rate: How many new members earn points at checkout for the first time?
• Visit frequency: Do members come more often than non-members?
• Redemption rate: How much of the earned points do customers actually spend?
• Notification impact: Do visits rise in the days after a campaign message?
• Lapse rate: Is the share of inactive members changing?

To get there, define app events from the start: sign-up, card display, points earned, reward redeemed, and notification opened. We explained naming and planning events in our post on which events to track in a mobile app. If possible, also keep a small control group. That way you can see a campaign's real effect.

What should sign-up and the first launch look like?

Customers often download the app at the counter, standing in line. So sign-up should take less than a minute. A phone number and a verification code are a solid start for most businesses. Ask for the rest later, and explain the benefit instead of paying for it.

On first launch, show three things: where the card is, how far the first reward is, and how points are earned. However, long tutorial screens make people in line impatient. Instead, a single explainer screen followed by the card works better.

You might also add a small welcome reward at sign-up. Tie it to registration or a first purchase, never to the notification prompt. To decide which screens your first version truly needs, read our guide on what to include in a mobile app MVP. In short, the card, points, rewards, and profile screens are often enough for version one.

Why does staff training matter so much?

Even the best loyalty program sits idle if the cashier never asks, "Do you have our app?" That is why staff should be part of the project from day one.

We suggest short, hands-on training on these points:

• How to introduce the program to a customer in one sentence.
• What to do when a code will not scan, such as raising brightness or using the phone number fallback.
• Which steps to follow when a customer redeems a reward.
• Whom to contact when they suspect abuse.

Also, give cashiers a simple screen showing their own results, such as new members signed up. As a result, the program becomes a measurable goal for them too. That said, never turn the target into pressure. A cashier who pushes customers to register hurts the program. As an example scenario, a small team reward for the location with the most weekly sign-ups works better than individual pressure.

How do you move customers to the app at launch?

If you already run a paper stamp card or another system, you need to move customers over without losing anything. Otherwise, people who lose their stamps will turn away from the program.

1. Set a rule for transferring old stamps into the app, and teach it to cashiers.
2. Place QR codes that point to the app at the counter, on tables, and on receipts.
3. Plan a short launch week offer that rewards sign-up plus a first purchase.
4. Add download links to your website and social media profiles.
5. Share the wallet pass link by SMS or email for customers who skip the app.

For restaurants and cafes, we compared apps and QR menus in our post on whether a restaurant needs an app or a QR menu. After launch, watch the first two weeks closely. Sign-up and first scan rates give early signals about the program's health.

What are the most common loyalty app mistakes?

Most mistakes we see are design mistakes, not technical ones. The most common are:

• Hiding the point value, for example showing "1,250 points" without saying what that means.
• Placing the first reward too far away, so customers quit before reaching it.
• Rewarding the notification prompt, which breaks Apple's guidelines.
• Leaving the checkout scan slow, so the program fades in busy hours.
• Thinking about fraud only after launch.
• Launching without defined events, so you cannot prove impact later.

Moreover, sending the same campaign to everyone lowers results. For instance, a "we miss you" message makes sense for someone absent for three weeks. A daily regular, by contrast, is a better fit for a new product announcement. In other words, segmentation matters as much as the points themselves.

What do we handle in a loyalty app project?

As Talha Aslan and team, we run the whole loyalty app project, from the reward model to store release. We design the point economics with you, plan checkout and POS integration, and develop the iOS and Android apps. We also set up Apple Wallet and Google Wallet passes, the notification flow, and measurement events.

On the store side, we prepare review notes, privacy disclosures, and the account deletion flow before submission. This way we work to reduce rejection risk from the start. Still, the final review decision always belongs to the store.

If you are considering a loyalty app for your business, describe your needs and checkout setup and request a quote on our mobile app development page. Our proposal states which model we recommend, which integrations you need, and the timeline.

Pre-launch checklist

Finally, we suggest ticking off the list below before release:

1. Does the sign-up screen clearly explain the reward model and point value?
2. Did you check the point economics with an example calculation?
3. Does a checkout scan finish within a few seconds?
4. Are customer and receipt QR codes short-lived and single-use?
5. Is there separate marketing consent and an in-app opt-out?
6. Is every reward independent of notification or location permission?
7. Can users delete their account inside the app?
8. Do your privacy disclosures match what the app actually does?
9. Does the wallet pass include your business contact details?
10. Did you define and test your measurement events?

A program that passes this list meets fewer surprises in store review and at the register.