Hi, You're here because you've had issues with your implementation of Wallet Extensions for Apple Pay In-App Provisioning or In-App Verification. To prevent sending sensitive credentials in plain text, create a new report in Feedback Assistant to share the details requested below with the appropriate log profiles installed. Gathering Required Information for Troubleshooting Apple Pay In-App Provisioning or In-App Verification Issues While troubleshooting Apple Pay In-App Provisioning or In-App Verification, it is essential that the issuer is able to collect logs on their device and check those logs for error message. This is also essential when reporting issues to Apple. To gather the required data for your own debugging as well as reporting issues, please perform the following steps on the test device: Install the Apple Pay and Wallet profiles on your iOS or watchOS device. If the issue occurs on Mac, continue to Step 2. Reproduce the issue and make a note of the timestamp when the issue occurred, while optionally capturing screenshots or video. Gather a sysdiagnose on the same iOS or watchOS device, or on macOS. Create a Feedback Assistant report with the following information: The bundle IDs App bundle ID Non-UI app extension bundle ID (if applicable) UI app extension bundle ID (if applicable) The serial number of the device. For iOS and watchOS: Open Settings > General > About > Serial Number (tap and hold to copy). For macOS: Open the Apple () menu > About This Mac > Serial Number. The SEID (Secure Element Identifier) of the device, represented as a HEX encoded string. For iOS and watchOS: Open Settings > General > About > SEID (tap and hold to copy). For macOS: Open the Apple () menu > About This Mac > System Report > NVMExpress > Serial Number. The sysdiagnose gathered after reproducing the issue. The timestamp (including timezone) of when the issue was reproduced. The type of provisioning failure (e.g., error at Terms & Conditions, error when adding a card, etc.) The issuer/network/country of the provisioned card (e.g., Mastercard – US) Last 4 digits of the FPAN Last 4 digits of the DPAN (if available) Was this test initiated from the Issuer App? (e.g., yes or no) The type of environment (e.g., sandbox or production) Screenshots or videos of errors and unexpected behaviors (optional). Important: From the logs gathered above, you should be able to determine the cause of the failure from PassbookUIService, PassKit or PassKitCore, and by filtering for your SEID or bundle ID of your app or app extensions in the Console app. Submitting your feedback Before you submit to Feedback Assistant, please confirm the requested information above is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Apple Pay client. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your client, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer

Hello, I have existing application that was created 2 years ago and we wanted to start developing wallet, but in order to do that I need to create new Identifiers with In-App Provisioning but unfortunately it is missing. Any idea on how to solve that?

Hi, We have a bank app which can activate tokenized payment cards (in Requires Activation status) on Apple devices. In my case some customers tried to activate their card token on their Apple Watch. Our card system gathered all the required card data with the PNO and sent them to our app. Our app called the PKPassLibrary.activate() method, but got back the Swedish localizedDescription "Oväntat fel" which means "Unexpected error" in English. We checked our card system logs and contacted our PNO, both found no issue and no explanation to the unexpected error. How can we identify the issue here? Can we somehow find a more detailed error log from Apple Server? Best regards, Adrian Lui

I am encountering an issue related to the status property within the payment object of the order.json file when opening an order in the iOS Wallet. According to the official documentation, the status property in the payment object is marked as deprecated. Based on this information, I removed the status property from the order.json. However, when I attempt to open the order in the iOS Wallet app, an error occurs, preventing the order from being opened. This creates confusion, as the documentation implies that the status property in the payment object is no longer required. However, the iOS Wallet app seems to still rely on the presence of this property or encounters an error when it’s missing. Tested on IOS 17.6.1 & IOS 18

