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

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

Hi everyone! Our Tap to Pay on iPhone integration using the ProximityReader framework is experiencing widespread failures with error code 2016 ("Unexpected reader error") when attempting to prepare the reader for contactless payment sessions. The issue started on August 9, 2026 and is affecting multiple device models across iOS 26.x versions. Error Details: Framework: ProximityReader Error: "Unexpected reader error (2016)" Operation: Session activation during payment flow (ProximityReader.prepare()) Result: Reader cannot be prepared; payment sessions fail immediately Questions: What does ProximityReader error code 2016 specifically indicate? Is there a known issue with the ProximityReader framework on iOS 26.5.2 / 26.6 / 27.0? Many thanks Icaro.

Hi all, I recently requested the Tap to Pay on iPhone entitlement for my app and was approved by Apple. The approval email included a link to download the marketing guide and branding toolkit (logos, brand guidelines, UI assets). Unfortunately I didn't download the toolkit at the time, and now when I open the link it says it has expired. A couple of questions: Is there a way to get a fresh download link for the Tap to Pay on iPhone marketing/branding toolkit? Is it available anywhere publicly, or does it have to be re-sent by Apple? To be clear — my understanding is that the entitlement itself is already attached to my account and I do not need to re-request it just to get the toolkit again. Can anyone confirm that re-requesting the entitlement is unnecessary (and not something I should do)? I'd rather not resubmit the entitlement request and risk disrupting an approval I already have. Just trying to recover the branding assets. Has anyone run into this? Should I contact Developer Program Support to have the toolkit link re-sent, or is there a self-serve resource page? Thanks in advance.

Hello, We operate an app that grants users credits after a successful in-app purchase. Our current purchase-processing flow is as follows: A user completes an in-app purchase. Our app or server receives the purchase-related information. Our server sends a transaction verification request to the App Store Server API. After verifying the transaction, our service marks the purchase as completed and grants credits to the user. However, we are intermittently experiencing connection timeouts and unidentified server errors when retrieving transaction information through the App Store Server API. One example of the timeout error is: HTTPSConnectionPool( host='api.storekit.itunes.apple.com', port=443 ): Max retries exceeded with url: /inApps/v1/transactions/330003085668123 Caused by ConnectTimeoutError: Connection to api.storekit.itunes.apple.com timed out. (connect timeout=3) We also intermittently receive the following error response: { "code": 5000001, "message": "An unknown error occurred. Please try again." } When this issue occurs, the payment may have been successfully completed through the App Store, but our server is unable to immediately verify the transaction. As a result, the user may not receive the purchased credits in our app. We would appreciate your guidance on the following questions: What are the common causes of connection timeouts or error code 5000001 when calling /inApps/v1/transactions/{transactionId}? What retry strategy does Apple recommend when these errors occur? Please advise whether there are recommended timeout values, retry limits, or exponential backoff parameters. Is there another reliable method to confirm a completed purchase when the transaction lookup API does not return a response immediately? Does Apple recommend using App Store Server Notifications V2 to process completed purchases asynchronously rather than relying solely on an immediate transaction or receipt verification response? For an app that grants consumable digital credits, which value should be used as the primary identifier for purchase completion and duplicate-grant prevention: transactionId, originalTransactionId, or the information contained in signedTransactionInfo? When a temporary API error occurs, is it recommended to store the purchase as pending and perform transaction verification again from our server until a definitive result is received? We would appreciate Apple’s recommended implementation approach for reliable transaction verification and recovery, particularly to prevent cases in which a payment is successfully completed but the purchased credits are not granted due to a temporary API communication error. Thank you.

Has anyone run into an expired access grant on Apple Business Register for "Tap to Pay on iPhone for Payment Providers"? Context: I work on a Tap to Pay on iPhone integration at a payment service provider. I was granted access to the PSP section of Apple Business Register roughly six months ago and had been using it without issue. Steps to reproduce: Sign in to register.apple.com with the Apple Account that originally received access. Open the Tap to Pay on iPhone for Payment Providers section. A dialog appears: "Your access to the connection expired. Contact your organization admin to renew your access for Tap to Pay on iPhone for Payment Providers." The dialog only has an OK button. Dismissing it leaves a blank page — there is no renewal link or request option anywhere in the interface. What I've already ruled out: Signed in with the correct Apple Account (not a personal one) Full sign out and sign back in Tested in a different browser with extensions disabled Same result every time. What I'm hoping to learn from anyone who's been through this: Was your Account Holder able to re-grant access to a member directly inside Apple Business Register? If so, roughly where in the interface? Or did it require Apple to restore it on their side — and how long did that take? Is the access window a fixed six months for everyone, and does Apple send any warning before it lapses? I've opened a case with Apple Developer Support in parallel, but I'd like to hear whether others have hit the same wall and what actually resolved it. Thanks.

