noticed something here, dont underasand why. but here in Retrieve the registrations for a device in Apple Developer Documentation in Retrieve the registrations for a device. There is no Authorization in the header to include, however, other endpoints support that? Is this header will be sent from Walle? meaning that it has been missed in the documentation ? https://developer.apple.com/documentation/walletorders/retrieve-the-registrations-for-a-device

Environment: Apple sandbox environment Test card number: 4622 9431 2318 9343 Phone models: iPhone 17 Pro Max, iPhone 16 Pro ios version: 26.3.1(a) Problem Description: After biometric verification passed, the Apple-provided JS method onpaymentauthorized was not called. Instead, the session.oncancel method was triggered directly. session.completeMerchantValidation(session): The session is as follows { epochTimestamp: 1774586541529, expiresAt: 1774590141529, merchantSessionIdentifier: 'SSH172FFE4410DA4F4E9C52E66AD440E472_A0E617ED4A56A343E07C6E1255BD4098423B3A8E1243236462D07B14B4A0F7C3', nonce: 'db797548', merchantIdentifier: '8D78418145EFBC98571CE62A98832FC4286A5F465FA1B0570919E156E901D33F', domainName: 'bifrost.lianlianpay-inc.com', displayName: '', signature: '308006092a864886f70d010702a0803080020101310d300b0609608648016503040201308006092a864886f70d0107010000a080308203e330820388a003020102020816634c8b0e305717300a06082a8648ce3d040302307a312e302c06035504030c254170706c65204170706c69636174696f6e20496e746567726174696f6e204341202d20473331263024060355040b0c1d4170706c652043657274696669636174696f6e20417574686f7269747931133011060355040a0c0a4170706c6520496e632e310b3009060355040613025553301e170d3234303432393137343732375a170d3239303432383137343732365a305f3125302306035504030c1c6563632d736d702d62726f6b65722d7369676e5f5543342d50524f4431143012060355040b0c0b694f532053797374656d7331133011060355040a0c0a4170706c6520496e632e310b30090603550406130255533059301306072a8648ce3d020106082a8648ce3d03010703420004c21577edebd6c7b2218f68dd7090a1218dc7b0bd6f2c283d846095d94af4a5411b83420ed811f3407e83331f1c54c3f7eb3220d6bad5d4eff49289893e7c0f13a38202113082020d300c0603551d130101ff04023000301f0603551d2304183016801423f249c44f93e4ef27e6c4f6286c3fa2bbfd2e4b304506082b0601050507010104393037303506082b060105050730018629687474703a2f2f6f6373702e6170706c652e636f6d2f6f63737030342d6170706c65616963613330323082011d0603551d2004820114308201103082010c06092a864886f7636405013081fe3081c306082b060105050702023081b60c81b352656c69616e6365206f6e207468697320636572746966696361746520627920616e7920706172747920617373756d657320616363657074616e6365206f6620746865207468656e206170706c696361626c65207374616e64617264207465726d7320616e6420636f6e646974696f6e73206f66207573652c20636572746966696361746520706f6c69637920616e642063657274696669636174696f6e2070726163746963652073746174656d656e74732e303606082b06010505070201162a687474703a2f2f7777772e6170706c652e636f6d2f6365727469666963617465617574686f726974792f30340603551d1f042d302b3029a027a0258623687474703a2f2f63726c2e6170706c652e636f6d2f6170706c6561696361332e63726c301d0603551d0e041604149457db6fd57481868989762f7e578507e79b5824300e0603551d0f0101ff040403020780300f06092a864886f76364061d04020500300a06082a8648ce3d0403020349003046022100c6f023cb2614bb303888a162983e1a93f1056f50fa78cdb9ba4ca241cc14e25e022100be3cd0dfd16247f6494475380e9d44c228a10890a3a1dc724b8b4cb8889818bc308202ee30820275a0030201020208496d2fbf3a98da97300a06082a8648ce3d0403023067311b301906035504030c124170706c6520526f6f74204341202d20473331263024060355040b0c1d4170706c652043657274696669636174696f6e20417574686f7269747931133011060355040a0c0a4170706c6520496e632e310b3009060355040613025553301e170d3134303530363233343633305a170d3239303530363233343633305a307a312e302c06035504030c254170706c65204170706c69636174696f6e20496e746567726174696f6e204341202d20473331263024060355040b0c1d4170706c652043657274696669636174696f6e20417574686f7269747931133011060355040a0c0a4170706c6520496e632e310b30090603550406130255533059301306072a8648ce3d020106082a8648ce3d03010703420004f017118419d76485d51a5e25810776e880a2efde7bae4de08dfc4b93e13356d5665b35ae22d097760d224e7bba08fd7617ce88cb76bb6670bec8e82984ff5445a381f73081f4304606082b06010505070101043a3038303606082b06010505073001862a687474703a2f2f6f6373702e6170706c652e636f6d2f6f63737030342d6170706c65726f6f7463616733301d0603551d0e0416041423f249c44f93e4ef27e6c4f6286c3fa2bbfd2e4b300f0603551d130101ff040530030101ff301f0603551d23041830168014bbb0dea15833889aa48a99debebdebafdacb24ab30370603551d1f0430302e302ca02aa0288626687474703a2f2f63726c2e6170706c652e636f6d2f6170706c65726f6f74636167332e63726c300e0603551d0f0101ff0404030201063010060a2a864886f7636406020e04020500300a06082a8648ce3d040302036700306402303acf7283511699b186fb35c356ca62bff417edd90f754da28ebef19c815e42b789f898f79b599f98d5410d8f9de9c2fe0230322dd54421b0a305776c5df3383b9067fd177c2c216d964fc6726982126f54f87a7d1b99cb9b0989216106990f09921d00003182018730820183020101308186307a312e302c06035504030c254170706c65204170706c69636174696f6e20496e746567726174696f6e204341202d20473331263024060355040b0c1d4170706c652043657274696669636174696f6e20417574686f7269747931133011060355040a0c0a4170706c6520496e632e310b3009060355040613025553020816634c8b0e305717300b0609608648016503040201a08193301806092a864886f70d010903310b06092a864886f70d010701301c06092a864886f70d010905310f170d3236303332373034343232315a302806092a864886f70d010934311b3019300b0609608648016503040201a10a06082a8648ce3d040302302f06092a864886f70d01090431220420de088abe02a4f981acade953307d1922bf121ff836f7dfdeedd7689f6aa8c82c300a06082a8648ce3d04030204463044022040e4fbacada10a457f02cbabfd75dea2c9316494458ab473d70fd4e600673fd902204efcde5b48f29c9a99a179a8193d56a954ed216f6643afc2af0d80acfcc2e879000000000000', operationalAnalyticsIdentifier: ':8D78418145EFBC98571CE62A98832FC4286A5F465FA1B0570919E156E901D33F', retries: 0, pspId: '8D78418145EFBC98571CE62A98832FC4286A5F465FA1B0570919E156E901D33F' } code-block

