Re: Multiple Wallets

I have thought more about multiple wallets.

I can image it will be similar to setting primary search engine at browser.
also we can think the default wallet.

comparing to search engine and wallet,
 * number of search engines are less than wallet's
 * search engine is for enhancing user experience but wallet is part of
infrastructure.
 * default search engine is set by browser vendor. but default wallet by
browser vendor? not good for me.

I tried to add discovery of wallets in my diagram (diagram just for push
payment)

http://bit.ly/1UaKjB6
[image: Inline image 2]



On Sun, Jul 19, 2015 at 1:25 AM, Nick Shearer <nshearer@apple.com> wrote:

>
> On Jul 17, 2015, at 8:14 PM, Mountie Lee <mountie@paygate.net> wrote:
>
> I image following scenario.
>
> payee know the differences of wallet services.
> UK based payee found consumers were trying to pay with ApplePay but the
> customer is from Japan.
> payee may know the Apple Pay is not available for Japanese customer.
> to finish checkout successfully
> payee will recommend to use different wallet to select another payment
> scheme and instrument.
>
>
> I think this is another wallet terminology issue. If you use Adrian’s
> terminology, technologies like Apple Pay, PayPa, Venmo, and the like are
> both wallets *and* payment instruments. For example, PayPal is typically
> backed by a user’s credit or debit cards, so it’s something of a wallet.
> But just because you can process a Visa or MasterCard payment doesn’t mean
> you can process a PayPal payment - it’s also a discreet payment instrument.
>
>
> without discovery of wallet services, customer will do something manually
> or by browser support.
> with discovery of wallet service, customer will switch wallet easily by
> browser support.
>
> I'm not just saying about "discovery of wallet services"
>
> when I map the charter to real world example,
> the case of multiple wallets is quite unclear to understand.
>
>
> I agree. The closest real world example I could think of it where you have
> a debit card that is backed by multiple funding sources you can select
> between at point of payment (e.g, a checking and savings account). But this
> isn’t particularly common.
>
>
> regards.
> mountie.
>
>
>
> On Sat, Jul 18, 2015 at 11:13 AM, Nick Shearer <nshearer@apple.com> wrote:
>
>>
>> On Jul 17, 2015, at 6:43 PM, Mountie Lee <mountie@paygate.net> wrote:
>>
>> Hi.
>>
>> I believe followings are existing multiple wallet services
>> ApplePay, SamsungPay, Google Wallet, PayPal, Alipay, Bitcoin Wallet...
>>
>> Payment Scheme is group of payment instruments like Credit Card(choice of
>> card brands), Cash with Escrow(choice of banks), Cryptocurrecy Payment...
>>
>> card payment will be available via multiple wallet services.
>>
>> if all those wallet services keep standard interface,
>> how payee recommend to payer using which wallet service?
>>
>>
>> To reiterate Adrian’s point, why would the payee want to recommend a
>> specific wallet? The payee wants to recommend payment instruments.
>>
>> how payer discover multiple wallet services?
>>
>> still it is not easy to image the whole process.
>>
>> best regards
>> mountie.
>>
>>
>>
>> On Sat, Jul 18, 2015 at 2:09 AM, Adrian Hope-Bailie <
>> adrian@hopebailie.com> wrote:
>>
>>> I agree.
>>>
>>> Theoretically it could be "wallets all the way down" but practically
>>> that seems unlikely.
>>>
>>> It seems more likely that users will select a primary wallet that covers
>>> 90% of their payment instruments and this will link to one or two secondary
>>> wallets that are needed to support obscure payment instruments.
>>>
>>>
>>> For the majority of users even this won't be the case, they'll have a
>>> primary wallet and that will be all.
>>>
>>> On 17 July 2015 at 06:18, <Joerg.Heuer@telekom.de> wrote:
>>>
>>>> … if we succeed to establish a wallet that really belongs to the user,
>>>> multiple wallets should be the exception.
>>>>
>>>>
>>>>
>>>> If we ever see client-side wallets battling payee-side wallets, I’d
>>>> call it defeat.
>>>>
>>>>
>>>>
>>>> Cheers,
>>>>
>>>>                 Jörg
>>>>
>>>>
>>>>
>>>> *From:* Mountie Lee [mailto:mountie@paygate.net]
>>>> *Sent:* Freitag, 17. Juli 2015 06:24
>>>> *To:* public-webpayments-ig@w3.org
>>>> *Subject:* Multiple Wallets
>>>>
>>>>
>>>>
>>>> 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
>>>>
>>>
>>>
>>
>>
>> --
>> Mountie Lee
>>
>> PayGate
>> CTO, CISSP
>> Tel : +82 2 2140 2700
>> E-Mail : mountie@paygate.net
>>
>>
>>
>
>
> --
> Mountie Lee
>
> PayGate
> CTO, CISSP
> Tel : +82 2 2140 2700
> E-Mail : mountie@paygate.net
>
>
>


-- 
Mountie Lee

PayGate
CTO, CISSP
Tel : +82 2 2140 2700
E-Mail : mountie@paygate.net