Gathering Required Information for Troubleshooting Apple Pay In-App Provisioning or In-App Verification Issues

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:

1. Install the Apple Pay and Wallet profiles on your iOS or watchOS device. If the issue occurs on Mac, continue to Step 2.
2. Reproduce the issue and make a note of the timestamp when the issue occurred, while optionally capturing screenshots or video.
3. Gather a sysdiagnose on the same iOS or watchOS device, or on macOS.
4. Create a Feedback Assistant report with the following information:
   1. The bundle IDs
      1. App bundle ID
      2. Non-UI app extension bundle ID (if applicable)
      3. UI app extension bundle ID (if applicable)
   2. The serial number of the device.
      1. For iOS and watchOS: Open Settings > General > About > Serial Number (tap and hold to copy).
      2. For macOS: Open the Apple () menu > About This Mac > Serial Number.
   3. The SEID (Secure Element Identifier) of the device, represented as a HEX encoded string.
      1. For iOS and watchOS: Open Settings > General > About > SEID (tap and hold to copy).
      2. For macOS: Open the Apple () menu > About This Mac > System Report > NVMExpress > Serial Number.
   4. The sysdiagnose gathered after reproducing the issue.
   5. The timestamp (including timezone) of when the issue was reproduced.
   6. The type of provisioning failure (e.g., error at Terms & Conditions, error when adding a card, etc.)
   7. The issuer/network/country of the provisioned card (e.g., Mastercard – US)
   8. Last 4 digits of the FPAN
   9. Last 4 digits of the DPAN (if available)
   10. Was this test initiated from the Issuer App? (e.g., yes or no)
   11. The type of environment (e.g., sandbox or production)
   12. 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