Environment: Apple sandbox environment Test card number: 4622 9431 2318 9343 Phone models: iPhone 17 Pro Max, iPhone 16 Pro ios version: 26.3.1(a) Problem Description: After biometric verification passed, the Apple-provided JS method onpaymentauthorized was not called. Instead, the session.oncancel method was triggered directly. session.completeMerchantValidation(session): { epochTimestamp: 1774586541529, expiresAt: 1774590141529, merchantSessionIdentifier: 'SSH172FFE4410DA4F4E9C52E66AD440E472_A0E617ED4A56A343E07C6E1255BD4098423B3A8E1243236462D07B14B4A0F7C3', nonce: 'db797548', merchantIdentifier: '8D78418145EFBC98571CE62A98832FC4286A5F465FA1B0570919E156E901D33F', domainName: 'bifrost.lianlianpay-inc.com', displayName: '', signature: '308006092a864886f70d010702a0803080020101310d300b0609608648016503040201308006092a864886f70d0107010000a080308203e330820388a003020102020816634c8b0e305717300a06082a8648ce3d040302307a312e302c06035504030c254170706c65204170706c69636174696f6e20496e746567726174696f6e204341202d20473331263024060355040b0c1d4170706c652043657274696669636174696f6e20417574686f7269747931133011060355040a0c0a4170706c6520496e632e310b3009060355040613025553301e170d3234303432393137343732375a170d3239303432383137343732365a305f3125302306035504030c1c6563632d736d702d62726f6b65722d7369676e5f5543342d50524f4431143012060355040b0c0b694f532053797374656d7331133011060355040a0c0a4170706c6520496e632e310b30090603550406130255533059301306072a8648ce3d020106082a8648ce3d03010703420004c21577edebd6c7b2218f68dd7090a1218dc7b0bd6f2c283d846095d94af4a5411b83420ed811f3407e83331f1c54c3f7eb3220d6bad5d4eff49289893e7c0f13a38202113082020d300c0603551d130101ff04023000301f0603551d2304183016801423f249c44f93e4ef27e6c4f6286c3fa2bbfd2e4b304506082b0601050507010104393037303506082b060105050730018629687474703a2f2f6f6373702e6170706c652e636f6d2f6f63737030342d6170706c65616963613330323082011d0603551d2004820114308201103082010c06092a864886f7636405013081fe3081c306082b060105050702023081b60c81b352656c69616e6365206f6e207468697320636572746966696361746520627920616e7920706172747920617373756d657320616363657074616e6365206f6620746865207468656e206170706c696361626c65207374616e64617264207465726d7320616e6420636f6e646974696f6e73206f66207573652c20636572746966696361746520706f6c69637920616e642063657274696669636174696f6e2070726163746963652073746174656d656e74732e303606082b06010505070201162a687474703a2f2f7777772e6170706c652e636f6d2f6365727469666963617465617574686f726974792f30340603551d1f042d302b3029a027a0258623687474703a2f2f63726c2e6170706c652e636f6d2f6170706c6561696361332e63726c301d0603551d0e041604149457db6fd57481868989762f7e578507e79b5824300e0603551d0f0101ff040403020780300f06092a864886f76364061d04020500300a06082a8648ce3d0403020349003046022100c6f023cb2614bb303888a162983e1a93f1056f50fa78cdb9ba4ca241cc14e25e022100be3cd0dfd16247f6494475380e9d44c228a10890a3a1dc724b8b4cb8889818bc308202ee30820275a0030201020208496d2fbf3a98da97300a06082a8648ce3d0403023067311b301906035504030c124170706c6520526f6f74204341202d20473331263024060355040b0c1d4170706c652043657274696669636174696f6e20417574686f7269747931133011060355040a0c0a4170706c6520496e632e310b3009060355040613025553301e170d3134303530363233343633305a170d3239303530363233343633305a307a312e302c06035504030c254170706c65204170706c69636174696f6e20496e746567726174696f6e204341202d20473331263024060355040b0c1d4170706c652043657274696669636174696f6e20417574686f7269747931133011060355040a0c0a4170706c6520496e632e310b30090603550406130255533059301306072a8648ce3d020106082a8648ce3d03010703420004f017118419d76485d51a5e25810776e880a2efde7bae4de08dfc4b93e13356d5665b35ae22d097760d224e7bba08fd7617ce88cb76bb6670bec8e82984ff5445a381f73081f4304606082b06010505070101043a3038303606082b06010505073001862a687474703a2f2f6f6373702e6170706c652e636f6d2f6f63737030342d6170706c65726f6f7463616733301d0603551d0e0416041423f249c44f93e4ef27e6c4f6286c3fa2bbfd2e4b300f0603551d130101ff040530030101ff301f0603551d23041830168014bbb0dea15833889aa48a99debebdebafdacb24ab30370603551d1f0430302e302ca02aa0288626687474703a2f2f63726c2e6170706c652e636f6d2f6170706c65726f6f74636167332e63726c300e0603551d0f0101ff0404030201063010060a2a864886f7636406020e04020500300a06082a8648ce3d040302036700306402303acf7283511699b186fb35c356ca62bff417edd90f754da28ebef19c815e42b789f898f79b599f98d5410d8f9de9c2fe0230322dd54421b0a305776c5df3383b9067fd177c2c216d964fc6726982126f54f87a7d1b99cb9b0989216106990f09921d00003182018730820183020101308186307a312e302c06035504030c254170706c65204170706c69636174696f6e20496e746567726174696f6e204341202d20473331263024060355040b0c1d4170706c652043657274696669636174696f6e20417574686f7269747931133011060355040a0c0a4170706c6520496e632e310b3009060355040613025553020816634c8b0e305717300b0609608648016503040201a08193301806092a864886f70d010903310b06092a864886f70d010701301c06092a864886f70d010905310f170d3236303332373034343232315a302806092a864886f70d010934311b3019300b0609608648016503040201a10a06082a8648ce3d040302302f06092a864886f70d01090431220420de088abe02a4f981acade953307d1922bf121ff836f7dfdeedd7689f6aa8c82c300a06082a8648ce3d04030204463044022040e4fbacada10a457f02cbabfd75dea2c9316494458ab473d70fd4e600673fd902204efcde5b48f29c9a99a179a8193d56a954ed216f6643afc2af0d80acfcc2e879000000000000', operationalAnalyticsIdentifier: ':8D78418145EFBC98571CE62A98832FC4286A5F465FA1B0570919E156E901D33F', retries: 0, pspId: '8D78418145EFBC98571CE62A98832FC4286A5F465FA1B0570919E156E901D33F' }

