What’s New in Apple Wallet (iOS 27 / WWDC26) — and What It Means for Digital Cards

In 2026, Apple pushed Wallet further than boarding passes and credit cards. WWDC26’s “What’s new in Wallet” session and the iOS 27 Wallet app changes matter if you share identity with a PKPass—whether you build with PassKit yourself or use a template tool like Aplcard.

Direct answer: iOS 27 adds Poster Generic styling, Create a Pass for personal barcode cards, Pass Designer + Pass Builder for issuers, new barcode formats, and featured actions on the pass face. Creators still need a signed .pkpass for a polished LinkedIn or payment identity pass—Aplcard remains the no-account path for that job.

Apple, Apple Wallet, and related marks are trademarks of Apple Inc. Aplcard is not affiliated with Apple.

Poster Generic: richer pass faces

Poster Generic is a new top-level pass style aimed at bold, full-bleed backgrounds with a primary logo, header fields, primary fields, a footer, and an optional barcode. On older iOS versions, Apple recommends also including the classic generic style so the pass still installs.

For digital business cards, that means Wallet faces can look more like a designed card and less like a sparse ticket stub—when issuers adopt the style. Template tools will follow as the ecosystem updates.

Create a Pass (built into Wallet)

iOS 27’s Create a Pass (via the + menu in Wallet) lets people digitize membership cards, tickets, and similar codes. You can scan with the camera / Visual Intelligence or create manually. Templates include Standard, Membership, and Event, with colors and field types like membership, contact, or coupon code.

This sherlocks a class of “scan my gym barcode into Wallet” apps. It does not replace a branded social or payment identity pass with your LinkedIn URL, Instagram handle, or Venmo QR packaged as a shareable .pkpass for networking.

Pass Designer and Pass Builder (for developers)

Apple announced Pass Designer (Mac app for designing templates) and Pass Builder (Swift on Server package + buildpass CLI) to design, personalize, and sign passes at scale. That lowers friction for companies issuing loyalty and event passes.

Most creators still will not open Xcode or run a Linux signing pipeline. They want: pick template → paste handle → download .pkpass. That is Aplcard’s wedge versus PassKit APIs and Passmint-style developer platforms.

New barcodes and featured actions

iOS 27 adds barcode formats including EAN-13, Code 39, Codabar, and Interleaved 2 of 5 (ITF). Issuers should still include a QR (or other older-compatible format) for devices on iOS 26 and earlier.

Featured actions let passes surface tappable actions below the face—useful for “open profile” style flows when issuers wire them. For a simple identity pass today, a clear QR to your profile remains the universal pattern.

What this means for Aplcard users

Native Create a Pass is perfect when you already have a physical barcode and want it in Wallet. Aplcard is for when the “code” is your social or payment identity and you want a branded pass without an Apple Developer account or CRM signup.

As Poster Generic and actions roll out, expect identity passes to look sharper industry-wide. Start now with a LinkedIn or payment template at pass.honrly.com/create/linkedin—your QR works today on current Wallet.

Quick answers