Adding NDEF message to Loyalty Card on Android Pay (Save To Android Pay API)
Asked Answered
D

1

6

I'm analyzing if S2AP API is able to provide a valid replacement for an existing NFC identification process through a real NFC card. The idea is to get rid of the physical cards and use virtual cards instead.

These cards got some encrypted payload that they send within the NDEF records to the NFC reader, which is ultimately used to identify the user and grant/deny access.

I've been reading a lot of information about the S2AP API and they claim that through the so called "Loyalty cards" you can add custom cards and send info to the NFC terminal whenever they are used. From the Android Pay Merchant Help: “When they make a purchase, they can easily share their loyalty info by showing the barcode on their device or by automatically sending it via NFC at your point-of-sale terminal.

I know Loyalty Cards are not intended for this kind of custom cards, but as long as the user can select a card and this card send custom NFC info to the reader, it looks like enough for my purposes.

However, there is little info out there about this kind of integration and all the Android official doc that I found reference the Barcode option, which is obviously simpler. I don’t find the way to add that NFC info (the NDEF message that the card should exchange when it is used). I’ve checked the supported fields within LoyaltyObjet and the LoyaltyClass and don’t find any related field.

Does anybody have any experience regarding this?

Edit

Eventually I got to spend some more time in this project. After a lot of effort (too much IMO) I got access to the API, not without explaining in detail my goals to the Google team several times and waiting 1-2 weeks for it. I get that Google wants to keep under control who and why use Android Pay, but some kind of dev key or sandbox to test its capabilities without the need of launching a actual commercial project would be really appreciated. Anyway, this is another topic.

Although I didn't test the API in depth, what I understood from all these conversations with the Google team is that this API is only intended for commercial loyalty programs and it does not seem to be any chance of using it other way, so it does not fit my needs. Anyway, from the little time I could spend on it, I didn't find a way to load custom NFC data either.

Destructive answered 9/10, 2017 at 14:0 Comment(2)
Hea @Destructive did you get any info on this. I am struggling to do the same. I have a Physical Loyalty card and I want to create a virtual card for the same. For which I need to figure out what NDEF message does Android Pay send for such card and mimic the same in my app.Freeloader
Hi @SagarMody, still no luck. The project got stuck by the moment, but if I get to continue it and get some extra info regarding this, I'll let you know. I'll be glad if you share your progress too. Regards!Destructive
L
1

Unfortunately as you have already found out, you need to apply for early access here. How to use NFC reader terminals to read Smart Tap data is under NDA.

You can update passes with the REST API. Each pass returns encrypted payloads with a unique ID. Here is a video of reading Apple and Google Pay passes: PassNinja Instagram

Disclosure: I work for Flomio. The company behind PassNinja.

Labe answered 12/6, 2018 at 12:0 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.