Apple changed the name in 2015. The technology underneath has not changed since 2012. Eleven years later, "passbook apple wallet" still pulls roughly 14,800 monthly U.S. searches because the old name is baked into vendor contracts, training docs, and inherited code.
What is passbook in Apple Wallet?
Passbook in Apple Wallet is the original name for Apple's digital pass container, launched in iOS 6 in September 2012. Apple renamed Passbook to Apple Wallet in iOS 9 on September 16, 2015 after adding payment-card support. The .pkpass file format and PassKit framework did not change, so passes built for Passbook still install on a modern iPhone today.
Key facts that have stayed constant since 2012:
- Same file format. Passes are .pkpass files (signed ZIP archives) issued through the Apple PassKit Programming Guide.
- Same five core pass types. Boarding pass, event ticket, store card, coupon, and generic.
- Same developer requirement. Apple Developer Program membership at $99 per year (Apple Developer site).
- Same web service push. Lock-screen updates flow through APNs via the PassKit Web Service.
- Same backward compatibility. A pass.json written for iOS 6 still validates against iOS 18.
Why this guide exists
I run Regulr AI, a wallet-pass marketing platform for local businesses. Every week a new operator emails me asking some version of "is Apple Passbook still a thing" or "do I need a Passbook account to send loyalty cards." The short answer is no, the longer answer is what this guide is. I wrote it because the existing top-ranked results on this topic are either Apple support pages from 2015 that read like museum exhibits, or wallet-platform blog posts that pretend Passbook never existed. Neither one helps a real operator who inherited a Passbook reference in a vendor contract.
The Passbook to Wallet timeline
September 19, 2012, iOS 6. Apple launches Passbook alongside the iPhone 5. Launch partners include American Airlines, United, Delta, Starbucks, Target, Walgreens, MLB, Ticketmaster, Fandango, and Eventbrite. The app supports five pass types out of the gate: boarding passes, event tickets, store cards, coupons, and a generic catch-all. Apple publishes the PassKit framework and the .pkpass file specification.
September 17, 2014, iOS 8. Passbook gets visual refinements and tighter Touch ID integration. Apple Pay launches a month later (October 20, 2014) as a separate product, but the credit-card storage lives inside Passbook from day one. This is the seed of the future rebrand.
September 16, 2015, iOS 9. Apple renames Passbook to "Wallet." MacRumors and 9to5Mac both covered the change at WWDC 2015 (June 8, 2015) when Apple previewed iOS 9. The reasoning Apple gave was simple: "Passbook" no longer described what the app did, because store credit cards, debit cards, and loyalty cards now sat next to boarding passes inside it. The .pkpass format and PassKit framework were left untouched.
2016 to 2019. Wallet adds NFC tap-to-add for passes (2019), express transit support, student ID cards, and car keys. None of these break the original Passbook pass spec.
2020 to 2024. Wallet adds digital driver's licenses in select states, Apple Cash, and tighter Maps integration for geofenced relevance. Apple's Q4 2024 earnings call referenced more than 600 million active Apple Pay users globally, which is the closest public proxy for active Wallet users since the two now share an install base.
2025 to 2026. Wallet remains the dominant U.S. mobile pass container. Google Wallet, the Android equivalent, is the second pillar. Together they cover essentially every smartphone owner in North America.
What changed at the rename, and what did not
What changed:
- The app name on the home screen went from "Passbook" to "Wallet."
- The app icon was redesigned.
- Payment cards became a first-class citizen alongside passes.
What did not change:
- The .pkpass file format, including its signed-ZIP structure, pass.json schema, and asset folder layout.
- The PassKit framework that developers use to generate passes.
- The web service endpoints used for push updates and registration.
- The pass type ID and certificate model issued through the Apple Developer Program.
- The five original pass types: boarding pass, event ticket, store card, coupon, and generic.
In practical terms, a sample app written against PassKit in 2014 still compiles and serves valid passes in 2026. I have personally tested this with a 2015-era Ruby gem on iOS 17 and the pass installed without complaint.
Why people still search "Apple Passbook" in 2026
Four reasons keep this keyword alive eleven years after the rename.
Aged content. A huge portion of the loyalty, ticketing, and event-tech blog content indexed by Google was written between 2012 and 2015 when Passbook was the only correct term. Those articles still pull traffic and still use the old name.
Internal training and contracts. Vendor contracts, retail point-of-sale documentation, and internal training decks at large chains often still reference "Passbook integration." When a new employee inherits the doc, they search the term they see.
Inherited code. A non-trivial amount of Ruby, PHP, and Node code on GitHub has variable names like passbook_url or class names like PassbookService. Engineers debugging that code search the term in the file.
SEO inertia. Google's training data still surfaces Passbook in autocomplete suggestions for queries like "what is Apple," and that compounds the search volume on the original term.
What modern Apple Wallet (formerly Passbook) does for businesses in 2026
Same five original pass types, plus payment cards and a few new categories:
- Loyalty cards. Coffee shops, restaurants, gyms, salons. The original Starbucks use case, now the most common.
- Event tickets. Concert, sports, theater, and conference tickets. Often delivered by Ticketmaster, AXS, SeatGeek, Eventbrite, Humanitix.
- Boarding passes. Every major U.S. and most international airlines.
- Membership cards. Gym memberships, museum memberships, club cards.
- Coupons. One-time-use offers and ongoing promotions.
- Generic passes. Anything that does not fit the other categories. This is what Regulr AI uses for most local-business loyalty programs.
- Apple Pay payment cards. Credit, debit, and prepaid cards.
For a local business, the relevant categories are usually loyalty cards, store cards, and generic passes. The technical mechanism is identical to what Passbook supported in 2012.
The technical implementation has not changed
For developers and operators, the build is recognizable to anyone who shipped a Passbook pass a decade ago.
- Pass files are still .pkpass. A signed ZIP archive containing pass.json, manifest.json, signature, and image assets.
- PassKit framework is still the API. Apple Developer Program membership is required ($99 per year as of 2026).
- Pass type ID and certificate. Each business needs one pass type ID, signed with an Apple-issued certificate.
- Web service URL. Optional but standard for real-time updates and push notifications via APNs.
- Geofencing. Up to 10 relevant locations per pass, same as 2012.
- NFC. Optional, requires Apple's NFC entitlement, used mostly for transit and access control.
A pass.json file written for iOS 6 still validates against the iOS 18 PassKit parser. I have not found a single breaking change to the schema in eleven years.
Passbook era versus Wallet era for businesses
The mechanism is identical. The improvements are around the edges.
- Loyalty card distribution. Then and now, the standard delivery is a .pkpass file linked from a webpage, an SMS, an email, or a QR code. Same flow.
- Push notifications. Then and now, push goes through Apple's APNs service via the PassKit web service. The wallet push appears on the lock screen as a banner. Same mechanism.
- Geofencing. Then and now, up to 10 latitude-longitude relevance points trigger the pass to surface on the lock screen when a customer is nearby.
- Real-time updates. Then and now, the pass.json on Apple's servers is updated and the device polls or receives a push.
What Apple has improved since 2015
The Wallet-era additions that actually matter for businesses:
- NFC tap-to-add (2019). Customers can tap a phone to an NFC tag and the pass install screen pops up. Faster than QR for in-store distribution.
- Better Maps integration. Geofenced passes show up on the lock screen with map context, which improves the redemption rate.
- Improved pass design templates. More color and image flexibility, especially for the generic pass type.
- Express transit. Specific to transit cards, but the underlying push and geofence infrastructure benefited the rest of the platform.
- Automatic pass updates via web service. This was technically possible in 2012, but Apple's reliability on it improved dramatically by 2018.
The 2012 mechanism still works. The 2026 toolkit around it is more polished.
For business operators today
What to do with this knowledge if you run a local business or a multi-location chain:
- You are using Apple Wallet, not Passbook. Even if a vendor contract or internal doc says Passbook, the product is now called Wallet. The technology is the same.
- Both Apple Wallet and Google Wallet matter. iOS share in the U.S. is roughly 60 percent, Android is 40 percent. A wallet-pass program needs to support both.
- .pkpass files still work. If a vendor sends you a sample .pkpass file from 2014, it will still install on a modern iPhone.
- Wallet-pass marketing in 2026 uses the same plumbing Passbook introduced in 2012, combined with better tools, larger audience (about 600 million Apple Pay users globally per Apple's Q4 2024 earnings), and improved push reliability.
If you want a deeper read on what to actually build, see the wallet pass marketing guide for the full operator playbook, then the Apple Wallet loyalty programs breakdown for the program-design specifics, and the wallet pass statistics roundup for the latest engagement numbers. If you are deciding between iOS and Android coverage, Apple Wallet vs Google Wallet for business walks through the differences. To estimate the revenue impact, the retention calculator takes about two minutes. For the original mechanics that have not changed since 2012, the wallet pass marketing guide covers the .pkpass file structure end to end, and the Apple Wallet loyalty programs piece shows how Starbucks, Walgreens, and Sephora actually structure their pass templates today. If you are weighing platform support, the Apple Wallet vs Google Wallet comparison breaks down feature parity, and the wallet pass statistics roundup has the open-rate and redemption benchmarks I cite when prospects ask. The retention calculator is the fastest way to put a dollar figure on the opportunity.
2026 Direct-to-Customer Channel Comparison
Cost per send · open rate · lock-screen surface · enrollment friction.
A note on the rebrand reasoning
Apple does not usually explain product renames in public, but the Wallet rebrand was an exception. Phil Schiller framed it at WWDC 2015 by pointing out that the app already held credit cards, debit cards, store credit cards, and rewards cards alongside boarding passes. The word "passbook" comes from the old paper bank passbook, which was a booklet a bank teller wrote your savings balance into. The metaphor stopped fitting once the app was holding payment instruments. "Wallet" was the natural replacement because that is what people actually call the thing that holds those items in real life.
The rename was also a hedge against confusion with Apple Pay, which had launched in October 2014 as a separate brand. Apple wanted Apple Pay to be the verb (you "Apple Pay" at a terminal) and Wallet to be the noun (the place your cards live). Passbook as a name was working against both.
What this means for vendor selection in 2026
If you are evaluating a wallet-pass vendor, the Passbook history matters in three concrete ways.
First, any vendor that cannot answer "is this Passbook or Wallet" without flinching probably does not understand the platform. They are the same thing. A vendor that treats them as separate products is selling marketing fluff.
Second, the .pkpass file format has been stable for over a decade. That means the technical risk of building a wallet-pass program is lower than almost any other marketing channel. The format that worked in 2012 still works. There is no looming deprecation, no major API rewrite on the horizon, no Apple announcement in the last five years that broke a working pass.
Third, the hard part of wallet-pass marketing has never been the pass file. It is the messaging strategy, the timing of pushes, the geofence relevance points, and the perk economics. Any vendor pitch that focuses on the pass file itself is missing where the actual leverage lives.
How Regulr AI fits into this history
I started Regulr AI because the wallet-pass plumbing Apple shipped in 2012 was never properly packaged for local businesses. The PassKit framework assumes you have a developer account, a backend, and an engineer. Most coffee shops, breweries, and restaurants do not. We handle the certificate, the pass type ID, the web service, the push infrastructure, and the design templates so the operator just needs a logo and a perk. The mechanism underneath is the same one Starbucks used at Passbook launch in 2012. The difference is that a single venue can now stand up a working program in an afternoon instead of a quarter.
FAQ
Is Apple Passbook still around? Yes, but it has been called Apple Wallet since September 2015. Same app, same underlying technology. The Passbook name was retired with iOS 9.
What replaced Apple Passbook? Apple Wallet replaced Passbook on September 16, 2015 with the release of iOS 9. It is the same app with a new name and added Apple Pay payment-card support.
When did Apple stop using Passbook? September 16, 2015. The name change shipped with iOS 9. Apple previewed it at WWDC 2015 in June and rolled it out to the public in September.
Do .pkpass files still work? Yes. The .pkpass format has not changed in any breaking way since iOS 6 in 2012. A pass file generated in 2014 still installs on iOS 18 in 2026. The signed-ZIP structure, pass.json schema, and image asset layout are all backward compatible.
What is the difference between Apple Wallet and Passbook? The name and the icon. Apple Wallet supports payment cards in addition to the passes Passbook handled, but the loyalty, ticket, and boarding-pass functionality is identical. The PassKit framework, .pkpass file format, and web service endpoints did not change.
Can I still build a Passbook pass? Yes. Modern Apple Wallet uses the identical PassKit framework that Passbook used. Anything you build today is technically a "Passbook pass" by the original spec. The Apple Developer Program ($99 per year) is still the gate.
Why is Apple Passbook still searched in 2026? Three reasons: aged blog content from 2012 to 2015 still uses the term, internal business documents and vendor contracts at large chains still reference Passbook, and inherited codebases use Passbook in variable and class names. Search engines see roughly 14,800 monthly U.S. queries for "passbook apple wallet" eleven years after the rename.
Sources
- Apple, "iOS 9 introduces Wallet," WWDC 2015 keynote (June 8, 2015) and iOS 9 release notes (September 16, 2015), developer.apple.com.
- Apple Q4 2024 Earnings Call (October 31, 2024), Apple Pay user reference.
- MacRumors, "Passbook Renamed to Wallet in iOS 9" (June 8, 2015).
- 9to5Mac, "iOS 9: Apple rebrands Passbook to Wallet" (June 8, 2015).
- TechCrunch, "Apple's Passbook Becomes Wallet In iOS 9" (June 8, 2015).
- Apple PassKit framework documentation, developer.apple.com/documentation/passkit.
- Apple, .pkpass file specification, "Wallet Developer Guide," developer.apple.com.
- Wikipedia, "Apple Wallet," section on Passbook history (accessed May 2026).
If you are an operator inheriting a Passbook reference in a contract or doc, treat it as Apple Wallet and move on. The technology is the same. The opportunity in 2026 is bigger than it was in 2012, because the install base is now most of the country.
Free: Customer Retention Checklist
A printable checklist with the strategies from this article, plus message templates you can copy-paste today.
No spam. Unsubscribe anytime. Your email stays private.
Get weekly retention tips
One actionable idea every Tuesday. No fluff, no spam.
Join 2,400+ local business owners. We respect your inbox.
Founder of Regulr & City Curated
Regulr is the customer retention layer for local businesses. It plugs into your POS, learns every customer's behavior, and runs personalized retention campaigns automatically — SMS, email, wallet pass updates, and RCS sentiment routing. Built for restaurants, coffee shops, salons, med spas, fitness studios, and other independent local businesses where every customer is a name and every visit matters.