RE: What single thing should we deliver?

Agreed but push payments is more about back end IETF standards than front end Web standards, correct? We would have to focus more across various domains to achieve this, not just W3C?

Erik Anderson


-------- Original message --------
From: Manu Sporny <msporny@digitalbazaar.com> 
Date:11/24/2014  11:05 PM  (GMT-05:00) 
To: public-webpayments-ig@w3.org 
Cc:  
Subject: What single thing should we deliver? 

The discussion so far has given me hope that we're going to be able to
recommend doing something substantial with the Web Payments work. We
have some great people involved, which got me thinking - if we could
only deliver one thing, what would it be? What would be the most
impressive/simplest thing we could do? Some thoughts on that line of
questioning:

It seemed like push-based payments was pretty high on everyone's list at
TPAC of important things to do from a safety perspective.

The ideal use case for the buyer seemed to play a pivotal role as well
(more so than the ideal use case for the merchant or the payment
processor, even those were deemed very important).

If I had to summarize the single most important thing that this group
should do, I think it would be something like this:

Make it so that a buyer can:

1. Go to a website
2. Click a Buy button
3. Be provided an offer of sale / invoice
4. Choose their method of payment from an array of payment instruments
5. Complete the purchase and send the proof of purchase to the merchant
   to receive their goods/service

All of this would be done w/o exchanging any theft-worthy data with the
merchant.

If we do nothing else, wouldn't the above be a huge step forward in
worldwide payments? If so, shouldn't we craft the narrative and the
roadmap around achieving the above?

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: The Marathonic Dawn of Web Payments
http://manu.sporny.org/2014/dawn-of-web-payments/