Goodmorning, I want to request NFC & SE Platform functionality but the following link does not seem to work for me. https://developer.apple.com/contact/request/nfc-se-platform It displays the following message: You must be the Account Holder of an Apple Developer Program for Organizations or an Apple Developer Enterprise Program to view this page. Visit account But in my membership details, I am the account holder as seen in the image below. Does someone know how this might happen?

Now that we are to move away from designing apps for specific devices and fixed orientations, and to instead target “a dynamic range of sizes and aspect ratios”, what does that mean for Apple Pay and CoreNFC flows? For layouts that show users where to tap the NFC tag device to the phone (approximate location where the NFC hardware is located in the phone), how should placement instructions be updated? For reference to all, here's Apple's design, that contains a dot cloud, showing the general tap area: https://www.apple.com/business/tap-to-pay-on-iphone/ Wondering if Apple could provide any updated examples (especially for CoreNFC)? Thanks for the help!

Hello Team, We are currently implementing a digital membership solution across our gym facilities, allowing members to add their access cards to Apple Wallet. In this regard, we would like to request enablement of NFC capability for Wallet passes associated with our Apple Developer account. Our setup includes NFC-enabled access control hardware integrated with our gym management system, and NFC support is required to issue and utilize digital membership cards. At present, we only have a standard Pass Type ID Certificate in our developer account. However, we understand that NFC-enabled Wallet passes require a Pass Type ID Certificate with NFC capability. We would appreciate your guidance on how we can enable or obtain a Pass Type ID Certificate with NFC support in our Apple Developer account. Looking forward to your support.

Great Morning, We would like to request the entitlement: com.apple.developer.passkit.pass-presentation-suppression Use Case: Our application provides NFC-based mobile key access for hotel guests.  When the device is presented to an NFC reader (door lock), iOS automatically  launches Apple Wallet, interrupting the in-app unlock experience. We need to suppress Wallet presentation while the app is in the foreground to allow a seamless “tap-to-unlock” experience. Please let us know if additional information or agreements are required. Thank you.

We are working on an HCE application following your documentation. Almost everything is working fine except that we encounter a crash when using CardSession.init() method. We are calling CardSession.isEligible() before CardSession.init(). This crash is random and affects very few user and we did not find a way yet to reproduce this crash on our side. Our theory is CardSession.isEligible() is doing thing under the hood and make CardSession.init() cause a crash, but that just our theory. Here are some stacks : CoreNFC/NFCCardSession.swift:431: Fatal error: Previous session exists 0 libswiftCore.dylib   0x000000019ed73800 _assertionFailure(_:_:file:line:flags:) + 168 (AssertCommon.swift:171) 1 CoreNFC   0x000000025b99f630 NFCCardSession.startSession() + 296 (NFCCardSession.swift:431) 2 CoreNFC   0x000000025b994771 CardSession.begin() + 1 (CardSession.swift:337) 3 CoreNFC   0x000000025b99427d CardSession.init() + 1 (CardSession.swift:320) 4 Paiement Mobile   0x000000010197f345 HceNativeSDK.startCardSession() + 1

We have enabled the Host Card Emulation (HCE) capability for our app and successfully implemented and tested the functionality during development. When running the app directly from Xcode, HCE-related flows work as expected. However, we are observing different behavior in the distributed build. In particular, the following check consistently evaluates to false: guard await CardSession.isEligible else { return } After distributing the app via TestFlight, HCE functionality is not available for external testers. The CardSession.isEligible property always returns false, even when tested on supported devices and in supported regions. We are using the same bundle identifier for both development and distribution builds, and the provisioning profiles include the required capability. Could you please clarify the following: Are there any additional entitlements, approvals, or configuration steps required for HCE to function in TestFlight or distribution builds? Are there known region, device, or account-related restrictions that could cause CardSession.isEligible to return false outside the development environment? Is there any difference in behavior between development-signed and distribution-signed builds for this capability?

Hi, I have the NFC &SE entitlement but still not able to read a pass from the apple wallet on another iphone. The logs show that the NFCVASReader session is initialised and the readerSessionDidBecomeActive — session is live, waiting for pass tap, but nothing is read. The pass is nfc enabled with correct encryption key. It feels like I am still missing some kind of entitlement to read VAS from passes - could anyone advise please?

