While troubleshooting Tap to Pay on iPhone, it is essential that the developer is able to collect logs on their device and check those logs for error messages. 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 Tap to Pay profile on your iPhone. 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 iPhone. Create a Feedback Assistant report with the following information: The bundle ID The serial number of the device. For iOS, open Settings > General > About (tap and hold to copy). The SEID (Secure Element Identifier) of the device, represented as a HEX encoded string. For iOS, open Settings > General > About > SEID (tap and hold to copy). The sysdiagnose gathered after reproducing the issue. The timestamp (including timezone) of when the issue was reproduced. Screenshots or videos of errors and unexpected behaviors (optional). Submitting Your Feedback After your submission to Feedback Assistant is complete, please respond to your post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your app, a configuration issue within your developer account, app configuration, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer

If your developer team has been approved to implement Tap to Pay on iPhone, you were granted a managed entitlement configured only for the Development distribution type. When compiling your project for any other distribution type, such as App Store, Ad hoc, or In-house (for Enterprise apps), the build with fail with errors. You can resolve these errors by contacting the initial provisioning team and asking for production distribution review/validation. For more information on requesting the Tap to Pay on iPhone entitlement, see the documentation below: Setting up Tap to Pay on iPhone https://developer.apple.com/documentation/proximityreader/setting-up-the-entitlement-for-tap-to-pay-on-iphone To request for permission for the App Store, Ad hoc, or In-house distribution types, please respond to the confirmation email received after your initial entitlement request. The provisioning team will provide the next steps to begin the public distribution review process and eventually approve your app for distribution via TestFlight, the App Store, or to Enterprise managed devices. Note: The only team that manages this entitlement is the same provisioning team that granted you access, so you'll need to follow-up with the same team that approved your initial request to resolve this compilation and archival issue. Once you're approved for App Store distribution, the same steps used to distribute your app via TestFlight or In-house will be successful. If you continue to have errors after confirming you've been granted the expected distribution type for your app configuration, please see the post below, then create a new post for your issue and mention your Feedback ID after following the steps: Gathering Required Information for Troubleshooting Tap to Pay on iPhone https://developer.apple.com/forums/thread/775784 Cheers, Paris X Pinkney |  WWDR | DTS Engineer

Hello, I’m trying to better understand the implementation flow for Tap to Pay on iPhone. In a partner onboarding portal (Partner Hub), the process is presented in the following stages: • Registration • Prerequisites • Operations & Setup • Certification • Launch However, it’s not clear what actually changes after completing the “Prerequisites” stage. Questions: After completing “Prerequisites”, are there any changes in terms of entitlements or capabilities provided by Apple? Is access to Tap to Pay functionality enabled at this point, or does it depend on steps outside of Apple’s developer environment? At what stage is the production entitlement typically granted? Is there any Apple-specific action required between “Prerequisites” and “Operations & Setup”? I would appreciate any clarification on how this transition works from Apple’s perspective. Thank you.

Hi everyone, we’ve been waiting since May 30 for our Tap to Pay on iPhone entitlement to be enabled for distribution, but it’s still only active for development (Case‑ID: 14485444). We submitted: A new video recorded from an external device showing the full checkout flow Updated merchant education using the ProximityReaderDiscovery.Topic.payment(.howToTap) API, as suggested by Apple The team initially said the education was compliant, then said it wasn’t. We fixed everything, sent the updated materials, and haven’t heard back in days. We can’t even upload the app to TestFlight because of this error: Profile doesn't include the com.apple.developer.proximity-reader.payment.acceptance entitlement It’s now been almost a month and a half, and this delay is becoming critical. It’s blocking both internal testing and our production release. We’d really appreciate clarity on: Do we need to submit another request via the form? Or is it enough to reply to the existing email thread? Also, are there any direct contacts or escalation paths we can use? Any help or guidance appreciated

Hi, I am developing an app that uses the Host Card Emulation (HCE) technology available on iOS. Our team is using the official HCE app entitlement, and we are testing the SDK’s behavior when the app is selected as the default contactless payment application. On devices located in supported regions, the system automatically displays a setting where the user can choose the default app. For colleagues who are located in those regions, the toggle appears normally. For development and QA purposes, I would like to understand whether there is an officially supported method to test the default-app selection behavior on devices that are not in a region where the feature is available. Any guidance on the correct testing approach would be appreciated. Thank you!

