Wallet Q&A

Our company, Rimoter Ltd., is developing a door access card reader based on NXP technology. We have signed the NDA and registered on the MFi portal, but we have not received any information on how to create a card for Apple Wallet to enable door access. Could you please provide the relevant documentation or direct us to the appropriate contact within Apple?

Apple VAS Passes are often more that sufficent with needs of institutions, but Most would like to Switch from Visual Codes (Barcode or QR-Codes) to NFC. The Limit of 64 Chars, Payload is very limiting. Compared to Google Wallet (Google Smart Tap) where multiple kilobyte of payload is possible, (or at least 256 Byte), it would be nice if Apple would increase the Payload size for VAS. Yes Most Reader only can read up to 240 Bytes in one go, but there are possible ways to continious read (pagination) the Payload. As VAS payload is Not stored within the Secure Element, it would be good to increase it. Apple Access Most often does not provide real benefits. The price and requirements are to high for the additional Elements, and also limited to the benefits for Most use-cases. For universities and non-Profits VAS is The best option and should not be threated as a second Child or second class Element.

I have a few products that want to integrate with the Wallet, but want to display very specific domain information. Since there isn't a 1:1 lab for wallet this year I'll vaguely post my feedback here. FB21642083 - Allow developers to add domain type cards to wallet and passes Happy to have further discussion in Feedback.

We implement with eduTAP (https://eduTAP.eu) a Framework for Universities to easily adopt wallet Passes in Europe (or globally). The new Pass Designer Sounds Great and the pkpasstemplate Idee very promissing and helpful. Will there also be more Details for additional passtypes Like Access Passes or Identity Passes on how to Design them, without relying on vendors? In the Log run only identity wallet will fullfil the European legal requirements for Student IDs, not the access Passes currently promoted by Apple. They will Stay for closed Loop payments and physical Access Control but not as a Student Identity card. Which is Most often used off-campus.

In the WWDC presentation, a "guest key" was mentioned, but only in relation to watchOS. Are there any more details about that somewhere? I can't find it on the developer documentation for either Home or Wallet. https://9to5mac.com/2026/06/09/top-watchos-27-features-that-will-enhance-your-apple-watch/

I'm curious as to the rationale as to why Japanese IDs are not allowed on wearOS, even though American ones are.

For high-throughput in-person ID Verifier flows, is it recommended to call MobileDocumentReader.prepare() before the operator starts a check and cache the prepared MobileDocumentReaderSession for one later requestDocument call? Or should apps only call prepare() after explicit user intent? If prewarming is supported what should invalidate a prepared session?

We are an issuer processor for payment cards. Our TSP is Discover. Two questions about payment card features in Apple Wallet that we and our users would really love to see. Live balance on the face of a prepaid card in Apple Wallet. Currently, this is not something we can do inside Apple Wallet. Curious if Apple has a payment card balance display feature anywhere on the roadmap (I believe there is a similar feature called "connected cards" but it's not globally available and not exactly the same) Custom push notification into Apple Wallet for a card, similar to how Apple displays notifications of purchase receipts, except controlled by card issuer processors. As a bonus, it would be great to send rich text messages with deep links to our own app.

I’m building an in-person ProximityReader ID Verifier Display Only flow for venue age checks. Right now on iOS 26, we use a single MobileDocumentDisplayRequest with allowedDocumentTypes: [.photoID, .driversLicense] and only request ageAtLeast(21). For reliability and broad credential support, is that the recommended request shape for both Passport-derived Photo ID and mobile driver’s license / State ID? Or should apps implement separate request paths when they want to support both document families? Trying to optimize for the most predictable Wallet behavior. Thank you!

As European Universities do need selective Selective Disclosure Verifiable Credentials (mDoc ISO 18013-5, SD-JWT, or W3C VD Date Model) for their student IDs and most usage of student and Heigher Education Institutions IDs are off campus, neither Apple VAS nor Apple Access Passes are sufficent. When will the Identity Wallet (Like TSA Approved Passes in the US) will be avaliable for broader usage?

I was glad to see the Apple provided wallet pass designer app. Unfortunately, it requires macOS 27. Where are the requirements documented, I didn't catch them anywhere. For example, if I upgrade a Neo (non M-series), will it work there too? Is macOS 27 the only requirement to run it?