Foundations
Start here for a precise, shared definition. A mobile wallet app is easy to use and surprisingly deep underneath — part payment terminal, part credential vault, part marketing surface. This part defines the object, shows the technology that makes it work, and traces how it evolved from a plastic-card replacement into a channel businesses can reach directly.
What is a mobile wallet app?
A mobile wallet app is a smartphone application that stores your payment cards, passes, tickets, and identity credentials digitally, so you can pay, check in, and prove who you are from your phone. The dominant apps — Apple Wallet, Google Wallet, and Samsung Wallet — come pre-installed on the device. Beyond tap-to-pay, they hold business-issued wallet passes (loyalty cards, coupons, tickets, memberships) that update remotely and can send lock-screen notifications.
Mobile wallet app — a native smartphone app that securely stores and presents digital versions of physical wallet contents: payment cards (via tokenized tap-to-pay), plus wallet passes such as loyalty and membership cards, coupons, gift cards, event tickets, boarding passes, transit passes, store cards, and, increasingly, identity documents. It replaces both the physical wallet and the stack of single-purpose apps a person would otherwise install.
The simplest way to understand a mobile wallet is to picture the physical wallet it replaces. In a leather wallet you carry payment cards, a driver's license, a coffee-shop loyalty card, a gym membership, a movie ticket, an airline boarding pass, and a fistful of coupons. A mobile wallet app carries all of the same things — but each item is now live. A payment card pays by tapping the phone to a terminal. A boarding pass updates itself when your gate changes. A loyalty card adds a stamp the moment you buy a coffee. A coupon disappears when it expires. The physical wallet was a static container; the mobile wallet is a container whose contents can change, notify, and be scanned.
This is the crucial distinction that most definitions miss: a mobile wallet app does two jobs, not one. Its first job is payment — storing tokenized bank cards so the phone can tap to pay in a shop or check out online. This is the job people notice first and the one the marketing on TV emphasizes. Its second job is credentials and passes — holding everything that isn't a payment card but still belongs in a wallet. For most users, the second category quietly outnumbers the first: a typical wallet holds one or two payment cards but a dozen loyalty cards, tickets, and passes. And it is that second job that turns the mobile wallet from a personal convenience into a business channel.
A mobile wallet is also not the same as a full-blown app for each brand. You do not download the "Starbucks wallet" and the "Delta wallet" and the "gym wallet." You save each of their cards into the one wallet your phone already has. That single-container model — one pre-installed app holding many businesses' credentials — is what makes the mobile wallet uniquely frictionless, both for the person carrying it and for the business trying to reach them.
- A mobile wallet app digitizes the physical wallet: payment cards, passes, tickets, and IDs, all live rather than static.
- It does two jobs — payment (tap-to-pay) and credentials/passes — and the second is where marketing lives.
- It is one pre-installed container holding many businesses' cards, not a separate app per brand.
Figure 1 — Inside a mobile wallet app. Two layers: a payment layer (tokenized cards, tap-to-pay) and a credential-and-pass layer (loyalty, coupons, tickets, IDs). Businesses market through the second layer. (Original PushNotice diagram.)
How mobile wallet apps work
A mobile wallet works by storing digital credentials securely on the phone and presenting them through NFC (tap), QR codes and barcodes (scan), or in-app checkout. Payments use tokenization — the real card number is replaced by a device-specific token, so the merchant never sees your actual card. Passes are signed data packages that the issuing business can update over the air, which is what lets a loyalty balance change or a gate number refresh without the customer doing anything.
Under the surface, a mobile wallet blends three technologies: secure storage, a presentation method, and — for business passes — an update channel. Understanding each demystifies the whole system.
Secure storage. Sensitive data is held in a protected area of the phone. On payment, the wallet does not store your real card number at all; it stores a token — a stand-in number tied to that specific device. Modern phones keep this in a dedicated hardware chip (Apple's Secure Element, Android's equivalent) isolated from the rest of the operating system, and unlocking it requires the owner's face, fingerprint, or passcode.
Presentation. A wallet has to hand its credential to a terminal or a staff member. It does this three ways. NFC (near-field communication) is the "tap" — holding the phone to a contactless reader transmits the payment token or, increasingly, a pass, over a few centimeters. QR codes and barcodes are the "scan" — the pass displays a code that a scanner reads, which is how most loyalty cards, coupons, and tickets are redeemed. In-app / online checkout lets the wallet fill payment details into a website or app without typing a card number.
The update channel. This is the part that makes wallet marketing possible. A business pass is not a static image; it is a small signed file plus a link back to the issuer's system. When the business changes the underlying record — adds a loyalty stamp, changes a gate, marks a coupon used — it pushes the update and the wallet re-renders the pass on the customer's phone, optionally showing a lock-screen notification. On Apple this runs through the PassKit push-update mechanism; on Google through the Wallet API. A single change on the business's server can refresh thousands of saved passes at once.
Figure 2 — How a mobile wallet works. Secure storage, then presentation by tap or scan, then — for passes — an over-the-air update channel. (Original PushNotice diagram.)
When you add a card to a mobile wallet, the wallet requests a token from the card network. That token — a Device Account Number — is what's stored and what's transmitted at the terminal. Your real 16-digit number is never on the phone and never handed to the merchant, so a breach at the store cannot expose it. Each transaction also carries a one-time cryptogram, making a captured token useless to replay. This is why tap-to-pay is generally more secure than swiping or inserting a physical card.
- Wallets combine secure hardware storage, a presentation method (NFC tap or QR scan), and — for passes — an over-the-air update channel.
- Payments use tokenization: a device-specific token replaces your real card number, which the merchant never sees.
- The update channel is what makes wallet marketing possible — a server change refreshes every saved pass.
The evolution of mobile wallets
Mobile wallets evolved in four waves: early carrier and PayPal experiments, the NFC breakthrough with Google (2011) and Apple Pay (2014), the expansion from payments into passes and tickets, and today's move into identity and everyday credentials. Each wave solved the previous one's biggest limitation — first getting a card onto the phone, then making tap-to-pay reliable, then giving the wallet a reason to open every day.
The idea of paying by phone is older than the smartphone, but it took four distinct waves to reach the wallet people use now.
Wave 1 — Early experiments (2000s–2011). Carriers and startups tried SMS payments, carrier-billing, and clunky "mobile money" apps. PayPal digitized online payments. These proved demand but were fragmented, and none put a real card securely on the phone for in-store use.
Wave 2 — The NFC breakthrough (2011–2014). Google Wallet launched in 2011 with tap-to-pay over NFC; Apple Pay followed in 2014 and, crucially, paired NFC with tokenization and fingerprint authentication, solving the security and trust problem that had held tap-to-pay back. Samsung Pay arrived in 2015 with the added trick of MST, letting it work on older magnetic-stripe terminals. Tap-to-pay finally worked and felt safe.
Wave 3 — From payments to passes (2012 onward). Apple's Passbook (2012, later renamed Wallet) introduced passes — boarding passes, tickets, loyalty and store cards — giving the wallet a reason to open on days you weren't paying for anything. This is the wave that created wallet marketing: for the first time a business could put a self-updating, notification-capable card on a customer's phone without building an app.
Wave 4 — The credential wallet (2020s). The newest wave adds identity: state IDs and driver's licenses in Apple and Google Wallet, digital car and home keys, corporate badges, health and vaccination records, and transit that just works by tapping the same phone. The wallet is becoming the place you keep everything you'd otherwise carry — which raises its value as a channel and its stakes for privacy.
Figure 3 — Four waves of mobile wallet evolution. Experiments, then the NFC-plus-tokenization breakthrough, then passes and tickets, then identity credentials. Wave 3 created wallet marketing. (Original PushNotice diagram; dates from public product histories.)
The pivotal moment for businesses was Wave 3, not Wave 2. Tap-to-pay made the wallet useful; passes made it a channel. Once a business could place a self-updating card on a customer's phone and message its lock screen for free, the wallet stopped being purely a payment device and became a marketing surface — which is the entire premise of this guide.
- Four waves: experiments, the NFC-plus-tokenization breakthrough, passes and tickets, and today's identity credentials.
- Apple Pay (2014) made tap-to-pay trustworthy; Passbook/Wallet (2012) made passes possible.
- The pass wave — not the payment wave — is what turned the wallet into a business channel.
The three wallets
Three apps hold almost every mobile wallet in the world: Apple Wallet on iPhone, Google Wallet on Android, and Samsung Wallet on Galaxy devices. They share a core model but differ in reach, features, and how businesses build for them. This part explains each in turn, then compares them head-to-head so you know exactly which platforms your program must support.
Apple Wallet explained
Apple Wallet is the built-in wallet app on every iPhone. It stores payment cards for Apple Pay (tap-to-pay via NFC), plus passes built on Apple's PassKit framework: boarding passes, event tickets, loyalty and store cards, coupons, transit, car keys, and — in supported regions — state IDs. Businesses issue passes as signed .pkpass files that customers save with one tap and that the business can update and notify remotely.
Apple Wallet (introduced as Passbook in 2012 and renamed in 2018) is pre-installed and cannot be removed, so it sits on effectively every iPhone in use. For consumers it does three things: it runs Apple Pay for contactless and online payments; it holds tickets and passes that surface when relevant; and it increasingly stores identity and access — car keys, hotel keys, corporate badges, transit cards, and driver's licenses where available.
For businesses, the important part is PassKit, Apple's framework for creating passes. A pass is a signed bundle tied to the issuer's Apple developer identity, which makes it tamper-evident. The relevant pass styles for marketing are the store card, coupon, generic, and event ticket types. Two capabilities matter most: remote updates (change the pass server-side and Apple Wallet pulls the new version, optionally showing a lock-screen notification) and relevance (a pass can specify locations and times so it surfaces on the lock screen when the customer is near your store or when an event approaches). Customers add a pass by tapping an "Add to Apple Wallet" button reachable from a link, an email, a QR code, or a website — no app download.
A coffee shop issues an Apple Wallet store card. A customer taps "Add to Apple Wallet" from a table QR code. Each purchase adds a stamp server-side; the card updates instantly and, at the ninth stamp, the shop pushes "One more for a free latte" to the lock screen. When the customer walks near the shop, the card surfaces automatically — ready to scan.
- Apple Wallet is pre-installed on every iPhone and runs Apple Pay plus PassKit passes.
- Business passes are signed
.pkpassbundles that update remotely and can notify the lock screen. - Location and time relevance surface a pass automatically when it matters most.
Google Wallet explained
Google Wallet is the built-in wallet app on Android. It stores payment cards for tap-to-pay, plus passes created through the Google Wallet API using a class (shared template) and object (individual card) model. It supports loyalty, gift, offer, generic, transit, event, and boarding passes, geofenced notifications, and — in supported regions — digital IDs. Android members save the same kinds of cards with an "Add to Google Wallet" button.
Google Wallet (relaunched in 2022, consolidating the older Google Pay and Android Pay efforts) is Android's counterpart to Apple Wallet and is pre-installed on the vast majority of Android phones. It runs contactless payments, holds tickets and passes, stores transit cards, and supports car keys and digital IDs where available.
For businesses, Google's model is a class plus object. The class is the template every customer's card shares — your branding, layout, and fields — defined once. The object is an individual customer's instance, carrying their balance, tier, ID, and code. Marketing passes typically use the loyalty, gift card, offer, or generic pass types. Updates work by patching the object through the API; Google Wallet reflects the change on the customer's phone and can raise a notification. Google Wallet also supports geofenced notifications (surface a message near a location) and smart-tap for NFC redemption where enabled.
Because Android has the larger global market share, Google Wallet is not optional for any serious program. A complete wallet strategy issues both an Apple Wallet and a Google Wallet version of the same card, generated from one customer record, so every customer — whichever phone they carry — can save the identical pass.
- Google Wallet is Android's pre-installed wallet, running payments and passes via the Google Wallet API.
- Its model is a class (template) plus an object (individual card); patch the object to update it.
- Android's global scale makes Google Wallet mandatory — issue both Apple and Google versions.
Samsung Wallet explained
Samsung Wallet is Samsung's wallet app for Galaxy phones, combining payments, passes, tickets, boarding passes, digital keys, and identity in one place. Its historical edge was MST (magnetic secure transmission), which let older Galaxy phones pay at magnetic-stripe terminals that lacked NFC — though newer devices increasingly rely on NFC like everyone else. For most businesses, Samsung devices are reached through Google Wallet passes; Samsung Wallet adds a Samsung-specific option on Galaxy hardware.
Samsung Wallet (which merged Samsung Pay and Samsung Pass in 2022) is the default wallet on Samsung Galaxy devices, a large share of the Android market. It stores payment cards, boarding passes, event tickets, loyalty cards, digital car and home keys, and IDs in supported regions. For consumers on Galaxy phones it is a full-featured wallet comparable to Apple's and Google's.
Its distinctive feature was MST: by emitting a magnetic field that mimics a card swipe, older Samsung phones could pay at terminals that only accepted magnetic stripe — a real advantage in markets slow to adopt NFC. As contactless terminals became universal, MST's importance faded, and Samsung's newer phones lean on NFC.
From a marketing standpoint, most businesses do not build a separate Samsung integration. Galaxy users can save Google Wallet passes, so a program that supports Apple Wallet and Google Wallet already reaches Samsung customers. Samsung Wallet becomes worth a dedicated look mainly for programs heavily weighted toward Galaxy users or in regions where Samsung Wallet has strong local partnerships. Understanding it matters for completeness, but it rarely changes the two-platform rule: build for Apple and Google first.
Think in two platforms, not three, when planning a build. Apple Wallet covers iPhone; Google Wallet covers Android including Samsung Galaxy devices. Samsung Wallet is a Galaxy-native alternative that layers on top — useful to know, rarely a separate integration for a small or mid-sized business.
- Samsung Wallet is the Galaxy-native wallet, merging payments, passes, keys, and identity.
- Its historical edge was MST for magnetic-stripe terminals; NFC has largely superseded it.
- Most businesses reach Samsung users through Google Wallet — build for Apple + Google first.
Apple vs Google vs Samsung Wallet
All three do the same core jobs — tap-to-pay, passes, tickets, and identity — but differ in reach and how businesses build for them. Apple Wallet covers iPhone via PassKit; Google Wallet covers Android (including Samsung) via the Wallet API; Samsung Wallet is a Galaxy-native option that also supported MST. For a business, the rule is simple: support Apple Wallet and Google Wallet, and Samsung customers are covered.
| Aspect | Apple Wallet | Google Wallet | Samsung Wallet |
|---|---|---|---|
| Platform | iPhone / iOS | Android (all brands) | Samsung Galaxy |
| Pre-installed | Yes | Yes | Yes (Galaxy) |
| Payment tech | NFC | NFC | NFC + MST (older) |
| Pass framework | PassKit (.pkpass) | Google Wallet API | Samsung Wallet / partners |
| Business build model | Signed pass bundle | Class + object | Usually via Google Wallet |
| Remote pass updates | Yes | Yes | Yes |
| Lock-screen notifications | Yes | Yes | Yes |
| Location relevance | Yes | Yes (geofence) | Yes |
| Digital ID (region-dependent) | Growing | Growing | Growing |
| Do businesses build separately? | Yes — Apple | Yes — Google | Rarely — covered by Google |
Never ship a single-platform program. Apple-only excludes every Android customer; Google-only excludes every iPhone customer. Choose software that generates both an Apple Wallet and a Google Wallet pass from one record and automatically shows the right "Add" button based on the customer's device. That one decision doubles your reachable audience at no extra effort.
- The three wallets share core jobs; they differ in reach and build model, not fundamentals.
- Apple Wallet = iPhone; Google Wallet = all Android including Samsung; Samsung Wallet = Galaxy-native add-on.
- Support Apple + Google and you reach essentially every smartphone customer.
What a wallet is not
"Mobile wallet," "digital wallet," "banking app," and "payment app" get used interchangeably, and the blur causes real confusion when businesses plan. This part draws three clean lines: mobile wallet vs the broader digital wallet, wallet apps vs banking apps, and wallet apps vs standalone payment apps.
Mobile wallet vs digital wallet
"Digital wallet" is the umbrella; "mobile wallet" is the phone-based member of that family. A digital wallet is any software that stores payment or credential data — including browser-based wallets like PayPal that live in the cloud. A mobile wallet is a digital wallet that runs as an app on a phone and can pay in person by tapping (NFC). Every mobile wallet is a digital wallet; not every digital wallet is mobile.
The terms overlap because a mobile wallet is a kind of digital wallet — but the umbrella is wider than the phone. A digital wallet is any system that stores payment methods and credentials in software: an online checkout wallet like PayPal, a browser's saved cards, an in-app balance. It may never touch a physical terminal. A mobile wallet is the subset that lives on a smartphone, is unlocked by the device's biometrics, and can present itself in the physical world by NFC or by displaying a scannable code. The defining extras of a mobile wallet are in-person presentation (tap to pay, scan a pass) and proximity (it's on the device the person always carries).
| Dimension | Digital wallet (umbrella) | Mobile wallet (subset) |
|---|---|---|
| Where it lives | Cloud, browser, or app | On the phone (native app) |
| In-person payment | Usually no | Yes — NFC tap |
| Holds business passes | Rarely | Yes — core feature |
| Examples | PayPal, browser autofill, in-app balances | Apple / Google / Samsung Wallet |
| Unlock method | Password / login | Face / fingerprint / passcode |
| Marketing channel? | Limited | Yes — lock-screen passes |
- Digital wallet is the category; mobile wallet is the phone-based member of it.
- Mobile wallets add in-person presentation (NFC/scan) and always-on proximity.
- The pass-and-notification channel is a mobile-wallet trait, not a general digital-wallet one.
Wallet apps vs banking apps
A banking app manages your money; a wallet app carries your cards and passes. The banking app (from your bank) shows balances, moves money, pays bills, and handles account admin. The mobile wallet holds tokenized copies of cards to spend, plus non-payment passes. They connect — you often add a card to the wallet from the banking app — but the wallet doesn't hold your account or run transfers, and the banking app doesn't carry your gym card or concert ticket.
The confusion is understandable because both deal with cards. The clean split is management vs presentation. A banking app is issued by a financial institution and is the control panel for an account: balances, statements, transfers, bill pay, card freezing, dispute filing. A mobile wallet is issued by the phone maker and is a presentation layer: it holds a tokenized version of a card so you can tap to pay, and it holds passes that have nothing to do with banking at all. Your bank balance does not live in Apple Wallet; your concert ticket does not live in your bank's app.
| Factor | Banking app | Mobile wallet app |
|---|---|---|
| Issued by | Your bank | Phone maker (Apple/Google/Samsung) |
| Core job | Manage the account | Present cards & passes |
| Move money / transfers | Yes | No |
| Tap to pay in store | Sometimes | Yes — primary |
| Holds loyalty, tickets, IDs | No | Yes |
| Multiple banks in one place | One bank | Many cards, any bank |
| Business marketing surface | No | Yes |
- Banking apps manage accounts; wallet apps present tokenized cards and passes.
- Wallets don't hold your balance or run transfers; banking apps don't hold tickets or loyalty cards.
- They link — you often add a card to the wallet from the banking app — but do different jobs.
Wallet apps vs payment apps
A payment app does one thing — move money — while a mobile wallet is a broader container that includes payment but adds passes, tickets, and identity. Apps like PayPal, Venmo, Cash App, or a merchant's own pay-app focus on sending, receiving, or accepting payment. A mobile wallet can pay too, but its wider job is carrying everything else a wallet holds. Payment apps are a feature; mobile wallets are the container.
Standalone payment apps — peer-to-peer apps like Venmo and Cash App, checkout wallets like PayPal, or a single retailer's pay-and-earn app — are purpose-built to transact. They're excellent at that one job and often add social or rewards features around it. But they are single-purpose: Venmo won't hold your boarding pass, and your bank's pay-app won't store a rival shop's loyalty card. A mobile wallet is deliberately general: it pays and holds any business's passes and carries identity, all in one pre-installed place. For a business, the difference is decisive — a payment app reaches only its own users, while a wallet pass reaches every customer through the wallet already on their phone.
| Factor | Standalone payment app | Mobile wallet app |
|---|---|---|
| Primary purpose | Move / accept money | Carry cards, passes & IDs |
| Scope | Single-purpose | General container |
| Holds non-payment passes | No | Yes |
| Pre-installed | Must download | Built in |
| Reaches all customers | Only its users | Anyone with the phone's wallet |
| Examples | PayPal, Venmo, Cash App | Apple / Google / Samsung Wallet |
The reach difference is the whole point. To market through a payment app, your customer must already use that app. To market through a mobile wallet, they only need the wallet their phone shipped with — which is essentially all of them. That near-universal, no-download base is why wallet passes are a broader channel than any single payment app can be.
- Payment apps are single-purpose money movers; wallets are general containers that include payment.
- Only wallets hold non-payment passes and come pre-installed on the phone.
- Wallets reach every customer through a built-in app; payment apps reach only their own users.
Types of wallet passes
A wallet pass is any business-issued card a customer saves to their mobile wallet. There are eight everyday types, each solving a different job, and knowing them is the foundation of wallet marketing. This part defines each pass type, shows what it carries, and maps them into one reference table and diagram.
Types of wallet passes
The main wallet pass types are loyalty cards, membership cards, coupons, gift cards, event tickets, boarding passes, store cards, and identity cards. All share the same superpowers — one-tap save, remote updates, a scannable code, and lock-screen notifications — but each carries different data and serves a different goal, from earning rewards to proving who you are. A ninth, the transit pass, blends payment and ticketing.
Wallet pass — a digital card stored in a mobile wallet, built on Apple PassKit or the Google Wallet API, that a business issues, updates remotely, and can use to send lock-screen notifications. Every pass carries branding, some payload of data (a balance, a seat, a code), and a scannable QR code or barcode for redemption or access.
Loyalty cards
A loyalty card tracks accumulating rewards — points, stamps, or visits — and is the workhorse of wallet marketing. It shows the current balance ("7 of 10 stamps"), updates the instant a purchase is logged, and notifies when a reward is earned or close. Because the balance is live, the customer always sees how near they are to the next reward, which drives return visits. See our companion guide, Customer Loyalty Cards.
Membership cards
A membership card proves belonging and status rather than tracking rewards. It carries a member ID, tier, and renewal date, and is scanned to verify access — a gym, club, association, or museum member. It updates when a member upgrades or renews. See Digital Membership Cards.
Coupons & offers
A coupon (Apple's coupon style; Google's offer type) carries a discount or promotion with an expiry. Saved to the wallet, it can surface by location ("you're near the store — 20% off today") and time, and it disappears or greys out when redeemed or expired, so it never looks stale. Coupons are the most direct wallet path from awareness to purchase.
Gift cards
A gift card stores a prepaid balance that decrements as it's spent. In a wallet it can't be lost like plastic, shows the live remaining balance, can be reloaded, and can notify when the balance runs low — a nudge to top up and return.
Event tickets
An event ticket carries the event, seat, and entry code. It surfaces on the lock screen as the event approaches and at the venue by location, updates if a time or gate changes, and scans for entry. It removes printed tickets and the "which email was it in?" scramble.
Boarding passes
A boarding pass is the travel sibling of the event ticket: flight, seat, gate, and boarding time on a pass that updates in real time (a gate change refreshes the card and can notify) and surfaces automatically at the airport. It's the pass type most travelers already trust in their wallet.
Store cards
A store card represents a retailer account or prepaid store balance, often blending a loyalty balance, member pricing, and a payment or account code in one pass. It's the retail all-rounder — identity, rewards, and sometimes value together.
Identity cards
An identity card in the wallet ranges from a member or employee ID to, increasingly, government credentials — state IDs and driver's licenses in supported regions, plus digital car and hotel keys and corporate access badges. These carry the highest security and privacy stakes and are the frontier of the credential wallet.
A transit pass blends payment and ticketing — a stored-value or account-based fare card that taps to ride the bus, train, or metro. Many cities now let riders tap a bank card or a dedicated transit pass in the wallet directly at the gate, making transit one of the most-used wallet features worldwide.
Figure 4 — The eight wallet pass types. Loyalty, membership, coupon, gift card, event ticket, boarding pass, store card, and identity — each a different payload on the same wallet-pass foundation. (Original PushNotice diagram.)
| Pass type | Carries | Core job | Signature move |
|---|---|---|---|
| Loyalty card | Points / stamps balance | Reward repeat purchases | Updates balance live; reward nudge |
| Membership card | Member ID, tier, expiry | Prove belonging & access | Tier change; renewal reminder |
| Coupon / offer | Discount, code, expiry | Drive a purchase now | Location + time surfacing |
| Gift card | Prepaid balance | Store & spend value | Live balance; low-balance nudge |
| Event ticket | Event, seat, entry code | Admit to an event | Surfaces at venue; live updates |
| Boarding pass | Flight, seat, gate | Board a flight | Real-time gate updates |
| Store card | Account, balance, code | Retail identity + value | Blends loyalty, pricing, payment |
| Identity card | ID, credential, key | Prove identity / grant access | Tap to verify or unlock |
| Transit pass | Fare value / account | Pay to ride | Tap at the gate |
- Eight everyday pass types — loyalty, membership, coupon, gift card, event ticket, boarding pass, store card, identity — plus transit.
- All share one-tap save, live updates, a scannable code, and notifications; each carries different data.
- Loyalty and coupons are the entry points to wallet marketing; identity is the frontier.
Mobile wallet marketing
Here is where the mobile wallet stops being a consumer convenience and becomes a business channel. This part explains why businesses reach for wallet passes, what mobile wallet marketing actually is, how its notifications work, and how it drives loyalty and retention — with the benefits laid out for both sides of the counter.
Why businesses use mobile wallet apps
Businesses use mobile wallets because they combine three things no other channel offers at once: near-universal reach with no app to build, a free lock-screen notification channel, and self-updating, scannable cards that produce first-party data. The wallet is already on the customer's phone, saving a pass takes one tap, and every notification and scan is owned and costs nothing per message.
Every marketing channel makes a trade-off. Email is cheap but buried and ignored; SMS is immediate but costs per message and fatigues fast; apps are powerful but almost no one installs them. The mobile wallet is compelling precisely because it dodges each of those weaknesses at the same time.
Near-universal reach, no app. Apple Wallet and Google Wallet ship on every phone. There is no download wall, no app-store review, no five-star hurdle. A customer saves your card in one tap and it lives beside their boarding passes and bank cards. A free, unfiltered channel. Once the pass is saved, you can push a lock-screen notification for a reward, an offer, or a reminder — with no per-message fee and no spam folder to fight. Self-updating cards. The pass is a live record; a balance, a tier, or an offer changes centrally and refreshes on every phone at once. First-party data. Every save, scan, and redemption is consented, owned data — increasingly valuable as third-party cookies disappear.
Three forces converged. Retaining a customer is far cheaper than acquiring one, so a channel built for repeat visits pays back quickly. Wallets are now on essentially every phone, so distribution is free. And a decade of low app-install rates taught businesses that the pass — not the custom app — is what customers actually keep. The wallet sits exactly where those three forces meet.
- Wallets combine near-universal reach, a free notification channel, live cards, and owned data — at once.
- No app to build or install: a save is one tap into an app the customer already has.
- The economics favor retention, and the wallet is a retention-first channel.
Mobile wallet marketing explained
Mobile wallet marketing is the practice of using wallet passes — loyalty cards, coupons, memberships, and more — as an owned marketing and retention channel. A business issues a pass, distributes a one-tap Add-to-Wallet link, and then uses free lock-screen and location notifications to bring customers back, all without a mobile app. It sits alongside email and SMS as a third owned channel, distinguished by proximity and zero per-message cost.
Mobile wallet marketing (wallet marketing) — reaching and retaining customers through passes stored in Apple Wallet, Google Wallet, and Samsung Wallet. The pass is the durable presence on the customer's phone; the notification is the message; the scan is the redemption; and the data from all three is the feedback loop.
Wallet marketing runs a simple loop: issue a pass, distribute it, engage through notifications, redeem at the counter, and learn from the data — then repeat. What makes it distinct from email and SMS is the medium. The pass is not a message that arrives and is gone; it is a persistent object that lives in the wallet, updates itself, and surfaces on the lock screen when it's relevant. The customer doesn't have to open anything to see their stamp count grow or a nearby offer appear.
The Mobile Wallet Marketing Funnel™ below frames the stages. Awareness and acquisition get the pass saved; activation and engagement bring the customer back through the card and its notifications; and retention and advocacy compound as the relationship deepens. Unlike a linear ad funnel, the wallet funnel loops — each redemption is another chance to notify, reward, and return.
Figure 5 — The Mobile Wallet Marketing Funnel™. Awareness and acquisition get the pass saved; activation, engagement, and retention compound through the card and its notifications. (Original PushNotice framework.)
| Factor | Wallet marketing | SMS | |
|---|---|---|---|
| Cost per message | $0 | Very low | Per message |
| Spam / inbox filtering | None | Heavy | Some |
| Lock-screen presence | Native | No | On arrival |
| Self-updating content | Yes | No | No |
| Location targeting | Yes | No | No |
| Depth / long content | Limited | Rich | Short |
| Best role | Timely, in-context nudges | Depth & reach | Urgent, two-way |
Wallet marketing does not replace email and SMS — it completes them. Email carries depth and reach; SMS carries urgency; the wallet carries the persistent, in-context layer neither can: a living card on the phone that surfaces itself at the right place and time, for free. The strongest programs use email or SMS to invite the wallet save, then run day-to-day loyalty through the pass. See Wallet vs Email and Wallet vs SMS.
- Wallet marketing uses passes as an owned channel: issue, distribute, engage, redeem, learn — then loop.
- Its edge over email and SMS is proximity, self-updating cards, and zero per-message cost.
- It complements, not replaces, email and SMS — use them to drive the wallet save.
Wallet notifications
A wallet notification is a lock-screen message a business pushes to a saved pass — free, unfiltered, and highly visible. It fires when the business updates the pass (a new stamp, a reward, an expiring offer) and appears without the customer opening any app. Because the lock screen is high-trust, the rule is to send only genuine value; over-notifying gets passes deleted, which closes the channel for good.
The lock screen is the most valuable and most fragile surface in marketing. A wallet pass that lives there earns visibility email and SMS can only envy: no per-message fee, no spam filter, near-guaranteed sight. But customers punish abuse instantly by deleting the pass, which permanently closes the channel. The governing rule is simple — notify only when the customer would thank you for it.
| Notification | Trigger | Send? |
|---|---|---|
| Reward earned / near | Balance crosses a threshold | Yes — high value |
| Expiring offer / credit | Coupon near expiry | Yes — urgency |
| New stamp / points added | Purchase logged | Yes — progress |
| Location arrival | Customer near the store | Yes — in context |
| Ticket / gate update | Event or flight change | Yes — essential |
| Genuinely relevant offer | Segment-matched promo | Sparingly |
| Generic broadcast blast | "Sale this weekend" to all | No — erodes trust |
| Repeated same nudge | Re-sending an ignored message | No — deletes passes |
Treating the wallet like an email list and blasting every promotion to every pass holder. The lock screen has no spam folder to absorb the noise, so the customer's only defense is deleting the pass — and once deleted, that channel is gone. Restraint is not timidity here; it is what keeps the channel alive.
- Wallet notifications are free, unfiltered, and highly visible — but the lock screen is fragile.
- Send only high-value triggers: rewards, expiring offers, progress, arrival, essential updates.
- Over-notifying gets passes deleted, permanently closing the channel.
Location- & time-based notifications
Wallet passes can surface on the lock screen based on where the customer is or what time it is. A pass can carry locations, so it appears when the customer is near your store; it can carry times, so a ticket surfaces as the event approaches. This context-aware surfacing — the right card at the right moment — is unique to wallets and runs through the platforms' privacy-preserving mechanisms, so the business never receives a live location feed.
Two forms of context turn a passive card into a timely prompt. Location-based: a pass can specify one or more geolocations, and when the customer is nearby, Apple Wallet or Google Wallet can raise it on the lock screen — a coffee loyalty card as they pass the shop, a museum membership as they arrive, a coupon within range of the store. Time-based: a pass can specify relevant times, so a concert ticket or boarding pass surfaces as the moment approaches. Both can carry a short message ("Welcome back — your reward is one stamp away").
Two guardrails matter. First, privacy: proximity is handled by the operating system, not by the business. You register a location on the pass; the phone decides when the customer is near and surfaces the card. You do not get a stream of where your customers are. Second, restraint: a card that appears helpfully at your door is welcome; one that fires far from any real relevance is annoying and gets the pass deleted. Treat location like notifications — reserve it for genuine, in-context value.
Figure 6 — Location- and time-based surfacing. The pass carries the triggers; the phone decides when they're met and surfaces the card. The business sees a redemption, not a location trail. (Original PushNotice diagram.)
- Passes surface by location (near a venue) and time (event approaching) — context-aware prompts unique to wallets.
- Proximity is privacy-preserving: the OS decides, and no live location feed reaches the business.
- Use it for in-context value at arrival, not repeated or irrelevant pop-ups.
Retention, loyalty & membership
The mobile wallet is fundamentally a retention channel: it excels at bringing existing customers back, not at first-touch acquisition. Loyalty cards reward repeat purchases, membership cards lock in belonging and renewals, and coupons pull customers back for the next visit — all on a card that lives on the phone and nudges at the right moment. Because retaining a customer is far cheaper than acquiring one, that focus is exactly where the money is.
Not every channel is built for the same job. Search and social are acquisition channels — they find new people. The wallet is a retention channel — it deepens the relationship with people you already have. That's a feature, not a limitation: retention economics are powerful. Acquiring a new customer typically costs several times more than keeping an existing one, and small improvements in repeat-visit rate compound into large revenue gains.
The wallet drives retention three ways. Loyalty: a live stamp or points balance uses the goal-gradient effect — motivation rises as the reward nears — and the card keeps that goal visible between visits. Membership: a card carrying tier and renewal date, with a well-timed reminder, recovers memberships that would otherwise lapse silently. Offers: a location- or time-triggered coupon pulls a customer back at the moment intent is highest. Each mechanic is a reason to return, delivered on the one screen the customer always has.
Widely cited research attributed to Bain & Company (via Harvard Business Review) finds that acquiring a customer can cost 5–25× more than retaining one, and that a 5% lift in retention can raise profits 25–95%. A channel purpose-built for repeat visits — which the wallet is — therefore pays back faster than one built for first-touch reach. Figures are dated because they change; see Sources.
- The wallet is a retention channel — its strength is bringing existing customers back.
- Loyalty, membership, and offers each give a reason to return, delivered on the lock screen.
- Retention economics (5–25× cheaper than acquisition) make that focus high-leverage.
Benefits for businesses & customers
Mobile wallets benefit businesses through lower cost, higher retention, a free channel, and owned data — and customers through convenience, security, and a lighter wallet. The strongest programs deliver both at once: the business gets a durable, measurable line to the customer, and the customer gets cards that are always with them, always current, and safer than plastic.
For the business
Lower cost — no printing, plastic, or postage; issuing and updating a pass is a record change. Higher retention — live cards and timely nudges bring customers back. A free channel — lock-screen notifications with no per-message fee and no spam folder. Owned first-party data — every save, scan, and redemption is consented and yours. Instant changes — update branding, an offer, or a balance across every card with one push. No app to build — the customer already has the wallet.
For the customer
Always available — cards live on the phone they already carry. Always current — balances and details update without a reprint. Safer — tokenized payments and signed passes are harder to steal or forge than plastic; nothing spills a card number. One tap to save — no app, no account friction. A lighter wallet — the whole stack of plastic collapses into one screen. Timely, low-noise reminders — a nudge only when it matters.
- Business gains: lower cost, higher retention, a free channel, owned data, instant changes, no app.
- Customer gains: always-available, always-current, safer cards saved in one tap.
- The best programs deliver both sides at once — that alignment is the case for wallet marketing.
Implementation
From understanding to doing. This part is the operational core: how a customer's pass actually gets onto their phone, the end-to-end workflow behind a wallet program, how to choose the software that runs it, how push notifications work technically, and the security and privacy responsibilities the channel carries.
How businesses add customers to wallet
Customers add a pass by tapping an "Add to Apple Wallet" or "Add to Google Wallet" button — reached from a QR code, a link, a website, an email, an SMS, or a checkout page. The best programs put that one-tap button everywhere a customer already is: at signup, at the point of sale, on the receipt, and on the counter as a QR code. The save takes seconds and requires no app.
Getting the pass onto the phone is the single most important conversion step in wallet marketing, and it's designed to be nearly effortless. The mechanism is always the same: a one-tap "Add to Wallet" button that detects the customer's device and offers the right version. What varies is where you place it. The rule is to meet the customer at moments of natural intent rather than asking them to go somewhere new.
| Placement | Moment of intent | Best for |
|---|---|---|
| Counter / table QR code | In-store, deciding to return | Cafés, restaurants, retail |
| Point of sale / receipt | Just after paying | Any physical business |
| Signup / onboarding form | Joining the program | Memberships, loyalty |
| Checkout / order confirmation | Completing a purchase | E-commerce, ticketing |
| Email & SMS link | Reading a message | Existing lists |
| Website / landing page | Researching the brand | Always-on acquisition |
| Social bio / ad | Discovering the brand | Campaigns |
Make the counter QR code your default. A printed "Scan to save your loyalty card" at the register captures the customer at the exact moment they've decided your product is worth returning for — the highest-intent, lowest-cost acquisition point in the whole funnel. Pair it with a small first-visit incentive to convert the save.
- A one-tap Add-to-Wallet button that auto-detects the device is the universal mechanism.
- Place it at moments of intent: counter QR, point of sale, signup, checkout, email/SMS, website.
- The in-store QR at the register is often the highest-intent, lowest-cost save.
The wallet marketing workflow
The workflow runs in six steps: choose the pass type, choose software, design the pass, distribute the Add-to-Wallet link, engage with notifications, and measure. A basic program can launch in an afternoon; depth like POS integration and segmentation comes later. The sequence matters — decide the goal and pass type before you design anything.
The Wallet Experience Blueprint™ sequences the build so each step sets up the next. The most common failure is designing a beautiful card before deciding what job it does; teams then rebuild. Do it in order.
Step 1 — Choose the pass type. Loyalty to reward repeat purchase, membership for belonging, coupon to drive a visit, gift card to store value, ticket to admit. The goal picks the type. Step 2 — Choose software that issues both Apple and Google passes, updates them, and sends notifications (see the next section). Step 3 — Design the pass: branding, the payload (balance, tier, offer), a scannable code, and relevant locations. Step 4 — Distribute: place the one-tap Add-to-Wallet button at every high-intent moment; connect it to your POS or CRM so records stay in sync. Step 5 — Engage: reserve notifications for genuine value — rewards, expiring offers, arrival. Step 6 — Measure: track saves, activation, redemption, and repeat visits; refine the offer and cadence.
Figure 7 — The Wallet Experience Blueprint™. Six sequenced steps: pass type → software → design → distribute → engage → measure. Decide the goal before you design. (Original PushNotice framework.)
- Six steps: choose pass type, choose software, design, distribute, engage, measure.
- Decide the goal and pass type before designing — it drives every later step.
- A basic program launches in an afternoon; integration and segmentation come later.
Choosing wallet marketing software
Choose wallet software by the jobs it must do: issue and update both Apple and Google Wallet passes, support your pass types, send free notifications with location and time targeting, provide analytics and an API, integrate with your POS, CRM, and Shopify, and price on a flat fee rather than per pass or per message. Score candidates against fixed criteria and compare totals rather than buying on a demo impression.
Wallet software spans three broad types. Wallet-pass / wallet-marketing platforms specialize in creating, updating, and notifying Apple and Google passes and integrating with the tools you already use — the best fit for most businesses that want the card and channel fast. All-in-one loyalty or POS suites bundle wallet passes into a wider system, convenient but sometimes with basic passes. Developer APIs (PassKit and the Google Wallet API directly) give engineering teams full control at the cost of building and maintaining it. Match the type to whether wallet is your focus, a feature of a bigger system, or something you'll build in-house.
| Criterion | What "strong" looks like | Why it matters |
|---|---|---|
| Apple Wallet support | Native, self-updating passes | Reaches every iPhone customer |
| Google Wallet support | Native, self-updating passes | Reaches every Android customer |
| Pass types | Loyalty, coupon, membership, gift, ticket | Matches your goal |
| Notifications | Free, triggered, location + time | The owned channel |
| Automation | Rules & triggered workflows | Scales without staff time |
| Analytics | Saves, activation, redemption, retention | Measure what matters |
| API | Documented, complete | Integrate & automate |
| POS / CRM integration | Sync members & award at checkout | One source of truth |
| Shopify integration | Issue at checkout | For e-commerce |
| White label | Your brand, not the vendor's | Trust & agencies |
| Pricing model | Flat, not per-pass / per-message | Predictable at scale |
| Ease of use | Launch without engineers | Small-team friendly |
| Support | Responsive, knowledgeable | You'll need it live |
Weight before you score. A single café should weight both wallets, ease of use, and notifications heavily and can ignore agency features; an agency should weight white-label, multi-client management, and the API. Rate each candidate 0–2 per criterion, apply your weights, and compare totals — a scored comparison surfaces the Google Wallet gap or the missing automation that a polished demo hides.
To be transparent: PushNotice is a wallet-marketing platform. It creates Apple Wallet and Google Wallet passes — loyalty, membership, coupons, gift cards, store cards, and tickets — from one record, sends free lock-screen and location notifications, provides analytics and an API, and prices on a flat subscription rather than per pass or per message. It is a strong fit for businesses that want the card and channel without building an app. The criteria above stand on their own regardless of which platform you pick.
- Non-negotiables: both wallets, your pass types, free targeted notifications, analytics, an API, and flat pricing.
- Match the software type to whether wallet is your focus, a feature, or an in-house build.
- Score and weight candidates — a demo hides the gaps a scored comparison reveals.
How push notifications work
A wallet push notification works by the business updating the saved pass server-side; the wallet then pulls the change and can display a lock-screen note — no separate messaging app or per-message fee. On Apple this uses PassKit's push-update service; on Google, the Wallet API. It differs from app push (which needs an installed app and its own opt-in) because the "app" is the pre-installed wallet, and the notification rides on the pass the customer already saved.
It helps to distinguish two kinds of "push." App push notifications require the customer to have installed your app and granted it notification permission; you then send messages through Apple's or Google's push services. Wallet push is subtly different and simpler for the business: the customer saves a pass (which itself is the permission), and thereafter you trigger a notification by updating the pass. You change a field server-side — a new stamp, an expiring offer, a gate change — the platform notifies the device, the wallet re-renders the pass, and a lock-screen message can appear.
Mechanically: your software (or PushNotice) holds the pass record. When something changes, it signals Apple's PassKit update service or Google's Wallet API. The customer's phone receives a lightweight ping, fetches the updated pass, and shows the notification text you attached. There is no message body sent through a carrier (unlike SMS) and no inbox to land in (unlike email) — the update is the message. That's why it's free per message and why it can't be filtered as spam: it's a system-level pass refresh, not a third-party message.
Figure 8 — How wallet push works. A server-side pass update propagates through the platform to the phone, which fetches the pass and shows the note. (Original PushNotice diagram.)
- Wallet push works by updating the saved pass; the update itself carries the notification.
- The saved pass is the permission — no separate app or opt-in like app push needs.
- Because it's a system-level pass refresh, it's free per message and can't be spam-filtered.
Security
Mobile wallets are generally more secure than physical cards: payments are tokenized (the real card number is never shared), transactions require biometric authorization, and passes are cryptographically signed so they can't be forged. The customer's data sits in a hardware-isolated secure element. For businesses issuing passes, the main duty is to verify status server-side at scan time rather than trusting a card's appearance.
Security operates at two layers. On payments, three mechanisms combine: tokenization (the merchant receives a device token, never your real number), biometric authorization (a face or fingerprint approves each transaction), and hardware isolation (the token lives in a secure element cut off from the operating system). A per-transaction cryptogram means even a captured token can't be replayed. This is why tapping to pay is generally safer than swiping or inserting plastic — and why a lost phone is far less dangerous than a lost card, since nothing works without the owner's biometrics.
On passes, each is cryptographically signed by the issuer, so a forged or tampered pass fails validation, and passes carry no payment credentials — just an ID, a balance, or a status. The business's responsibility is to verify at scan time: resolve the scanned code against the live record rather than trusting how the card looks. A screenshot of a loyalty card is worthless if the code it shows resolves to a redeemed or expired record.
| Risk | Mechanism | Effect |
|---|---|---|
| Card number stolen at merchant | Tokenization | Real number never shared |
| Unauthorized payment | Biometric authorization | Only the owner can pay |
| Data extracted from phone | Secure element isolation | Credentials walled off |
| Captured transaction replayed | One-time cryptogram | Token can't be reused |
| Forged / tampered pass | Cryptographic signing | Fails validation |
| Screenshot / copied pass reused | Server-side verification | Resolves to live status |
| Lost or stolen phone | Remote wipe / revoke | Credentials disabled |
Trusting the card's face. If staff wave through anyone whose pass merely looks valid, a single screenshot defeats the system. Always scan and resolve to the live record — that one habit closes the most common form of pass abuse.
- Payments are secured by tokenization, biometrics, hardware isolation, and one-time cryptograms.
- Passes are signed and payment-free; a lost phone is safer than a lost card.
- Business duty: verify pass status server-side at scan time, never by appearance.
Privacy
Mobile wallets are designed to limit what businesses learn: the platform handles location proximity without giving the business a live location feed, payments are tokenized, and pass data is limited to what the business needs to run the program. The data a business does get — saves, scans, redemptions, and consented profile fields — is first-party and owned. The obligation is to collect only what's needed, secure it, and be transparent about its use.
Privacy in the wallet is a shared responsibility, and the platforms deliberately hold back data from businesses. When a pass surfaces by location, the phone decides proximity; the business registers a location on the pass but never receives a stream of where customers are. Payments are tokenized, so the merchant doesn't learn the card number. This design means wallet marketing is inherently more privacy-respecting than cookie-based tracking — the business sees relationship data (this customer saved a card, earned a reward, redeemed an offer), not surveillance data.
That relationship data is genuinely valuable precisely because it is first-party and consented: the customer chose to save the pass. As third-party cookies decline, owned wallet data becomes a primary marketing asset. But value comes with duty. The business should practice data minimization (collect only what the program needs), secure the records, honor deletion and opt-out requests, and be transparent — a clear privacy note on the pass back and site. Treat the consented channel as a trust relationship, and it stays a channel; abuse it, and customers delete the pass.
The wallet's privacy model and its marketing value point the same direction. Because the platform withholds surveillance data and gives the business only consented relationship signals, wallet marketing is durable in a post-cookie world — it was never built on tracking. The businesses that treat that data respectfully keep both the trust and the channel.
- Platforms limit business data: no live location feed, tokenized payments, minimal pass data.
- What the business gets is first-party, consented relationship data — valuable and post-cookie durable.
- Duty: minimize, secure, honor opt-outs, and be transparent about use.
The PushNotice wallet frameworks
This part collects the original models behind a modern wallet program into one reference — a maturity model to place your program, an ecosystem map to see the connections, an adoption curve to read the market, a flywheel and pyramid for engagement and loyalty, a journey for the customer, and an identity framework for the credential frontier. Each is meant to be quoted, adapted, and built on.
Original frameworks & the wallet knowledge graph
Nine original PushNotice frameworks map mobile wallet marketing end to end — from the funnel a customer travels and the maturity a program reaches, to the ecosystem it plugs into and the identity layer it's growing toward. The index below places each, and the knowledge graph ties the domain's core entities together with explicit relationships.
| Framework | Answers the question | Where |
|---|---|---|
| Mobile Wallet Marketing Funnel™ | What stages does a customer move through? | Figure 5 |
| Wallet Experience Blueprint™ | How do we build the program step by step? | Figure 7 |
| Wallet Marketing Maturity Model™ | How advanced is our program? | Figure 9 & Table 12 |
| Mobile Wallet Ecosystem™ | How does the wallet connect to our stack? | Figure 10 |
| Digital Wallet Adoption Curve™ | Where is the market, and our customers? | Figure 11 |
| Wallet Engagement Flywheel™ | How does engagement compound? | Figure 12 |
| Wallet Loyalty Pyramid™ | How should loyalty value escalate? | Figure 13 |
| Customer Wallet Journey™ | What does the customer experience, moment to moment? | Below |
| Digital Identity Framework™ | How far into credentials should we go? | Below |
The Wallet Marketing Maturity Model™
Not every program is at the same stage, and knowing your level tells you the next move. The maturity model runs from Level 0 (no wallet presence) to Level 4 (predictive, personalized wallet marketing). Most businesses sit at Level 1–2 and can capture large gains simply by reaching Level 3.
Figure 9 — The Wallet Marketing Maturity Model™. Five levels from no wallet presence to predictive personalization. (Original PushNotice framework.)
| Level | Stage | What it looks like | Next move |
|---|---|---|---|
| 0 | No wallet | Plastic cards or none; email/SMS only | Issue one wallet pass |
| 1 | Pass issued | An Apple + Google pass customers can save | Turn on notifications |
| 2 | Engaging | Triggered lock-screen & location notifications | Instrument analytics |
| 3 | Data-driven | Save/redemption/retention dashboards, segments | Personalize by segment |
| 4 | Predictive | Lapse prediction, personalized offers & tiers | Continuous optimization |
The Mobile Wallet Ecosystem™
The wallet is not an island. The Mobile Wallet Ecosystem™ shows the pass as the identity-and-engagement hub connecting the rest of the stack — POS, CRM, e-commerce, email, SMS, and analytics — with the wallet platform in the middle translating one customer record into passes on every phone.
Figure 10 — The Mobile Wallet Ecosystem™. The wallet pass as the hub connecting POS, CRM, e-commerce, email, SMS, and analytics. (Original PushNotice framework.)
The Digital Wallet Adoption Curve™
Adoption is not uniform — it varies by age, region, and use case. The Digital Wallet Adoption Curve™ maps the familiar innovation curve onto wallets: payments have crossed into the early majority, passes and tickets are climbing fast, and identity credentials are still with innovators and early adopters. Knowing where your customers sit tells you how hard to push and which pass type will land.
Figure 11 — The Digital Wallet Adoption Curve™. Payments are mainstream, passes and tickets are crossing into the early majority, identity is still early. Position by use case, not by "wallets" as a whole. (Original PushNotice framework; positions are illustrative.)
The Wallet Engagement Flywheel™
Engagement compounds. The Wallet Engagement Flywheel™ shows the loop: a saved pass earns a reward, the reward prompts a return visit, the visit generates data, and the data sharpens the next offer — which earns the next reward. Each turn lowers the cost of the next return.
Figure 12 — The Wallet Engagement Flywheel™. Save → reward → return → data → sharper offer — each turn lowers the cost of the next return. (Original PushNotice framework.)
The Wallet Loyalty Pyramid™
Loyalty value should escalate. The Wallet Loyalty Pyramid™ orders what a program delivers, bottom to top: convenience (the card is always there), rewards (points and stamps), recognition (status and personalization), and belonging (identity with the brand). You can't skip levels — recognition means nothing if the card is a hassle to use.
Figure 13 — The Wallet Loyalty Pyramid™. Convenience, then rewards, recognition, and belonging. Higher levels only matter once the lower ones hold. (Original PushNotice framework.)
The Customer Wallet Journey™ & Digital Identity Framework™
Two more lenses complete the set. The Customer Wallet Journey™ traces the moment-to-moment experience: discover the offer, save the pass in one tap, use it at the counter, get reminded by a timely notification, return, and become a regular. Mapping your program to these moments reveals where saves stall or engagement leaks. The Digital Identity Framework™ addresses the credential frontier — how far into identity a program should go. It stages the choice from basic identity (a member ID on the pass), to access (the pass unlocks a door or event), to verified identity (government-grade credentials), each step adding value and privacy responsibility. Most businesses live at the first two stages; the third belongs to institutions with the security posture to match.
Customer Wallet Journey™ — the six moments: Discover → Save → Use → Remind → Return → Regular. Digital Identity Framework™ — the three stages: Basic identity → Access → Verified identity. Score your program on each; the weakest moment or the right identity stage is usually your next move.
The mobile wallet knowledge graph
To make the domain's semantics explicit — for readers and for the AI systems that increasingly parse these relationships — the graph below connects the core entities. A mobile wallet app holds wallet passes and payment cards, runs on a smartphone, uses NFC and QR codes, enables wallet marketing, sends notifications, and generates first-party data.
Figure 14 — The mobile wallet app knowledge graph. Core entities and their relationships, made explicit for readers and machines. (Original PushNotice diagram.)
Alongside the nine frameworks, this guide contributes reference tools built to be cited: the Wallet Platform Comparison Matrix™ (Table 1), the Wallet Channel Comparison™ (Table 6, wallet vs email vs SMS), the Wallet Software Evaluation Checklist™ (Table 9), the Wallet Notification Playbook™ (Table 7), and the Digital Wallet Readiness Assessment™ (the Maturity Model in Table 12). Reuse them with attribution.
| Entity | Relationship | Connected entity |
|---|---|---|
| Mobile wallet app | holds | Wallet passes & payment cards |
| Mobile wallet app | runs on | Smartphone (iOS / Android) |
| Mobile wallet app | uses | NFC, QR code, barcode |
| Mobile wallet app | enables | Wallet marketing |
| Wallet pass | sends | Lock-screen notifications |
| Wallet pass | generates | First-party data |
| Payment | secured by | Tokenization |
| Wallet marketing | drives | Customer retention |
- Nine frameworks cover funnel, build, maturity, ecosystem, adoption, engagement, loyalty, journey, and identity.
- The Maturity Model™ tells you your next move; the Adoption Curve™ reads the market by use case.
- The knowledge graph makes the domain's relationships explicit for readers and AI systems.
State of Mobile Wallet Marketing 2026
A structured read on where the category stands. This section separates verifiable facts (attributed to named public sources) from illustrative examples (clearly labeled models to reason with, not measured findings). We do not present illustrative figures as research results. The methodology and a transparency note close the section.
State of Mobile Wallet Marketing 2026
Digital wallets have crossed into the mainstream for payments and are climbing fast for passes and tickets, with several billion users worldwide and a majority of consumers in many markets using wallets regularly. For businesses, the frontier is the non-payment pass — loyalty, coupons, and memberships — where adoption still trails consumer readiness, leaving a clear opening. The figures below are split into verifiable and illustrative.
Verifiable market signals
These figures come from named public sources and reflect widely reported trends as of the mid-2020s. Verify against the primary source before republishing; numbers change.
| Signal | Figure | Source (see Sources) |
|---|---|---|
| Digital wallet users worldwide | ~5.2–5.4B by mid-2020s | Juniper Research (via Capital One Shopping) |
| U.S. consumers using digital wallets regularly | Majority (~53%+ use over cash/cards) | Forbes Advisor survey |
| Consumers in a loyalty / membership program | ~90% belong to at least one | Statista (via Capital One Shopping) |
| Retention vs acquisition cost | 5–25× cheaper to retain | Bain & Company (via HBR) |
| Profit lift from 5% retention gain | 25–95% | Reichheld, Bain & Company (via HBR) |
| Wallet notification per-message cost | $0 | Structural (PassKit / Wallet API) |
Illustrative model — the adoption gap
The figures in this subsection are an illustrative model to reason with, not survey results or PushNotice proprietary data. They express a directional pattern we observe qualitatively — high consumer wallet readiness, lower business pass adoption — not a measured statistic. Do not cite them as research findings.
The central story of 2026 is a gap. Consumers are ready — the wallet is on their phone and they already use it to pay and to hold tickets. But many businesses, especially small and mid-sized ones, still market only through email, SMS, and plastic, leaving the wallet-pass channel unused. That gap between consumer readiness and business adoption is the opportunity: the customers are already in the wallet; the businesses just haven't met them there.
Figure 15 — The adoption gap (illustrative model). Consumer wallet readiness runs well ahead of business pass adoption — a directional pattern, not a measured statistic. (Original PushNotice illustrative model.)
Trends shaping 2026
Passes overtake payments as the growth story. Tap-to-pay is mature; the fast growth is now in loyalty, tickets, and memberships living in the wallet. Identity enters the wallet. State IDs, driver's licenses, and digital keys are rolling out region by region, raising both the wallet's value and its privacy stakes. Post-cookie shift favors owned channels. As third-party tracking declines, the consented first-party data a wallet program generates rises in value. The SMB opening. Enterprise brands adopted wallet passes years ago; the tools that let a small team launch without engineers are bringing the channel to everyone else.
Predictions
Looking ahead, four movements seem likely: new loyalty and membership programs will start wallet-native rather than plastic; wallet notifications will become an expected baseline channel alongside email and SMS; identity credentials will normalize in the wallet over the next several years, market by market; and the businesses that build owned wallet data early will hold a durable advantage as tracking-based marketing keeps eroding.
Verifiable figures in this section are drawn from named public sources (Juniper Research, Forbes Advisor, Statista, and Bain & Company via Harvard Business Review), cited in Sources and dated at point of use. Illustrative models are clearly labeled as such and are directional reasoning aids, not measured findings or PushNotice proprietary data. Where a precise number would mislead if generalized, we describe the mechanism instead. PushNotice did not conduct an original survey for this section; when we publish primary research, it will be labeled explicitly and its method described.
- Verifiable: billions of wallet users, majority regular use in many markets, ~90% in a loyalty program.
- The 2026 story is an adoption gap — consumers are wallet-ready; many businesses haven't met them there.
- Illustrative models here are labeled and directional, never presented as measured research.
Industry examples
Any business with repeat customers benefits from a mobile wallet program, but the pass type and mechanic differ by industry. Retail and cafés lean on loyalty and coupons; gyms and clubs on membership and access; events and travel on tickets and boarding passes; healthcare and hospitality on identity and reminders. Match the pass and notification to how the business actually operates.
Retail & e-commerce
Retailers use loyalty and store cards with tiered rewards and member pricing, issued at checkout online and in-store, integrated with the POS or Shopify. Coupons surfaced by location pull nearby customers in. The card carries the tier and unlocks member prices at the register.
Restaurants & cafés
Cafés run stamp-based loyalty ("buy 9, get 1 free") on a wallet card saved from a counter QR. The live stamp count and a reward-near notification drive the next visit; restaurants add dining-club memberships and event notifications.
Fitness & gyms
Gyms issue membership cards that carry the plan and renewal date and are scanned for entry, with auto-renewal reminders recovering the involuntary churn that dominates gym lapses. Studios add class-pack loyalty passes.
Events & entertainment
Venues issue event tickets that surface at the venue by location and time, update if a time or gate changes, and scan for entry — replacing printed tickets and the email scramble. Season passes carry across the calendar.
Travel & hospitality
Airlines and hotels use boarding passes, room keys, and loyalty status in the wallet — real-time gate updates, tap-to-enter rooms, and elite-tier recognition, all surfacing at the right moment of the trip.
Healthcare
Clinics and wellness memberships use membership and identity passes with appointment reminders, carrying plan and renewal while keeping sensitive data minimal — privacy and data handling are paramount here.
| Industry | Primary pass type | Key mechanic | Notification focus |
|---|---|---|---|
| Retail / e-commerce | Loyalty / store card | Tiers + member pricing | Offer near store; reward earned |
| Restaurants / cafés | Loyalty (stamps) | Buy-X-get-1 | Reward near; new stamp |
| Fitness / gyms | Membership | Access + renewal | Renewal reminder; class credit |
| Events / entertainment | Event ticket | Entry + season pass | Venue arrival; time/gate change |
| Travel / hospitality | Boarding pass / key | Real-time updates | Gate change; check-in |
| Healthcare | Membership / identity | Plan + adherence | Appointment; renewal |
| Beauty / services | Loyalty / coupon | Rebooking | Rebook nudge; expiring offer |
| Nonprofits / associations | Membership | Annual renewal | Renewal; event access |
- Every repeat-customer business benefits, but the pass type and mechanic differ by vertical.
- Loyalty and coupons suit retail and food; membership suits gyms and clubs; tickets suit events and travel.
- Match the pass and notification to how the business actually operates, not a generic template.
Future, resources & reference
Where mobile wallets are heading, a launch checklist to act on this guide, the free tools that turn it into working artifacts, and the reference apparatus — 60 FAQs, a glossary, methodology, and sources — that make it citable.
The future of mobile wallet marketing
The future is wallet-native, credential-rich, and privacy-forward. New loyalty and membership programs will start in the wallet rather than on plastic; identity credentials — IDs, keys, tickets — will normalize; wallet notifications will join email and SMS as an expected baseline channel; and owned wallet data will grow more valuable as tracking-based marketing keeps declining. The wallet becomes the default place customers keep the businesses they belong to.
Four movements define the next several years. Wallet-native by default: businesses will start programs digital, treating plastic as the exception. The credential wallet matures: government IDs, car and hotel keys, and event and transit passes make the wallet the container for everything you'd otherwise carry — raising its everyday use and its value as a channel. Notifications become baseline: a free, in-context lock-screen channel will be a standard part of the marketing stack, not an advanced tactic. Owned data ascendant: as third-party cookies vanish, the consented first-party data a wallet program generates becomes a primary marketing asset that respects privacy by design.
The constant beneath the trends: the wallet is where customers keep what matters to them. The technology keeps making that container more live, more useful, and more measurable — but the opportunity is unchanged. Meet customers on the screen they already carry, give them a reason to save your card, and reserve the lock screen for moments they'll thank you for.
The mobile wallet is already on every customer's phone. The businesses that win treat it not as a way to get paid, but as the most direct channel they own.
- Wallet-native programs, richer credentials, baseline notifications, and owned data define the future.
- Identity and keys make the wallet the everyday container — raising its value as a channel.
- The opportunity is unchanged: meet customers on the screen they already carry.
Implementation checklist
Before launch, confirm the goal and pass type are set, both Apple and Google passes render on real devices, Add-to-Wallet buttons are live at every high-intent moment, notifications are reserved for genuine value, staff can scan and verify, and analytics are tracking. Treat every unchecked item as a launch blocker.
| Area | Checklist item | Ready? |
|---|---|---|
| Goal | Objective & pass type chosen (loyalty, coupon, membership…) | ☐ |
| Both wallets | Apple + Google passes issue from one record | ☐ |
| Devices | Pass tested on a real iPhone and a real Android | ☐ |
| Design | Branding, payload, and a scannable code with quiet zone | ☐ |
| Distribution | Add-to-Wallet at counter QR, POS, signup, checkout, email/SMS, site | ☐ |
| Records | POS / CRM sync verified; IDs unique | ☐ |
| Notifications | Only high-value triggers enabled; cadence set | ☐ |
| Location | Relevant locations added where useful | ☐ |
| Redemption | Staff trained to scan & verify live status; scanner tested | ☐ |
| Security | Server-side verification; signing verified | ☐ |
| Analytics | Saves, activation, redemption, retention dashboards live | ☐ |
| Privacy | Data minimized; privacy note on pass back & site | ☐ |
Do a full dress rehearsal: save your own pass on both an iPhone and an Android, walk through a redemption at the counter, trigger a notification, and confirm each event shows in analytics. Ten minutes of rehearsal prevents launch-day surprises in front of customers.
- Treat every unchecked item as a launch blocker.
- Test both wallet passes on real devices and rehearse a redemption before go-live.
- Confirm distribution, notifications, scanning, and analytics all work end to end.
Downloadable resources and templates
These free planners, calculators, and templates turn this guide's frameworks into working tools your team can use and share. Each stands on its own — the kind of resource other sites link to and teams keep open while building a wallet program.
Why it matters: a framework becomes durable when it becomes an artifact. A calculator that models wallet ROI, or a matrix that compares platforms, gets used, cited, and linked far more than the same idea buried in prose. The tools below cover the maths and process; use them alongside the frameworks in Part VII.
To save any section of this guide as a PDF, use your browser's Print → Save as PDF. Branded, editable versions of these planners and templates are maintained on the PushNotice wallet marketing hub.
- Planners and calculators make the pricing and process reusable.
- Matrices and checklists give each program a ready starting point.
- Useful, linkable tools compound topical authority and backlinks.
Frequently asked questions
60 answers to the real questions people and AI systems ask about mobile wallet apps — grouped by basics, the three wallets, payments and security, passes, marketing and notifications, software, and privacy and comparisons. Each answer stands on its own.
Basics
What is a mobile wallet app?
A mobile wallet app is a smartphone application that stores your payment cards, passes, tickets, and identity credentials digitally, so you can pay, check in, and prove who you are from your phone. The leading apps — Apple Wallet, Google Wallet, and Samsung Wallet — come pre-installed. Beyond tap-to-pay, they hold business-issued passes like loyalty cards and coupons that update remotely.
How does a mobile wallet app work?
It stores credentials securely on the phone and presents them by NFC (tap), QR code or barcode (scan), or in-app checkout. Payments use tokenization, replacing your real card number with a device-specific token. Business passes are signed files the issuer can update over the air, which is what lets a balance or gate number refresh automatically.
What is the difference between a mobile wallet and a digital wallet?
"Digital wallet" is the umbrella term for any software that stores payment or credential data, including cloud wallets like PayPal. A "mobile wallet" is the phone-based member of that family that can also pay in person by tapping. Every mobile wallet is a digital wallet, but not every digital wallet is mobile.
Are mobile wallet apps free?
Yes. Apple Wallet, Google Wallet, and Samsung Wallet are free and pre-installed on their respective phones. There is no fee to add cards or passes, and tapping to pay costs the consumer nothing beyond the normal price of what they are buying.
Do I need to download a mobile wallet app?
No. The main mobile wallets ship built into the phone — Apple Wallet on iPhone, Google Wallet on Android, Samsung Wallet on Galaxy — and cannot usually be removed. Saving a business pass into the wallet also takes just one tap, with no separate app to install.
What can I store in a mobile wallet?
Payment cards, transit cards, loyalty and membership cards, coupons, gift cards, event tickets, boarding passes, store cards, and — increasingly — identity documents, car and hotel keys, and corporate badges. In short, most of what you would otherwise carry in a physical wallet, in live digital form.
Is a mobile wallet safe?
Generally safer than a physical wallet. Payments are tokenized so your real card number is never shared, each transaction needs your face or fingerprint, and credentials sit in a hardware-isolated secure area. A lost phone is far less risky than a lost card because nothing works without the owner's biometrics.
Do mobile wallets work without internet?
Mostly yes. Tap-to-pay and displaying a saved pass work offline, since the credential is stored on the phone. Updates to a pass — a new balance, a gate change — and notifications sync when the phone is back online, but you can always present what is already saved.
What is a wallet pass?
A wallet pass is a digital card stored in a mobile wallet that a business can update remotely and use to send lock-screen notifications. Loyalty cards, coupons, memberships, gift cards, event tickets, and boarding passes are all wallet passes, built on Apple PassKit or the Google Wallet API.
What is the difference between a mobile wallet and a payment app?
A payment app like Venmo or Cash App does one thing — move money — while a mobile wallet is a broader container that includes payment but also holds passes, tickets, and IDs. Payment apps reach only their own users; a wallet pass reaches every customer through the wallet already on their phone.
The three wallets
What is Apple Wallet?
Apple Wallet is the built-in wallet app on every iPhone. It runs Apple Pay for tap-to-pay and online checkout, and it stores passes built on Apple's PassKit framework — boarding passes, tickets, loyalty and store cards, coupons, transit, keys, and, in supported regions, IDs.
What is Google Wallet?
Google Wallet is the built-in wallet app on Android. It handles contactless payments and stores passes created through the Google Wallet API using a class-and-object model, covering loyalty, gift, offer, generic, transit, event, and boarding passes, plus digital IDs where available.
What is Samsung Wallet?
Samsung Wallet is Samsung's wallet app for Galaxy phones, combining payments, passes, tickets, keys, and identity. Its historical edge was MST, which let older Galaxy phones pay at magnetic-stripe terminals without NFC. Most businesses reach Samsung users through Google Wallet passes.
What is the difference between Apple Wallet and Google Wallet?
They do the same core jobs on different platforms: Apple Wallet on iPhone via PassKit, Google Wallet on Android via the Wallet API. Apple issues signed pass bundles; Google uses a class (template) plus object (individual) model. For a business, the rule is to support both so no customer is excluded.
Which is the best mobile wallet app?
For a consumer, the best wallet is simply the one built into their phone — Apple Wallet on iPhone, Google Wallet on Android, Samsung Wallet on Galaxy. They are closely matched on features. For a business, the "best" choice is to support Apple and Google Wallet together rather than pick one.
Can I use Apple Wallet on Android?
No. Apple Wallet is exclusive to iPhone and iOS. Android users have Google Wallet (and Samsung Wallet on Galaxy devices). This is exactly why a business program must issue both an Apple and a Google version of each pass — one platform never covers everyone.
Do I need both Apple and Google Wallet for my business?
Yes. Issuing Apple-only excludes every Android customer, and Google-only excludes every iPhone customer. Good wallet software generates both versions from a single customer record and shows the correct "Add" button based on the customer's device, doubling your reach at no extra effort.
What is the difference between Apple Pay and Apple Wallet?
Apple Wallet is the app that holds your cards and passes; Apple Pay is the payment service that uses the cards inside it to tap-to-pay and check out. Apple Pay is a feature of Apple Wallet, not a separate app.
Is Google Wallet the same as Google Pay?
They are closely related. Google consolidated its payment and wallet efforts, with Google Wallet as the app that stores cards, passes, and credentials, while Google Pay branding persists for certain payment features and in some regions. For most users on Android, Google Wallet is the wallet they use.
Payments & security
How does tap to pay work?
You hold your phone near a contactless terminal, which communicates over NFC. The wallet transmits a payment token — not your real card number — along with a one-time cryptogram, and you approve with your face, fingerprint, or passcode. The whole exchange takes a second and never exposes your actual card.
What is NFC?
NFC, or near-field communication, is a short-range wireless technology that lets two devices exchange data over a few centimeters. In a mobile wallet it powers tap-to-pay and tap-to-verify — the phone "taps" a terminal or reader to transmit a payment token or a pass.
What is tokenization?
Tokenization replaces your real card number with a device-specific stand-in number (a token) that is stored on the phone and sent at checkout. Because the merchant only ever sees the token, a data breach at the store cannot expose your actual card number. It is the core of mobile wallet payment security.
Is tapping to pay safer than a physical card?
Generally yes. Tapping uses a token instead of your real number, requires your biometrics to authorize, and adds a one-time cryptogram that cannot be replayed. A swiped or inserted card exposes more data, and a lost phone is safer than a lost card because payments need the owner's face or fingerprint.
What happens if I lose my phone?
Your credentials are protected by the device's biometrics, so a finder cannot pay or use your passes. You can also remotely lock or wipe the phone and suspend its wallet, and re-provision cards and passes to a replacement device. Because the data is a record, nothing is permanently lost.
Can a mobile wallet be hacked?
No system is perfectly immune, but mobile wallets are hardened: credentials live in an isolated secure element, payments are tokenized, and access needs biometrics. The most realistic risks are phishing and social engineering rather than breaking the wallet itself — which is why you should never share codes or approve unexpected prompts.
Do merchants see my card number when I use a mobile wallet?
No. The merchant receives a payment token, not your real 16-digit card number. Your actual number is never stored on the phone or transmitted at the terminal, which is a key reason mobile wallet payments are more private and secure than handing over a physical card.
Do mobile wallet payments cost more?
No. For the consumer, tapping to pay costs exactly the same as using the card directly. For merchants, wallet payments run on the same card networks at comparable rates; there is no extra charge to the shopper for choosing to tap their phone.
Can I use a mobile wallet everywhere?
Almost everywhere that accepts contactless payments, which is now the vast majority of terminals. A small number of older or specialized terminals may still require a physical card, and some regions lag in contactless rollout, but acceptance is broad and growing.
Passes
What types of wallet passes are there?
The main types are loyalty cards, membership cards, coupons and offers, gift cards, event tickets, boarding passes, store cards, and identity cards, plus transit passes that blend payment and ticketing. Each carries different data but shares one-tap saving, live updates, a scannable code, and notifications.
What is a loyalty card in a wallet?
A wallet loyalty card tracks accumulating rewards — points, stamps, or visits — and updates live as the customer earns. It shows the current balance, notifies when a reward is near or earned, and keeps the goal visible between visits, which drives repeat business.
What is a digital coupon?
A digital coupon is a wallet pass carrying a discount or offer with an expiry. Saved to the wallet, it can surface by location and time, greys out or disappears when redeemed or expired, and gives customers the most direct wallet path from an offer to a purchase.
What is a gift card in a wallet?
A wallet gift card stores a prepaid balance that decrements as it is spent. Unlike plastic, it cannot be lost, shows the live remaining balance, can be reloaded, and can notify when the balance runs low — a nudge to top up and return.
What is a boarding pass in a wallet?
A wallet boarding pass carries your flight, seat, gate, and boarding time on a card that updates in real time — a gate change refreshes it and can notify you — and surfaces automatically on the lock screen at the airport, ready to scan.
What is an event ticket in a wallet?
A wallet event ticket carries the event, seat, and entry code, surfaces at the venue by location and as the event approaches by time, updates if details change, and scans for entry. It replaces printed tickets and the scramble to find the right confirmation email.
What is a store card?
A store card is a wallet pass representing a retailer's account or prepaid balance, often blending a loyalty balance, member pricing, and an account or payment code in one pass. It is the retail all-rounder — identity, rewards, and sometimes value together.
Can I put my ID in a mobile wallet?
Increasingly, yes. Apple and Google Wallet support state IDs and driver's licenses in a growing list of regions, along with corporate badges, and car and hotel keys. Availability depends on your location and issuer, and these credentials carry the highest security and privacy protections.
Do wallet passes update automatically?
Yes. A wallet pass is a live record, not a static image. When the issuing business changes it — a new balance, a tier, a gate, an offer — it pushes the change and the wallet re-renders the saved pass on the customer's phone, optionally showing a notification, with no action from the customer.
Marketing & notifications
What is mobile wallet marketing?
Mobile wallet marketing is the practice of using wallet passes — loyalty cards, coupons, memberships, and more — as an owned marketing and retention channel. A business issues a pass, distributes a one-tap Add-to-Wallet link, and uses free lock-screen and location notifications to bring customers back, all without a mobile app.
How do businesses use mobile wallets?
Businesses issue wallet passes customers save in one tap, then update those passes and send free lock-screen notifications for rewards, offers, and reminders. It gives them a durable presence on the customer's phone, a free channel, self-updating cards, and first-party data — without building an app.
What is a wallet notification?
A wallet notification is a lock-screen message a business pushes to a saved pass — free, unfiltered, and highly visible. It fires when the business updates the pass (a new stamp, an expiring offer, a gate change) and appears without the customer opening any app.
Are wallet notifications free?
Yes. Because a wallet notification is a system-level pass update rather than a message sent through a carrier or inbox, there is no per-message fee and no spam folder. The cost is structural zero — a core advantage over SMS, which charges per message.
How do location-based wallet notifications work?
A pass can carry one or more locations. When the customer is nearby, the phone surfaces the pass on the lock screen and can show a short message. Proximity is handled by the operating system in a privacy-preserving way — the business registers a location but never receives a live feed of where customers are.
Can businesses send push notifications without an app?
Yes — that is a defining advantage of wallet marketing. Once a customer saves a pass, the business can send lock-screen notifications by updating the pass, with no app to build, no app-store approval, and no separate opt-in beyond the customer saving the card.
How is wallet marketing different from email?
Email is rich and far-reaching but easily buried or filtered; wallet marketing is a persistent card on the phone that surfaces in context and notifies for free. Email carries depth; the wallet carries timely, in-context nudges. Many programs use email to invite the wallet save, then run day-to-day loyalty through the pass.
How is wallet marketing different from SMS?
SMS is immediate and two-way but costs per message and fatigues fast; wallet notifications are free, unfiltered, and tied to a living card. SMS suits urgent, personal messages; the wallet suits ongoing loyalty and offers. They complement each other rather than compete.
How do I add customers to my wallet program?
Customers tap an "Add to Apple Wallet" or "Add to Google Wallet" button, reached from a counter QR code, the point of sale, a signup form, checkout, an email or SMS link, or your website. The save takes seconds and needs no app; place the button at every high-intent moment.
Does wallet marketing require a mobile app?
No. That is the point. Wallet marketing runs entirely through the wallet already built into the customer's phone. There is nothing to download, no install wall, and no app to maintain — which is why adoption is far higher than for custom apps.
Software & building
How do I create a wallet pass?
Use wallet software (or build on Apple PassKit and the Google Wallet API directly). You design the pass — branding, the payload like a balance or offer, and a scannable code — then generate a one-tap Add-to-Wallet link. A platform lets a non-technical team create and update passes without engineers.
What is wallet marketing software?
Wallet marketing software creates, updates, and manages Apple and Google Wallet passes and sends notifications. It handles pass design, distribution, location targeting, analytics, and integrations with your POS, CRM, and e-commerce, replacing the need to build directly on the platform APIs.
Do I need developers to build wallet passes?
Not usually. Wallet-pass platforms let a small team design, issue, and update passes without engineers. Building directly on PassKit and the Google Wallet API gives full control but requires development and ongoing maintenance — best for teams with engineers and unique needs.
How much does mobile wallet marketing cost?
Most wallet software is a flat monthly subscription that does not scale per pass or per message — unlike plastic (per card) or SMS (per message). The main variable cost is delivering the rewards or offers themselves, sized against the repeat revenue the program drives.
Can wallet passes integrate with Shopify or my POS?
Yes. Good wallet software issues passes at Shopify checkout and syncs with retail POS and CRM systems, so passes are created and rewards awarded as part of normal transactions and customer records stay consistent. Scan-based programs can also launch without deep integration.
How long does it take to launch a wallet program?
With wallet software, a basic program can be live in an afternoon: choose the pass type, design the card, generate a one-tap Add-to-Wallet link, and start distributing it. Deeper POS integration, automation, and segmentation take longer but are not required to launch.
Privacy, data & comparisons
Do mobile wallets track my location?
Location relevance is handled by the phone's operating system, not by the businesses whose passes you hold. A pass can register a location so it surfaces when you are nearby, but the business never receives a live feed of your movements. You control location permissions in your phone settings.
What data do businesses get from wallet passes?
Businesses see relationship data — that a customer saved a pass, earned a reward, or redeemed an offer — plus any profile fields the customer consented to share. They do not get a live location feed or your card number. It is consented, first-party data about the relationship, not surveillance data.
Is wallet data first-party data?
Yes. Because customers choose to save the pass and use it directly with the business, the resulting data is consented, owned, first-party data. As third-party cookies decline, this owned wallet data becomes increasingly valuable for personalization, win-back, and product decisions.
Is a mobile wallet the same as a banking app?
No. A banking app, from your bank, manages your account — balances, transfers, bill pay. A mobile wallet, from the phone maker, holds tokenized copies of cards to spend plus non-payment passes. They connect, but the wallet does not hold your balance or run transfers.
Do I still need email and SMS if I use wallet marketing?
Yes — they are complementary. Wallet notifications handle timely, in-context nudges for free; email carries depth and reach; SMS adds urgent, two-way messaging. Many programs use email or SMS to drive the wallet save, then run ongoing loyalty through the pass.
What businesses benefit most from mobile wallets?
Any business with repeat customers: retail, restaurants and cafés, gyms and studios, events and venues, travel and hospitality, salons and services, and associations. The more a business depends on customers coming back, the more a retention-focused wallet channel pays off.
What is the future of mobile wallet apps?
The future is wallet-native and credential-rich: new loyalty and membership programs start in the wallet, identity documents and keys normalize there, notifications become a baseline marketing channel, and owned wallet data grows more valuable as tracking-based marketing declines. The wallet becomes the default container for everything you carry.
Glossary
The core mobile wallet terms in one place — from the technologies (NFC, tokenization, PassKit) to the pass types and marketing concepts — each defined in a sentence so this section can be quoted on its own.
- Mobile wallet app
- A smartphone app that stores payment cards, passes, tickets, and IDs digitally so you can pay, check in, and prove identity from your phone.
- Digital wallet
- The umbrella category of software that stores payment or credential data; a mobile wallet is the phone-based, tap-capable member of it.
- Apple Wallet
- The pre-installed wallet on iPhone, running Apple Pay and holding PassKit passes.
- Google Wallet
- The pre-installed wallet on Android, running payments and holding passes created through the Google Wallet API.
- Samsung Wallet
- Samsung's Galaxy-native wallet, which historically supported MST for magnetic-stripe terminals.
- Wallet pass
- A digital card in a mobile wallet that a business can update remotely and use to send lock-screen notifications.
- PassKit
- Apple's framework for creating, signing, distributing, and updating Apple Wallet passes.
- Google Wallet API
- Google's interface for creating and updating Google Wallet passes via a class (template) and object (individual) model.
- NFC
- Near-field communication, the short-range wireless link behind tap-to-pay and tap-to-verify.
- Tokenization
- Replacing a real card number with a device-specific token so the merchant never sees the actual number.
- Secure element
- A hardware chip that isolates payment credentials from the rest of the phone.
- MST
- Magnetic secure transmission, Samsung's method of emulating a card swipe at magnetic-stripe terminals.
- QR code / barcode
- Scannable codes on a pass used to identify a customer, redeem an offer, or grant access.
- Wallet marketing
- Using wallet passes as an owned marketing and retention channel with free lock-screen notifications.
- Wallet notification
- A free lock-screen message pushed to a saved pass by updating it server-side.
- Location relevance
- A pass surfacing on the lock screen when the customer is near a location it carries, handled privately by the OS.
- Loyalty card
- A pass that tracks accumulating rewards — points, stamps, or visits.
- Membership card
- A pass that proves belonging and status, carrying a member ID, tier, and renewal date.
- Coupon / offer
- A pass carrying a discount with an expiry that can surface by location and time.
- Gift card
- A pass storing a prepaid balance that decrements as it is spent.
- Boarding pass
- A travel pass carrying flight, seat, and gate that updates in real time.
- Event ticket
- A pass carrying an event, seat, and entry code that surfaces at the venue.
- Store card
- A retail pass blending account, loyalty balance, and sometimes payment.
- First-party data
- Consented data a business collects directly from its own customers; owned and independent of third-party cookies.
- Add to Wallet
- The one-tap button that saves a pass to Apple Wallet or Google Wallet.
Continue learning
These PushNotice guides go deeper on the topics above. This page is the pillar reference on mobile wallet apps; the guides below drill into individual wallets, pass types, and channel comparisons.
Read next: What Is Wallet Marketing? (the marketing pillar), Customer Loyalty Cards, Digital Membership Cards, Apple Wallet Marketing, Google Wallet Marketing, Wallet Marketing vs Email Marketing, and Wallet Marketing vs SMS Marketing.
About this reference
This guide is maintained by the team at PushNotice, which builds Apple Wallet and Google Wallet marketing software. It reflects direct experience designing wallet passes, engineering pass-update and notification logic, and running retention programs across retail, hospitality, fitness, and events.
Why this guide exists. Most "mobile wallet app" articles stop at a definition or focus only on payments. This reference exists to give consumers, operators, marketers, agencies, and researchers an accurate, citable account of what mobile wallets are, how the three platforms work, every pass type they hold, how businesses market through them, and the security and privacy realities — without the sales gloss.
Editorial and research policy. We state only verifiable figures and attribute them to primary or authoritative sources; where a number would mislead if generalized, we explain the mechanism instead. Adoption figures are attributed to Juniper Research, Forbes Advisor, and Statista (via Capital One Shopping); retention economics to Bain & Company (via Harvard Business Review); and platform capabilities to Apple's and Google's own developer documentation. Illustrative models are labeled as such and never presented as measured findings. We invent no research results, benchmarks, or case studies.
Content maintenance policy. This page is reviewed at least quarterly and whenever platform policies or headline figures change. The canonical URL always holds the current version. Corrections are welcome via the PushNotice contact page.
Content principles. Five rules govern every edit: (1) accuracy before ranking — no claim ships without a traceable source or an explained mechanism; (2) information gain — each section adds something competitors omit; (3) vendor-neutrality — the guidance holds whether or not you use PushNotice; (4) clarity — plain language over jargon; and (5) transparency — assumptions, dates, and limitations are stated, not hidden.
Transparency statement. PushNotice sells wallet-marketing software, so this guide is not disinterested — but it is written to be useful even if you never become a customer. Product mentions are confined to clearly marked calls to action, the "Where PushNotice fits" note, and the conclusion; the educational content stands on its own. Where we make a recommendation (support both wallets, reserve notifications for value), it is argued from the evidence in the guide, not from what we sell.
Research methodology
Every claim is sourced in one of three ways. Platform mechanics (how Apple, Google, and Samsung wallets store, present, and update credentials) are verified against the platforms' own developer documentation. Economic claims (retention economics) are attributed to named primary research — Bain & Company via Harvard Business Review. Adoption figures are drawn from published statistical compilations (Juniper Research, Forbes Advisor, Statista via Capital One Shopping) and dated at the point of use. Where a number would mislead if generalized, we describe the mechanism instead. Illustrative models are explicitly labeled and are reasoning aids, not measured results.
Reviewer qualifications
This reference is reviewed by the PushNotice Editorial Team, which builds and operates Apple Wallet and Google Wallet marketing software day to day: designing passes, engineering update and notification logic, and running live retention programs for retailers, restaurants, gyms, venues, and service businesses. That operational experience — not secondary summarization — is the basis for the practical guidance here.
About the author & reviewer
Sajid Ali is the co-founder of PushNotice, where he builds Apple Wallet and Google Wallet marketing software for retailers, restaurants, gyms, venues, e-commerce brands, and agencies. This guide was reviewed by the PushNotice Editorial Team for accuracy and clarity.
Author — Sajid Ali, Co-founder, PushNotice. Sajid works directly on wallet pass design, notification and update logic, and the retention programs that pair wallet passes with email and SMS — the same hands-on experience this guide is drawn from.
Reviewed by — the PushNotice Editorial Team. The Editorial Team fact-checks each reference against primary sources, verifies platform capabilities against Apple and Google documentation, and confirms that no statistic is presented without an attributable source and no illustrative model is presented as research. This reference is part of the PushNotice Reference Library, a series of vendor-neutral guides written to be accurate and citable first, and useful to practitioners second.
Version history
| Version | Date | Change |
|---|---|---|
| 1.0 | 2026-08-01 | Initial definitive reference published: foundations and how wallets work, the evolution, Apple/Google/Samsung Wallet and a platform comparison, mobile vs digital vs banking vs payment apps, all wallet pass types, why businesses use wallets, mobile wallet marketing, notifications and location/time targeting, retention and loyalty, benefits, adding customers, the workflow, a software buyer's guide, how push works, security and privacy, nine original frameworks and a knowledge graph, the State of Mobile Wallet Marketing 2026, industry playbooks, the future, an implementation checklist, downloadable resources, 60 FAQs, a glossary, and seven JSON-LD schema blocks. |
Cite this guide
If you reference this guide in an article, paper, or AI answer, please link to the canonical URL.
- APA: Sajid Ali. (2026). What Is a Mobile Wallet App? The Definitive Guide. PushNotice. https://pushnotice.io/blog/what-is-a-mobile-wallet-app
- MLA: Sajid Ali. "What Is a Mobile Wallet App? The Definitive Guide." PushNotice, 2026, pushnotice.io/blog/what-is-a-mobile-wallet-app.
Sources and further reading
- Apple Developer — Wallet & PassKit documentation: pass types, remote updates, and relevance. https://developer.apple.com/wallet/
- Google for Developers — Google Wallet passes: class/object model, pass types, updates, and issuance. https://developers.google.com/wallet
- Samsung — Samsung Wallet: features, MST history, and supported credentials. https://www.samsung.com/us/support/owners/app/samsung-wallet
- Capital One Shopping Research — Digital Wallet Statistics: global digital-wallet user data (compiling Juniper Research and others). https://capitaloneshopping.com/research/digital-wallet-statistics/
- Forbes Advisor — Digital Wallet / Mobile Payment statistics: U.S. consumer adoption of digital wallets. https://www.forbes.com/advisor/
- Capital One Shopping Research — Loyalty Program Statistics: consumer program-membership data (compiling Statista and U.S. Bureau of Labor Statistics). https://capitaloneshopping.com/research/loyalty-program-statistics/
- Harvard Business Review — The Value of Keeping the Right Customers (Amy Gallo, 2014): retention-vs-acquisition and retention-to-profit figures, attributed to Bain & Company research by Fred Reichheld. https://hbr.org/2014/10/the-value-of-keeping-the-right-customers
Figures were accurate as of their sources' publication dates and may change; verify against the primary sources before republishing derivative numbers. Illustrative models in this guide are labeled as such and are not measured research findings.