I've implemented Push Provisioning, but am having trouble testing it. When I try to add a payment pass with my activationData, encryptedPassData, and ephemeralPublicKey, I see the "Add Card to Apple Pay" screen, but then when I click "Add Card", I get a "Could Not Add Card" message. When I inspect the error from didFinishAddingPaymentPass, it reads "The operation couldn’t be completed. (PKPassKitErrorDomain error 2.)". Is this error PKPassKitError.Code.unsupportedVersionError? What does this error means? Additional context: We use cordova-apple-wallet to generate certificates and add payment pass.

I am developing In-App Provisioning functionality within an iOS application. When I try to perform the process, the process fails and the following is displayed on the screen: "Your issuer does not yet offer support for this card". The PassbookUIService logs show: https://nc-pod8-smp device.apple.com:443/broker/v4/devices/xxxxxxxxxxxxxx/cards 200 Time profile: 0.25497 seconds { auxiliaryCapabilities = { }; eligibilityStatus = 0; sanitizedPrimaryAccountPrefix = ""; } ProvisioningStepEligibility: received eligibility status: 0 Showing eligibility issue with reason: 2 ProvisioningOperationComposer: Step 'eligibility' failed with error (null) Would like to seek your help to investigate the problem. Thanks

Hello, I’m encountering an issue with Apple Wallet orders. Every time I send an order file to my iPhone, I get the error message: “Error reading order file.” Steps Taken: 1. Order File Structure: • I created an order.json file with the minimal required fields, including: • Order Type Identifier (created on the Apple Developer portal) • Merchant Identifier: (created on the Apple Developer portal) • Status: open • Other necessary fields, such as authenticationToken, createdAt, updatedAt, and payment. 2. Manifest and Signature: • A manifest.json file was generated with the SHA-256 hash for each file (e.g., order.json, images). • The manifest was signed using my Apple developer certificates: • Signer Certificate: signerCert.pem • Signer Key: signerKey.pem • WWDR Certificate: wwdr.pem • Verification of the manifest and signature was done using OpenSSL: • Command used: openssl smime -verify -in signature -inform DER -content manifest.json -noverify • The verification was successful, but the iPhone still returns the error. 3. File Packaging: • The final package includes the following files: • order.json • Images (e.g., gardenya_logo.png) • manifest.json • signature • The files were packaged into a .order file (renamed from .zip). 4. Apple WWDR Certificate: • I used Apple WWDR MP CA 1 - G1 for signing the package. Issue: Despite following all steps in the Apple documentation, the order file cannot be read by the iPhone, and the error message displayed is “Error reading order file.” Additional Information: • Manifest and Signature: Both files have been validated and match the package contents. • Apple Developer Certificates: Used valid Apple Developer certificates. • Order Schema: The order.json file follows Apple’s schema for orders. Could you please provide guidance on resolving this issue? Any suggestions on what could be causing the error, or additional steps to check, would be greatly appreciated. Thank you for your support!

We have a requirement to include Apple Pay In-App Provisioning in our Mobile Application and we have an API from Backend to get the tokenReferenceID for a given Card. I want to query the passes from Apple Wallet to see if there are any matches to the given tokenReferenceID before I can decide whether to show the “Add to Apple Wallet” button or not. I went through all PassKit APIs but couldn’t find a way to query for passes with tokenReferenceID. We have primaryAccountIdentifier, deviceAccountIdentifier but which one should be used to match with tokenReferenceID? Can someone please help me how to query the Wallet passes with tokenReferenceID using PassKit?

I am working on a transit app that offers a digital ticketing product that is powered by a QR code being scanned. We have been successful in preventing the Apple Pay takeover experience from happening when a user tries to use this product next to the tap to pay terminals by making a call to PKPassLibrary.requestAutomaticPassPresentationSuppression(...) before the QR code is presented. However, our transit agency is piloting Express Transit on these turnstiles and we are noticing that this experience overrides the old NFC suppression. Is there a similar method available to us to suppress the express transit experience for users who are using these mobile ticketing products?