We are developing an iOS application that requires NFC-based communication using ISO 7816 / ISO 14443 standards for secure element interaction as part of a card provisioning workflow. We would like clarification on the following points: Is it possible to provision a payment card or securely add a card to an NFC-enabled device using direct ISO 7816 APDU communication via NFCTagReaderSession? If not, is Apple Pay In-App Provisioning (PassKit framework) the only supported approach for enabling contactless payment functionality on iPhone? What specific entitlements are required if the use case involves secure element communication for token provisioning (not bypassing Apple Pay)? We have already requested the relevant NFC entitlements through our Apple Developer account and are awaiting a response. Any guidance on the correct architecture and approval requirements would be greatly appreciated. Thank you in advance for your support.

Hello Team, We applied for Tap to Pay on iPhone entitlement and were approved, but on distribution support it's only showing Development. We can build and debug Tap to Pay on development, but unable to build release. We opened ticket with Apple support but they were saying it was configured correctly. I attached screenshot of our developer account entitlement for Tap to Pay. It clearly said Development only.

Hi Apple team, We're planning to integrate Tap to Pay on iPhone feature in our product, and found there's a QR code button on the your Figma design: https://www.figma.com/design/2SOXmeLvimllvT67MTMLOy/Tap-to-Pay-on-iPhone--Community-?node-id=0-1&t=E3XskpsLctTuZvg5-1 Questions: is there any official documentation about the QR code button on this screen? What happens when user clicks on QR button? What're the suggestions to show/hide that button, and can we customize it? Thanks.

Hi I have been trying to purchase apple developer program since week now...and not working i have tried multiple cards, debit/credit (visa, mastercard) my bank is not blocking my payment either. It keeps saying authorisaion failed on Apple end. I tried use different WiFi still same & different Apple ID it does same thing. Anyone know what going on??

Hello, I’m having trouble accessing the Tap to Pay on iPhone Marketing Toolkit for Canada. I’m trying to complete section 6 of the Tap to Pay checklist, which directs me to the Marketing Toolkit page. After visiting the link, I enter our Team ID and select Canada as the region. This takes me to a page with Box links and passwords for each region. However, the password for Canada doesn’t work. When I enter it I receive an error: “Wrong password.” I’m not sure how to proceed from here. I’ve contacted Developer Support twice over the past two weeks but haven’t received a response yet. I’m hoping someone here can help me get access. Thank you, Alex

Hi, for Tap to Pay distribution, apple asked to submit an app review check list, in which there are merchant education questions. What does it mean by these questions, is apple asking us to show tutorials or help articles on the app or via company's help support website? Pls help as im not sure how to move forward.

Hi, We applied for Tap to Pay on iPhone entitlement and were approved, but on distribution support it's only showing Development. We can build and debug Tap to Pay on development, but unable to build release. We opened ticket with Apple support but they were saying it was configured correctly. I attached screenshot of our developer account entitlement for Tap to Pay. It clearly said Development only.

For Apple Pay Testing purposes, we're trying out cards from https://developer.apple.com/apple-pay/sandbox-testing/ Visa, AMEX, Discover cards can be added to the wallet. But all 5 of the listed options for Mastercard cannot be added to the wallet with the error "Card Device Limit". How can we resolve this?

Colombia is not yet listed as a Tap to Pay user, but it is in the process of becoming so. We are currently a group of developers at a company in Colombia working on a project to integrate Tap to Pay into our application. After reviewing Apple's documentation, my company is not certified to meet Apple's security requirements, PCI standards, or licensing requirements. However, the payment service provider we have contracted for this is in the process of obtaining the certifications, authorizations, and licenses that Apple specifies. Our team members and managers overseeing this Tap to Pay project have told us that we, as iOS developers, should integrate and use the Proximity Reader API, but we know that we, as developers, are not authorized by Apple to do so. Is the payment service provider the only one who can make this possible, enabling its use with NFC and Proximity Reader? I would like to know if the service provider will provide us with the SDK containing the Proximity Reader API for integration into the project, or if my company will have to implement the Proximity Reader API ourselves?

When I try to get a developer account, I keep getting the error "Payment approval failed". Can someone please help?

