- From: Dave Raggett <dsr@w3.org>
- Date: Wed, 23 Apr 2014 17:17:26 +0100
- To: Kumar McMillan <kmcmillan@mozilla.com>, Manu Sporny <msporny@digitalbazaar.com>
- CC: public-webpayments@w3.org
On 23/04/14 16:43, Kumar McMillan wrote: > On Apr 22, 2014, at 8:17 PM, Manu Sporny <msporny@digitalbazaar.com> wrote: >> 4. Standardize payment initiation: >> https://web-payments.org/specs/source/web-commerce-api/ >> 5. Standardize digital receipts: >> https://web-payments.org/specs/source/web-commerce/ > To specifically solve the nascar problem I think you only need these two things ^ > > A web API (or JavaScript shim) just needs to know how to invoke a compliant payment provider and how to verify the purchase. Each payment provider could still handle identity / credentials themselves. > > -Kumar > How does the user can choose between payment solutions? This is why it may be better for the same interface to bind to the user's choice of wallet (there could be more than one), and leave it to the wallet to provide the UX for for the user to pick her preferred payment solution for the current transaction. This means we also need to discuss how to allow the user to register and unregister wallets and payment solutions, and to allow for both locally installed and remotely hosted implementations. -- Dave Raggett <dsr@w3.org> http://www.w3.org/People/Raggett
Received on Wednesday, 23 April 2014 16:18:01 UTC