Hi Apple Support, After further investigation, we found that although we submitted a request for the Tap to Pay on iPhone entitlement, we never received any confirmation email afterward. At the moment, we are unable to upload our Tap to Pay on iPhone application to TestFlight, and we are wondering if the missing confirmation email may indicate that the entitlement request process was not completed successfully. Could you please advise whether there are any additional steps we need to take or whether we should submit the request again? Additionally, could you clarify what confirmation email or approval notification we should expect to receive after submitting a Tap to Pay on iPhone entitlement request? Any guidance would be greatly appreciated. Thank you for your support.

I'm trying to distribute our app through TestFlight's internal testing for our QA Analysts to run some tests in the non-production environment. In this page: https://developer.apple.com/documentation/storekit/testing-in-app-purchases-with-sandbox Is stated that: "Apps that you download from TestFlight always run in the sandbox environment." But we ran into the issue from the ProximityReaderAPI requesting a Sandbox account anyway (This token requires a sandbox test account from your Apple Developer account). Is that not the case for Tap To Pay on iPhone?

Hi everyone, I’m currently implementing Tap to Pay on iPhone following Apple’s official documentation. I’ve completed all the required configurations (entitlements, capabilities, merchant setup, etc.) on the Apple Developer portal. However, when I archive the app and attempt to upload it to TestFlight, I receive the following error: "Profile doesn't support Tap to Pay on iPhone. Profile doesn't include the com.apple.developer.proximity-reader.payment.acceptance entitlement." From what I understand, this seems related to the provisioning profile not including the required entitlement, even though I believe everything has been configured correctly. I have already tried: Regenerating provisioning profiles Verifying App ID capabilities Ensuring the correct entitlements are added in the project But the issue still persists. Has anyone encountered this issue before? Is there any additional approval step required from Apple to enable the Tap to Pay entitlement? I’d really appreciate any advice or experience you can share. Thanks in advance!

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.

Trying to figure out how to send btc, eth, etc, phone to phone. Square app allows for the phone to turn into a payment terminal for fiat currencies and payment systems. the data encryption logic and sending p2p is similar but can that functionality be enabled for alternative purposes i.e. sending crypto phone to phone (designated wallet on one phone to designated wallet on another)?

StoreKit error:Storekit has failed to fetch this product. We implemented in-app purchases using StoreKit2. During testing, we were able to make purchases smoothly in various ways without any issues. However, the reviewers encountered this error, and it happened 100% of the time.

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?

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 I am developing an iOS app and would like to read an EMV card that is issued by me and want my customers to tap to activate simply to validate the possession of the card at the time of activation. Any suggestions welcome on how can i achieve this using either NFC Framework or secure elements

Hello, We are trying to add tap to pay to our app built with react native through expo. When running the command eas build --profile development --platform ios --local I get this error: But when I open the project in XCode I can see that the Tap to Pay capability is enabled: And when I look at my profiles in the apple developer platform, I can see that the profile the error mentioned above has the Tap to Pay entitlement contrary to what it tells me: I don't understand what's happening, can somebody help me? I'm here if you need more informations. P.S.: not sure if it's relevant but, the way we did thing with expo, we have a different bundle identifier and app name according to which environment we are building for (development/preview/production)

大家好！应用程序提交审请时有个问题请教 （非消耗型产品）提示 购卖商品 ID不存在 应该如何解决

Trying to enable TTP and we're a PSP, from everything I'm reading I'm supposed to provide a reader token to our merchants but can't find anything on it. How do I generate this token? All I know is that it's a jwt and there's some header requirements. Documentation mentions the jwt should include a unique merchant identifier. My question is what does the payload and header look like when signing the jwt?