


Whereas the Mifare DESFire tag is a much more flexible implementation of the lower level NFC standards. So in General this Apple NFC feature allows you to provide some extra info to Apple Pay's Wallet App so it responds with some extra custom information to a NFC reader that conforms to Apple's Pay standards. So Banks, Visa, MasterCard, etc and the NDEF Standard all have their own AID numbers, so I guess that Apple also have an AID for their Value Added Services Protocol.Ī Mifare DESFire tag is also a NFC Forums Type 4 Tag and can be programmed to respond to the NDEF AID and other custom AID's though I'm not sure it can be programmed to be able to respond to the AID used for Bank cards or to respond to Apple's Value Added Services Protocol. So Contactless bank cards conform the the NFC Forums Type 4 Specification, the Type 4 specification is low level and defines a method interact with a Higher level protocol beginning with the selection of an AID (Application ID), how you interact act with the card after the AID selection is up to each Application Specification. Use a Base64 encoded X.509 SubjectPublicKeyInfo structure containing a ECDH public key for group P256. The public encryption key used by the Value Added Services protocol. Messages longer than 64 bytes are truncated by the system.ĮncryptionPublicKey, string, Optional. STOP WASTING MONEY ON PAPER, PLASTIC AND POSTAGE COSTS. And say hello to digital loyalty cards in your customers' mobile wallet application. The payload to be transmitted to the Apple Pay terminal. Say goodbye to paper coupons, plastic membership cards and junk email. I don't think using NFC Passkit allows you to behave like a Mifare DESfire Tag, this seems very limited to "Reward Card information" it just provides some extra info to a card reader that knows how to send Apple's Value Added Services Protocol over NFC (Not all card readers/POS terminals can do this)
