> To fix this, probably what is necessary is to insert a step into https://w3c.github.io/browser-payment-api/#user-accepts-the-payment-request-algorithm which passes data to some algorithm defined in each payment method specification
This should be ideal and providing an example would be also an interesting addition. It took a bit for me, until I read the [integration guide with Android Pay](https://developers.google.com/web/fundamentals/discovery-and-monetization/payment-request/android-pay), to realise that `data` served a purpose.
Another issue related to this is the fact that the `data` member affects all the payment method ids in the `supportedMethods` array. What is the use case for this? I would rather expect a pair `{ id, data } for each _paymentMethod_.
I'm not saying
--
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-267307242
Received on Thursday, 15 December 2016 11:38:00 UTC