- From: Manu Sporny <notifications@github.com>
- Date: Sun, 13 Mar 2016 17:39:46 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
Received on Monday, 14 March 2016 00:40:14 UTC
Migrating issue from https://github.com/w3c/webpayments/issues/15: When a user registers a new payment instrument, how is that payment instrument shared between different browser brands? For example, if I register a Visa debit card issued by my bank in Google Chrome on my laptop, when I go to purchase something using my mobile phone, is that same debit card available to me via my Firefox web browser (assuming I've authenticated in some way with both browsers)? There are a variety of choices here, in order of easiest to implement to hardest to implement: 1. There is no sharing mechanism 2. There is a unified payment instrument export mechanism 3. There is a storage and discovery mechanism that all browsers use to import data from other browsers I assert that the last bullet point is what we should strive for, but we may need to take baby steps to get there. In any case, we should implement the API as if the third item existed and figure out a way to polyfill our way there. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/38
Received on Monday, 14 March 2016 00:40:14 UTC