As per the guide, we need to email apple-pay-provisioning @apple.com but email bounces with error recipient no longer on server We also tried to send email to apple-pay-inquiries @apple.com but getting the same error. How do we contact Apple to request for the entitlement?

My application is from a bank that provides payment passes, and when I try to retrieve passes already enrolled in the wallet, it always returns empty. Is there something I need to configure for it to work? This is what I've tried, and it hasn't worked: let pkPassLibrary = PKPassLibrary() let paymentPasses = pkPassLibrary.passes(of:.payment) let pkPassLibrary = PKPassLibrary() let paymentPasses: [PKSecureElementPass]=pkPassLibrary .passes(of: .secureElement) .compactMap { $0 as? PKSecureElementPass }

I'm creating an event ticket Apple Wallet Pass and setting a light-coloured background image. When I do this, it automatically sets the foregroundColor to white, even when I explicitly set it to black. What's strange is that on my Mac, the foregroundColor appears as intended, and I can set it to any color I want, but when I AirDrop the pass to my iPhone, it sets the color to white, regardless of what I set the foregroundColor to. This means the text becomes completely illegible for my users, with white text on a white background image. If I remove the background image, the foregroundColor works fine. Is there a way to have a light-colored background image with dark text, or am I forced to have a dark-colored background image? Here are the colors in my pass.json: backgroundColor: "rgb(255, 255, 255)" foregroundColor: "rgb(0, 0, 0)" labelColor: "rgb(0, 0, 0)" I've attached what the pass looks like on my Mac and my iPhone.

