- From: L. David Baron <dbaron@dbaron.org>
- Date: Thu, 18 Jun 2015 22:43:47 -0700
- To: Evan Schwartz <evan@ripple.com>
- Cc: David Singer <singer@apple.com>, Web Payments IG <public-webpayments-ig@w3.org>
- Message-ID: <20150619054347.GA12012@pescadero.dbaron.org>
On Wednesday 2015-06-17 14:47 -0400, Evan Schwartz wrote: > You're right that we're interested in enabling merchants to collect > payments from users on the web, but they already do that today. > > We need to get more specific about what problem we're trying to solve. One > of the browser vendor reps made a good point yesterday that most web > payments today are made by filling out forms. If we're talking about > improving this, we're talking about replacing filling out forms with > something else. If we're proposing a replacement for something, we need > very compelling reasons for people to switch. Some reasons to switch that I'd offer might be: * less work for the end user to make a payment (typing in of credit card details, etc.), which should increase conversion for the merchant. Probably not "one click" or "one tap", but a lot closer to it than we are today. * improved security and perhaps even privacy for the user through a system that doesn't send their credit card number to the website, giving them (hopefully, if the UI explains the model well) more confidence in making payments to payees who they might not trust with their credit card number (I see this as particularly useful when purchasing online goods rather than physical goods, e.g., to pay a small amount to read the rest of a news article after seeing the first two paragraphs) -David -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla https://www.mozilla.org/ 𝄂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914)
Received on Friday, 19 June 2015 05:44:34 UTC