I have the same problem. My application ID indicates that the "Tap to Pay on iPhone" option is enabled on the Apple Developer Portal (this feature also appears in the "Signature & Capabilities" tab of Xcode), and the entitlement file is correctly provided in its project bundle. In development/debug mode, the functionality is available and operational: my application can perform Tap-to-Pay payment simulations via the Stripe PSP, using the Stripe Terminal SDK for SwiftUI. However, Xcode reports that the provisioning profile defined with this application ID for distribution on the App Store and loaded into Xcode does not include the com.apple.developer.proximity-reader.payment.acceptance authorization, even though all configuration settings comply with Apple's documentation guidelines. I've regenerated the profile several times without success (and when I use "Automatically Manage Signing" in Xcode, attempting to distribute an archive to Release Testing (TestFlight) generates an error message stating that the application ID doesn't include the "Tap to Pay on iPhone" capability). This inconsistency suggests that generating a provisioning profile for distribution on the App Store isn't enough to actually produce an appropriate entitlement. Why? Apple Support hasn't yet helped me understand or resolve this issue. I've requested a non-fake entitlement, but I still haven't received a response. On this forum, a DTS engineer suggests that the suitable entitlement can be obtained through a "confirmation email." I'd like to know about such a procedure.