Hello Apple Developer Team/Community,
I am working on developing an Apple Wallet pass with NFC functionality for our electric vehicle (EV) charging stations. The goal is to enable a "tap-to-start charging" feature, providing a seamless and efficient experience for users. However, my request for an NFC certificate to enable this functionality has been rejected.
Here is a summary of my use case and actions taken so far:
1. Use Case:
-
The Wallet pass will allow users to initiate charging sessions by tapping their iPhones or Apple Watches on the EV charger.
-
This feature aims to simplify the process by eliminating the need for additional apps, physical cards, or manual inputs.
-
It enhances accessibility and aligns with Apple’s goals of providing users with secure and convenient solutions.
2. Steps Taken:
-
Submitted the NFC certificate request with a detailed explanation of the functionality.
-
Included diagrams and supporting documents demonstrating the workflow and system readiness.
-
Received a rejection without clear guidance on how to address the issue.
3. Technical Readiness:
-
Our backend is fully prepared to support NFC passes, including secure processing of tap events and payload encryption.
-
The Wallet pass has been configured to include the nfc field with the required encryptionPublicKey.
Request for Assistance:
-
Could you provide guidance on improving my application to meet Apple’s criteria for NFC certificates?
-
Are there specific requirements or examples of successful NFC-enabled Wallet pass applications that I can use as a reference?
-
If anyone has faced a similar rejection, what steps did you take to get approval?
Additional Information:
-
Use case: EV charging stations
-
NFC functionality: Tap-to-start charging session
-
Current implementation: Pass is functional without NFC but requires NFC for seamless operation.
Any advice or resources to help resolve this issue would be greatly appreciated. Thank you for your time and support.
Best regards,
DeveloperSquillion