Re: [w3c/browser-payment-api] The "data" member of PaymentMethodData doesn't seem to actually be used for anything (#338)

I'm happy to provide more background information. :-)

Although Chrome's implementation of "basic-card" is based on Autofill data in Chrome, this is done via a "payment app" that we call "Autofill Payment App." It should behave as any 3rd party payment app that's being specified in [Payment App API](https://w3c.github.io/webpayments-payment-apps-api/) spec. Once that spec is finished and implemented, any 3rd party payment app should be able to register to handle "basic-card".

Note that Android Pay integration into Chrome is also done via a "payment app" that we call "Android Pay Payment App." This is temporary until the [Android Payment Apps](https://groups.google.com/a/chromium.org/forum/#!msg/chromium-dev/fsslHD1Gf88/K2KpikS6BwAJ) support is implemented. Android Pay implementation does not have a W3C-style spec, but they do have a [tutorial](https://developers.google.com/web/fundamentals/discovery-and-monetization/payment-request/android-pay#integration_using_gateway_token).

By the way, someone from Samsung has written up a [SamsungPay Payment Method](https://maheshkk.github.io/webpayments/proposals/SamsungPay-payment-method.html) spec that can be useful to read and compare to "basic-card".

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/338#issuecomment-267153357