- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Wed, 24 Jun 2015 00:54:59 -0400
- To: public-webpayments-ig@w3.org
On 06/23/2015 09:08 PM, Mountie Lee wrote: > to realize discovery as defined at usecase, > > payee collect available payment schemes and instruments of payer. > (has privacy issue) payee provide the list of schemes and instruments > to payer. payer will DISCOVER the schemes and instruments by > comparing to existing wallet(depository, account or ...). payer will > select payment instrument for payee. > > is it correct approach? No, that approach will lead to numerous privacy violations. :) The steps are listed here: https://www.w3.org/Payments/IG/wiki/Roadmap/PaymentArchitectureWG#Scope More specifically, the payee is the one that provides the payer with the list of accepted schemes. It is then up to the payer to select from the intersection of the payee-provided payment instrument list and their (the payer's) payment instrument list. The payer is the one that discovers what payment instruments are available to them. The payee is the one that transmits what payment instruments they accept to the payer. So, to apply this to the list you have above: 1. The payee provides a list of acceptable payment instruments to the payer via the payment request. 2. The payer discovers their available payment instruments. 3. The payer selects a payment instrument that the payee accepts and that they have. Hope that helps. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: Web Payments: The Architect, the Sage, and the Moral Voice https://manu.sporny.org/2015/payments-collaboration/
Received on Wednesday, 24 June 2015 04:56:39 UTC