My application is from a bank that provides payment passes, and when I try to retrieve passes already enrolled in the wallet, it always returns empty. Is there something I need to configure for it to work? This is what I've tried, and it hasn't worked

We have developed an app that communicates with an external reader using BLE, and the reader also supports NFC. We are implementing a feature that uses PKPassLibrary.requestAutomaticPassPresentationSuppression to prevent the Wallet from appearing when unlocking a lock. We have already completed the approval process for the entitlement required to enable Pass Presentation Suppression, referencing Apple’s documentation: https://developer.apple.com/documentation/passkit/pkpasslibrary/requestautomaticpasspresentationsuppression(responsehandler:) In most cases, this works as expected and the Wallet popup does not appear. However, in some cases — particularly when the app is running in the foreground — the Wallet still appears for users. We have verified that the app bundle includes the required entitlement, and the Info.plist correctly specifies the Pass Presentation Suppression key set to true. Could you please help us understand under what conditions this behavior might still occur, or if any additional configuration is required?

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?

Hi, We are able to successfully perform in-app provisioning and add cards to the native wallet. However, we are unable to retrieve the existing card status from the wallet. Even when the card is already added to the device or Apple Watch, the status is always returning as false for both. Could you please let us know if there are any additional configurations, entitlements, or issuer onboarding steps required to retrieve the existing card status from Apple Wallet?

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?