Hello I am implementing an NFC Reader session in my app, and presenting the bottom sheet works completely fine. However, I am facing an issue with screen rotation. If I rotate the device while the NFC bottom sheet is active, the sheet does not adapt or resize according to the new screen orientation. Is there a way to force the NFC bottom sheet to update its layout or fix this rotation issue?Any help or workarounds would be greatly appreciated. Thanks!

Hello I am experiencing a layout issue where UI components overlap in a bottom sheet during screen rotation while an NFC Reader session is active. The NFC Reader session initializes and displays the bottom sheet properly. However, if the device is rotated while this sheet is on screen, the layout breaks, and elements appear overlapped. I have attached a sample image demonstrating this rendering issue. Is there a known workaround to fix this layout distortion or force a proper layout update during an active NFC session?Any insights or suggestions would be greatly appreciated. Thanks!

I developed an app that uses the Core NFC framework to read tags. The feature works correctly on iOS 18 and earlier versions, but after upgrading to iOS 26, it stopped working. Details: Entitlement Near Field Communication Tag Reader Session Formats D2760000850101 D2760000850101 Info.Plist com.apple.developer.nfc.readersession.iso7816.select-identifiers D2760000850101 com.apple.developer.nfc.readersession.felica.systemcodes 12FC Privacy - NFC Scan Usage Description Signing and Capabilities: Near Field Communicating Tag Reading [Eanbled] My Sample Code Is: class NFCManager: NSObject, NFCTagReaderSessionDelegate { private var nfcSession: NFCTagReaderSession? let isConnectionNeeded = false func startNFCSession() { guard NFCTagReaderSession.readingAvailable else { // NFC is not available on this device. return } nfcSession = NFCTagReaderSession(pollingOption: [.iso14443, .iso15693, .iso18092], delegate: self) nfcSession?.begin() } func stopNFCSession() { nfcSession?.invalidate() } // MARK: - NFCTagReaderSessionDelegate Methods func tagReaderSessionDidBecomeActive(_ session: NFCTagReaderSession) { print("tagReaderSessionDidBecomeActive") } func tagReaderSession(_ session: NFCTagReaderSession, didInvalidateWithError error: Error) { print("didInvalidateWithError --\(error)") } func tagReaderSession(_ session: NFCTagReaderSession, didDetect tags: [NFCTag]) { print("didDetect: Tag Detected --\(tags)") } } The above code works fine on iOS 18 and earlier versions for detecting tags. Please let me know if I’m missing anything. Please help me to resolve the issue in iOS 26

We are developing a non-custodial cryptocurrency wallet app with the following characteristics: Architecture: Users hold their own private keys at all times (we never custody any assets). The app includes identity credential verification: KYC-verified identity data (Verifiable Credentials / DID-based) is exchanged between the payer's iPhone and a counterparty device for identity verification purposes. NFCTagReaderSession is used only to exchange identity credential data via our proprietary, non-payment ISO 7816 AID with the counterparty device. Cryptocurrency transactions are submitted entirely over the internet (blockchain RPC), completely independent of the NFC session. NFC is NOT used to: Transmit cryptocurrency or payment instructions. Interact with any EMV payment AID or Secure Element. Replace or emulate Apple Pay or any payment card. Jurisdiction & licensing context: The app is being developed by a Japanese company for initial launch in Japan. While this question is posted from an individual Developer account for inquiry purposes, the app itself will be submitted under an appropriate Organization Developer account of the operating company, in compliance with Guideline 3.1.5(a)(ii). We are working with Japanese legal counsel to obtain any applicable Japanese financial-services license (e.g., 電子決済手段・暗号資産サービス仲介業 / Electronic Payment Instruments and Crypto-Asset Service Intermediary Business under the 2023-amended 資金決済法 / Payment Services Act) prior to App Store submission, and a written legal opinion will accompany the submission. We are not seeking to qualify as a 暗号資産交換業 (crypto-asset exchange) or 資金移動業 (funds transfer service operator), as our non-custodial design is intended to fall outside those categories under Japanese law. Question: Under Guideline 3.1.5, does a non-custodial wallet that uses NFCTagReaderSession solely for identity credential data exchange (not for transmitting cryptocurrency or payment instructions over NFC) fall under the "Wallets" sub-category — requiring an Organization Developer account only — or does NFC involvement for identity verification shift it toward a sub-category requiring additional licensing, entitlements, or financial institution credentials?

Hi, I am trying to build a very simple iOS app in Xcode that starts an NFCNDEFReaderSession when I press a button. My goal right now is only to verify that the NFC reading process starts correctly on a real iPhone. I am not trying to publish the app on the App Store. When I try to start the session, I get this error in the console: -[NFCHardwareManager areFeaturesSupported:outError:]:435 XPC Error: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.nfcd.service.corenfc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.nfcd.service.corenfc was invalidated: Connection init failed at lookup with error 159 - Sandbox restriction.} and then my app reports that NFC is not available on this device. Important details: I added Near Field Communication Tag Reading in Signing & Capabilities. I added the NFC privacy usage description in the target settings. I am using automatic signing. I am not using an Apple Developer Program paid account. I am using a Personal Team / free account. I should also mention that I am not experienced with Swift/iOS development, so I may be missing something basic in the setup. My question is: Is this expected when using a Personal Team / free account, or is there some configuration issue I should still check? I am happy to provide any additional information needed

I've added NFC support for my app. So, my UIRequiredDeviceCapabilities were extended from "armv7" to "armv7 nfc". This means I've prevented this application from running on devices supported by previous versions. Now I've received a message from Apple: ITMS-90109: This bundle is invalid - The key UIRequiredDeviceCapabilities in the Info.plist may not contain values that would prevent this application from running on devices that were supported by previous versions. What is the right way to add new functions?

Hi everyone, I'm looking for clarity on the NFC HCE entitlement process for third-party apps in the EEA. I've built an alternative client for Milan's public transport app (ATM Milano) on Android by reverse engineering the original app. It offers the same core functionality(users still need a valid transit subscription) just with a different UI and better UX. I'd now like to port it to iOS. According to Apple's documentation, NFC HCE was opened to third parties in the EEA starting with iOS 17.4. However, the API requires an entitlement from Apple. I have a few questions: Is the entitlement required regardless of distribution method? Even if I distribute through a third-party marketplace like AltStore PAL rather than the App Store, do I still need Apple to grant the HCE entitlement? Are third-party/alternative clients eligible for the entitlement? My app isn't a competing transit provider, it's an alternative frontend for an existing service. Users must hold a valid subscription with the official provider. Is there anything in the entitlement criteria that would disqualify this kind of app? What's the correct process to apply?Developer Support directed me here, so I'm hoping someone from Apple engineering or someone who has gone through the process can share the steps. Thanks!

Is it possible to read a custom, non-payment, ISO7816 AID on a multi-application smartcard that also has an active payment AID? I guess Apple Wallet may auto-detect the payment scheme and open, but this could be prevented if my app was already running in the foreground and scanning for the custom AID?

Hello, I would like to discuss the behavior of the expiration of NFCPresentmentIntentAssertion (test in iOS 18.5). In the documentation we have : The intent assertion expires if any of the following occur: The intent assertion object deinitializes Your app goes into the background 15 seconds elapse BUT; in fact ; only the 1st rule is applied. The expiration seems to be random after the usage of CardSession and that's difficult to give to the user a good experience. Has someone faced the same kind of issue; or can give an explanation? Regards, François

Hi, I’m implementing ePassport reading in an iOS app using a third-party KYC identity verification SDK (the SDK handles the NFC logic internally). Before adding any specific AID, the NFC session would start normally and iOS showed the system popup asking the user to hold the passport near the device. However, the passport was never read , the session just stayed there with no progress or data returned. I then tried enabling the ICAO ePassport AID: A0000002471001 After adding this, the build failed with the following signing error: Provisioning profile "iOS Team Provisioning Profile: com.sandrotbilisi.DigitalCurrency" doesn't include the com.apple.developer.nfc.readersession.iso7816.select-identifiers entitlement. Has anyone encountered this behavior when working with ePassports? Do I need special entitlement approval from Apple for this AID? Thank you.

We have NFC capabilties enabled for our app ID - com.uob.mightyvn but our minimum deployment target is 15.0. We do not have an option deselect PACE from provisioning profile. Hence, the validation is failed for IPA. Invalid entitlement for core nfc framework. The sdk version '18.2' and min OS version '15.0' are not compatible for the entitlement 'com.apple.developer.nfc.readersession.formats' because 'NDEF is disallowed'

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.

Provisioning profile doesn't match the entitlements file's value for the com.apple.developer.nfc.hce.iso7816.select-identifier-prefixes entitlement. Although when we created the request, we added a list of AIDs which is the same as the list registered in Inof.plist <key>com.apple.developer.nfc.hce.iso7816.select-identifier-prefixes</key> <array> <string>XXXXXX</string> <string>XXXXXX</string> <string>XXXXXX</string> </array> How can we get a better message of diffs between them?