iPhone is throwing an error when starting Apple Tap to Pay transaction (other iPhones using the same merchant account working as expected) Error: Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 13.) We have tried full factory reset on the iPhone multiple times but still having the same issue. As mentioned issue is specific to one iPhone and other iPhones attached to the same merchant account have no issues taking Apple Tap to Pay transactions. Given the error is unknown / not documented, is it possible to get an explanation of what does error 13 means or what is causing it so we can troubleshoot accordingly? Full logs: readCancelled readyForTap readCancelled readyForTap userInterfaceDismissed Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 13.) readCancelled readyForTap readCancelled readyForTap readCancelled readyForTap userInterfaceDismissed Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 13.) readCancelled readyForTap userInterfaceDismissed Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 13.) readCancelled readyForTap readCancelled readyForTap updateProgress(100) updateProgress(99) updateProgress(98) updateProgress(96) updateProgress(95) updateProgress(94) updateProgress(93) updateProgress(92) updateProgress(91) updateProgress(90) updateProgress(89) updateProgress(88) updateProgress(87) updateProgress(86) updateProgress(85) updateProgress(84) updateProgress(82) updateProgress(81) updateProgress(80) updateProgress(79) updateProgress(78) updateProgress(77) updateProgress(75) updateProgress(74) updateProgress(73) updateProgress(72) updateProgress(69) updateProgress(68) updateProgress(67) updateProgress(66) updateProgress(65) updateProgress(64) updateProgress(62) updateProgress(60) updateProgress(59) updateProgress(58) updateProgress(57) updateProgress(56) updateProgress(55) updateProgress(54) updateProgress(53) updateProgress(52) updateProgress(48) updateProgress(47) updateProgress(45) updateProgress(44) updateProgress(43) updateProgress(41) updateProgress(40) updateProgress(39) updateProgress(37) updateProgress(36) updateProgress(34) updateProgress(33) updateProgress(32) updateProgress(31) updateProgress(30) updateProgress(25) updateProgress(22) updateProgress(19) updateProgress(18) updateProgress(17) updateProgress(15) updateProgress(14) updateProgress(13) updateProgress(12) updateProgress(10) updateProgress(9) updateProgress(8) updateProgress(7) updateProgress(5) updateProgress(4) updateProgress(3) Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 12.) userInterfaceDismissed readCancelled readyForTap readCancelled readyForTap userInterfaceDismissed Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 12.) readCancelled readyForTap readCancelled readyForTap readCancelled readyForTap Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 12.) userInterfaceDismissed readCancelled readyForTap notReady Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 12.) userInterfaceDismissed readCancelled readyForTap readCancelled userInterfaceDismissed Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 12.) readCancelled readyForTap Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 12.) userInterfaceDismissed readCancelled readyForTap readCancelled readyForTap userInterfaceDismissed Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 12.) readCancelled readyForTap readCancelled readyForTap readCancelled readyForTap readCancelled readyForTap Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 12.) userInterfaceDismissed readCancelled readyForTap readCancelled readyForTap userInterfaceDismissed Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 12.) readCancelled readyForTap Card reading failed due to unknown error: The operation couldn’t be completed. (ProximityReader.PaymentCardReaderSession.ReadError error 12.) userInterfaceDismissed readCancelled readyForTap readCancelled readyForTap

Hello friends, I am trying to get an Apple developer account from Şanlıurfa, Türkiye. I have tried using different cards, but I am getting an error saying the card is not approved.

Hi, We have app in which we take donations from people and send to non-profit organisations. I have read that Apple Pay can be integrated on non profit platforms to take donations, but we are middle man, we are not non profit .. we take donations, cut our platform fees and then sent to donations to non profit orgs. My question is can we integrate Apple Pay in our iOS app to take donations from apple? as we have integrated Apple Pay on the web.

I am receiving an entitlement error from stripe terminal SDK when integrating Tap to Pay from apple in the info.plist. Im hoping that someone can give me their input on my error output rather than diving into the stripe sdk to point me in the right direction of something I may have missed with entitlements. I have been approved for tap to pay entitlement and am following the instructions here from apple: https://developer.apple.com/documentation/proximityreader/setting-up-the-entitlement-for-tap-to-pay-on-iphone com.apple.developer.proximity-reader.tap-to-pay

I am trying to sign a enterprise app with provisioning profile which shows the tap to pay entitlement on Dev portal, but when downloaded on Xcode, it says the profile is missing the tap to pay capability and entitlement The capability was enabled by apple already, it was working fine until the provisioning profile got renewed.

Hi, I'm trying to integrate with Tap to Pay feature under Stripe. For this reason i need to add com.apple.developer.proximity-reader.payment.acceptance entitlement to my Identifier. I can see it under Provisioning Profile -> Enabled Capabilities. But after downloading this profile in Xcode I don't see this entitlement. What could be the reason for this discrapency?