Code found in Apple's backend suggests the iOS 27 Apple Wallet Create a Pass feature would let users scan physical cards and tickets to generate digital passes, bypassing the usual requirement for businesses to build native Wallet support. 9to5Mac and MacRumors first reported the backend-code findings on April 16, 2026, after developer Nicolás Alvarez discovered the functions; later reporting in early May added the more specific "Create a Pass" framing.
As of May 22, 2026, Apple has confirmed the WWDC schedule but has not announced "Create a Pass," so the feature remains unconfirmed until Apple addresses it in a keynote, beta release, or developer documentation.
The gap this feature would reportedly close is a persistent one. Getting a card into Apple Wallet currently requires the issuer to build native support; if a business has not integrated with Apple's pass system, the physical card stays in your pocket. The appeal is easy to understand: users already run into plenty of cards, tickets, and memberships that still do not offer an "Add to Apple Wallet" button. Whether "Create a Pass" actually closes that gap is a different question, and the leaked code doesn't answer it.
What "Create a Pass" might do
The reported mechanic is simple enough: point your camera at a physical card's barcode, and Wallet produces a digital pass. Reports so far point to event tickets, gym membership cards, and rewards cards as likely examples, with the basic flow described as scanning a barcode and receiving a pass directly in Wallet.
What Apple is building underneath that flow is still unclear, and the distinction matters more than it might seem at first. There is a real difference between a pass that simply stores a barcode and a fully structured Wallet pass with labeled fields, expiration details, issuer branding, and live-update support. The leaked code does not show which version Apple is pursuing.
That distinction determines whether a user-generated pass works as a real credential or just displays the right code on screen.
Where Apple Wallet scans could fail
Third-party apps have offered barcode-scanning pass creation for years. Those workarounds have always carried the same limitation: creating a pass is easier than guaranteeing a store, gym, or venue scanner will accept it. Google widely rolled out a comparable "Everything else" pass creator for Google Wallet in the US in August 2024. That puts Apple roughly two years behind Google on this particular capability, though Apple has not confirmed whether its version will work the same way.
A coffee shop loyalty card is the easy case: if the barcode number is stored accurately and shown in a readable format, many terminals should be able to scan it. Concert and stadium tickets are trickier because many venues now use rotating or time-limited barcodes to prevent screenshot duplication. A static capture may work at some venues and fail at others, and Apple cannot control how the venue's scanner treats it.
A native Apple implementation does have one advantage over the third-party workarounds: consistent formatting and deeper integration with Wallet's infrastructure should reduce the construction-side failure modes that come from how those apps assemble a pass. But the acceptance side, what happens at the merchant or venue terminal, is a separate problem and not one Apple can solve from its end.
Other iOS 27 features in the leak
The Wallet item is one of four functions Alvarez found in Apple's backend code. The others reportedly involve Visual Intelligence scanning nutrition labels, Contacts adding people from business cards, and Safari using AI to name tab groups based on open pages. All remain unconfirmed, and the final versions could differ from what the server-side code suggests.
What Apple still needs to explain
Apple's WWDC 2026 keynote is scheduled for June 8 at 10 a.m. Pacific, where the company is expected to preview iOS 27 and other next-generation platform updates. Three specifics will determine whether "Create a Pass" is a broadly useful addition or a feature with a narrow practical range.
Whether passes are issuer-grade or display-only. A fully structured Wallet pass with live fields and update support is a different product from a barcode wrapped in Wallet's interface. The everyday utility of the feature turns almost entirely on this, and it is the one thing the current leak does not clarify. Apple's announcement should address it directly.
Which pass types are supported at launch. Loyalty cards and gym memberships are the natural starting point, and the case for them is solid. If managed event tickets are included, Apple will need to explain how the feature handles the fraud-prevention systems venues have specifically built to block user-generated copies. If event tickets are excluded or heavily caveated, users are better off knowing that before they try it at the gate.
Rollout scope. Some existing Wallet functionality is tied to specific markets. Apple's higher-trust Wallet identity rollout remains limited: Apple said in November 2025 that driver's licenses and state IDs were live in 12 US states and Puerto Rico, while Japan's My Number Card marked the feature's first international launch. "Create a Pass" doesn't carry the same regulatory weight, but Wallet features with higher-trust requirements have followed staged rollouts before. Whether this one launches globally will affect how many users can actually put it to work when iOS 27 ships.
If the feature works reliably, it could noticeably lighten the load on physical wallets in everyday life. For loyalty cards and similar credentials, that case holds. For managed event tickets and other pass types where issuers have actively worked to control duplication, the picture is murkier. The leak points to a plausible feature, but June 8 is when the implementation details should determine whether it actually delivers.
Comments
Be the first, drop a comment!