Hi, I’m encountering an issue in my app’s Wallet Extension, specifically within the Non-UI Extension, where we are unable to retrieve payment passes bound to a user’s account. The same code that successfully retrieves these bound cards in the main app does not work when used in the Non-UI Extension. Case-ID: 8932090 Steps to Reproduce: Set up In-App Provisioning: Ensure that the app has the necessary In-App Provisioning permissions. This functionality works correctly in the main app, confirming that the permissions are properly configured. Configure Wallet Extensions: Follow the Wallet Extensions documentation to configure the app, including all required settings for the Non-UI Extension. Add Code to Retrieve Payment Passes: In the main app’s LoginView, implement the following code in the handleLogin() method to retrieve payment passes: // Get the identifiers of payment passes that already exist in Apple Pay. paymentPassLibrary = self.passLibrary.passes(of: .secureElement) for pass in paymentPassLibrary { if let identifier = pass.secureElementPass?.primaryAccountIdentifier { if pass.isRemotePass && pass.deviceName.localizedCaseInsensitiveContains("Apple Watch") { remotePassIdentifiers.insert(identifier) } else if !pass.isRemotePass { passIdentifiers.insert(identifier) } } } Verify Functionality in Main App: Run the app and verify that the code successfully retrieves the payment passes bound to the user’s account. Implement Code in Non-UI Extension: Add the same code to the Non-UI Extension, specifically in the WNonUIExtHandler class within the override func status(completion: @escaping (PKIssuerProvisioningExtensionStatus) -> Void) method. Test in Wallet Extension: Run the Wallet Extension and observe that the payment passes are not retrieved when the code is executed in the Non-UI Extension. Has anyone encountered a similar issue or can provide insight into why the code might not work in the Non-UI Extension compared to the main app? Support Information: iOS Version: 17.5.1 Development environment: Xcode 15.4 (15F31d), macOS 14.3 (23D56) Any help or suggestions would be greatly appreciated. Thank you!

I have created wallet non UI extension for adding card through wallet. It's working perfect when I open wallet from iPhone. But when I open wallet from Watch app (Watch bridge app on iPhone not on physical apple watch) then my extension (issuer app) is not showing there. Any idea if I need to setup or configure anything to access extension through watch bridge app wallet?

I'm trying to add a pass to Apple Wallet, but it isn't being detected when I attempt to add it. I've created the .pkpass file, and it contains the following files: en.lproj/ icon.png icon@2x .png manifest.json pass.json signature { "formatVersion": 1, "passTypeIdentifier": "pass.com.yourdomain.com", "serialNumber": "123456", "teamIdentifier": "5ZXXXXXX", "description": "This is an Event Pass", "eventTicket": { "primaryFields": [ { "key": "event", "label": "EVENT", "value": "Concert" } ], "secondaryFields": [ { "key": "location", "label": "LOCATION", "value": "Example Venue" }, { "key": "date", "label": "DATE", "value": "2024-08-15" } ], "auxiliaryFields": [ { "key": "time", "label": "TIME", "value": "7:00 PM" } ], "backFields": [ { "key": "terms", "label": "TERMS & CONDITIONS", "value": "Non-refundable. Please arrive 30 minutes early." } ], "barcode": { "message": "1234567890", "format": "PKBarcodeFormatQR", "messageEncoding": "iso-8859-1" } }, "organizationName": "ORGANIZATION NAME", "logoText": "Concert 2024", "foregroundColor": "rgb(255, 255, 255)", "backgroundColor": "rgb(0, 0, 0)", "eventTicketStrip": { "primaryFields": [ { "key": "event", "label": "Event", "value": "Concert" } ] }, "relevantDate": "2024-08-15T19:00:00Z" } What I've Done So Far: Validated the Manifest: The SHA-1 hashes in the manifest.json match the actual files in the package. Checked the pass.json: It seems to be correctly formatted, and all fields are populated. Verified Pass Structure: The .pkpass file structure appears to be correct. Validate with PKpass Validator: It's seems like all points are valid I put screenshot over here. My Questions: What could be preventing Apple Wallet from detecting this pass? How can I verify if the signature is correctly applied? Are there any recommended online tools or methods to debug this pass and identify what might be wrong? I've tried using a few online validators, but the issue persists. Any guidance on how to resolve this would be greatly appreciated!

