Re: [webpayments] Payment Method Identifier Registry should have oversight / formal structure (#25)

And I think that, as a value-add wallet developer, I would prefer to create
a smart wallet that does all sorts of cool stuff with every payment method
out there.  And have it dynamically expand its collection.  The
intelligence I add to my smart wallet - negotiating with the vendor,
dealing with affinity card information, bartering with the user for access
to their data in exchange for discounts - that's where I want to put my
energy.

If we don't provide this registry, someone else will.  Doesn't it behoove
us to ensure that it is done by us, done right, and done in a way that puts
all payment methods on an equal footing?

On Mon, Dec 7, 2015 at 10:44 AM, ianbjacobs <notifications@github.com>
wrote:

> Can you see us saying "NOTE: Wallet developers SHOULD periodically do a
> comprehensive web
> search to discover new, interesting payment methods in which their users
> may be interested."?
>
> I don't think wallet developers will hunt around looking for things to
> support.
>
> Rather, companies will promote their products and it will be an
> implementation detail what URI (or other string) people should use within
> the W3C APis to get those products to work.
>
> Then, if you are a wallet developer and want to know how to get
> FooPayments to work in your wallet, you'll search for FooPayments, and
> there will be a section for developers that explains what to do.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/w3c/webpayments/issues/25#issuecomment-162587059>.
>



-- 
Shane McCarron
halindrome@gmail.com


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/25#issuecomment-162589830