- From: Adrian Hope-Bailie <adrian@hopebailie.com>
- Date: Thu, 16 Jul 2015 21:46:32 -0700
- To: Mountie Lee <mountie@paygate.net>
- Cc: "public-webpayments-ig@w3.org" <public-webpayments-ig@w3.org>
- Message-ID: <CA+eFz_L+JYP3vX3qoZAe4GwUdVYsH3oEdmkMJo8GWCtNyOAUdQ@mail.gmail.com>
We do cater for this scenario. The intention is for the standard to support wallets that may be aggregators of other wallets. For every payment initiation request be require a single service to co-ordinate the discovery of payment instruments (even if this means discovering them from multiple wallets). For this reason a user must have a primary wallet and we would prefer this functionality to not be built into the browser otherwise we make the browser a gatekeeper for the standard. The proposal today is that the browser is just a proxy for the messages between the payee and the payer's wallet (we don't talk about a payee wallet, just a payee payment service provider). The messages from the payee are proxied by the browser to the primary wallet and this service is responsible for discovering all of the payer's available payment instruments in this and any other wallets that the primary wallet is aware of. I don't understand your point about client-side wallets being discovered by the payee. 1. Wallets are not discovered. Payment instruments are discovered from the wallet(s) of the payer. 2. Whether the wallet is client side (do you mean a native application/app on the payer's client?) or server side (do you mean hosted on the Web?) they will always be the payer's wallet. 3. Discovery is a capability of the wallet service. It can easily enumerate the payment instruments that have been registered with it but it may also call out to other secondary wallet services to discover the payment instruments that they hold. Do you have a use case in mind that would clarify this requirement because at this point I think we have it covered by the current charter? On 16 July 2015 at 21:24, Mountie Lee <mountie@paygate.net> wrote: > Hi. > > when I review Charter > it is describing discovery of payment schemes and selection of payment > instruments. > > it seams that discovery and selection are under single wallet. > > but normally we can think user will have multiple wallets. (maybe user > will choose primary wallet) > > I think the charter is not touching the case of multiple wallets. > > if we think discovery for multiple wallets, the operation and actors will > be totally different by the location of wallet (client side wallet can be > discovered by payee, server side wallet can be discovered by payer) > > how can I understand this scenario? > > regards > mountie > -- > Mountie Lee > > PayGate > CTO, CISSP > Tel : +82 2 2140 2700 > E-Mail : mountie@paygate.net > >
Received on Friday, 17 July 2015 04:47:05 UTC