I am implementing apple wallet extension. As part of it I have developed UI and Non-UI extension. I have implemented status , pass entries and remote pass entries method to return as per apple standard. My problem is pass entries is showing correct list of cards/passes as it is able to match against phone wallet. But remote pass entries method is not able to access watch app/watch wallet to match the existing passes. Any help is appreciated. When we print passlibrary count it displays the count matching phone wallet. But it ignores watch wallet passes which belongs to our app.

After logging into Apple Wallet and clicking the "+" button to add a card, if the "debit/credit card" option is selected, a list of banks appears. ** When I select my bank's name from the list, I want the icon of the bank's mobile application to be displayed, just like in Revolut. ** **When the icon is clicked, I want to redirect the user to the application or the App Store version of the application. ** How can I set this up and where can I do it? Has anyone experienced this before?

Hi there! My app supports one language by default Ukrainian (uk) and does not support multiple languages. In Xcode settings "Development Language" is set to Ukrainian by default also. I have a PKAddPassButton on a ViewController and "Add to Apple Wallet" always appears in Ukrainian (Tested on real device iOS 15/16/17). Apple's "Getting Started with Apple Pay: In-App Provisioning, Verification, Security, and Wallet Extensions” document states that "The Add to Apple Wallet button adapts to the device language and the light and dark appearances, but the issuer app needs to adapt the language of the row selector text." When I change device language to French the “Add to Apple Wallet” button does not change to French. I created a fresh swift app, added PKAddPassButton the "Add to Apple Wallet" button, General -> Language & Region changed the device language to French, etc, but the "Add to Apple Wallet" button is always in English. Has anyone run into the same issue? How to adapt the "Add to Apple Wallet" button to the device system language?

Hi There, I am developing an apple wallet pass for an insurance company and i'm currently using the generic pass template. My question is, are there any restrictions from Apple on using any other pass type (such as coupon or store .,.etc) since they may be more suitable for what i am creating. I am definitely not going to use a boarding pass , but will i be able to use anything else ? thanks!!

Hi! I develop my own NFC reader as a sole proprietor. I would like to get the Apple VAS and Apple Access Pass certificates for my reader. How can I do that? Should I apply for Apple’s MFi program or it’s just for bigger organizations/companies? Are there any way? Thank you! Daniel

I'm trying to access my own financial data (I'm building a dashboard for my own personal finances) but can't seem to find an API for this. I found FinanceKit but it sounds like you have to be a big company to use that and that and it's more of a swift SDK than a generic API endpoint. Does anyone know how I can access my financial data without manual downloads?

Dear Apple developers, I am seeking for an answer to the following question regarding Apple Pay In-App Provisioning: My company (which is a financial institution) is currently implementing the Manual Provisioning for the bank cards issued by the company. Now the question is, will the In-App provisioning be required to be implemented in a timely manner? Will the bank app be removed from App Store if In-App is not available within X days once Manual is made live? Thanks all!

We are essentially implementing a membership card feature wherein the card details originates from a third-party provider and gets stored in the Apple Wallet. We are utilizing the Passkit Generator ( https://www.npmjs.com/package/passkit-generator ) for this purpose. The challenge, or rather issue, is that when this card is saved to Apple Wallet and tapped on the NFC reader, it only shows "Invalid Card." When we attempted to gather information from the third-party provider regarding this issue on both Android and iOS, they stated: "For IOS we do not have any experience to share with, rather than the fact we have implemented the VAS protocol under an NDA signed with Apple. Related to Passkit we do not have any experience with it." We require your assistance to identify any potential issues.