5 Replies
      Latest reply on May 9, 2019 5:31 AM by dzentec
      Deepz Level 1 Level 1 (0 points)

        As part of our mobile app for Electrical Vehicle (EV) charging, we are creating a NFC enabled prepaid reward card. Can you help us in understanding following data flow so that we can use this pass in our application in conjunction with charge station NFC reader and our backend server

        1. We are able to create the Pass and add it in Apple Wallet. However the NFC reader is not able to read this pass. Is there anything else required to be done in order to enable this card for NFC data exchange?

        2. Once exchanged via NFC, the reader is expected to send this data to our server for validation. We are unable to find any documentation on apple developer site on this data exchange front. Can you help us in understanding following

        2.1 What data is exchanged over NFC for our pass? We are hoping data from pass.json is passed over NFC to the reader. Can we get a reference of which all data is exchanged over NFC? Is the exchange data encrypted?

        2.2 As part of our use case, NFC reader is expected to pass this data to our backend server for validation. We are hoping that if any of the data from pass.json is exchanged over NFC than that data we shall be able to use to validate it on our backend. Can you please provide any documentation pointers for us to get this done.

        2.3 After reading the pass data over NFC, is NFC reader required to talk to apple server for further decryption of data received via NFC?

        • Re: NFC enabled prepaid reward card
          FlonSolutions Level 1 Level 1 (0 points)

          Did you apply for and receive an NFC-certificate account upgrade?

          If not, you won't be able to create passes that will load into Apple Wallet and interact with NFC terminals.

           

          Have a look at the following documentation on NFC passes in the Wallet Developer Guide.

           

          The NFC-enabled pass will not function without a terminal compatible with the Apple value added services protocol. Each NFC-enabled pass contains a 64-byte data element which can identify a customer. This data element can represent a rewards card for a loyalty program, a stored value card, or a ticket. Apple Wallet only transmits this data element to an NFC-enabled terminal that is compatible with the Apple value added services protocol.

           

          NFC-Enabled Pass Keys

          NFC-enabled pass keys support sending reward card information as part of an Apple Pay transaction.

          Important: NFC-enabled pass keys are only supported in passes that contain an Enhanced Passbook/NFC certificate. For more information, contact merchant support at https://developer.apple.com/contact/passkit/.

           

          Passes can send reward card information to a terminal as part of an Apple Pay transaction. This feature requires a payment terminal that supports NFC-entitled passes. Specifically, the terminal must implement the Value Added Services Protocol.

          Passes provide the required information using the nfc key. The value of this key is a dictionary containing the keys described in NFC Dictionary Keys. This functionality allows passes to act as the user’s credentials in the context of the NFC Value Added Service Protocol. It is available only for storeCard style passes.

          Key name

          Type

          Description

          nfc

          nfc dictionary

          Optional. Information used for Value Added Service Protocol transactions. For this dictionary’s keys, see NFC Dictionary Keys.

          Available in iOS 9.0.

           

           

          NFC Dictionary Keys

          Information about the NFC payload passed to an Apple Pay terminal.

          Key name

          Type

          Description

          message

          string

          Required. The payload to be transmitted to the Apple Pay terminal. Must be 64 bytes or less. Messages longer than 64 bytes are truncated by the system.

          encryptionPublicKey

          string

          Optional. The public encryption key used by the Value Added Services protocol. Use a Base64 encoded X.509 SubjectPublicKeyInfo structure containing a ECDH public key for group P256.