W3C home > Mailing lists > Public > public-webpayments@w3.org > April 2015

Re: [payment agent] Payment architecture feature priorities

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Fri, 24 Apr 2015 17:40:11 +0200
Message-ID: <553A63DB.5020401@gmail.com>
To: Dave Longley <dlongley@digitalbazaar.com>, public-webpayments@w3.org
On 2015-04-24 16:48, Dave Longley wrote:
> On 04/24/2015 10:12 AM, Anders Rundgren wrote:
>> On 2015-04-24 15:47, Tony Camero wrote:
>>> Why would the the building blocks/protocols for web payments not
>>> directly migrate
>>> into native apps?  Any native app could certainly meet the
>> requirements set for
>>> a web payments. It seems inclusive to me.
>> It is the opposite that doesn't work smoothly, making
>> Web(browser)-payments a difficult target for innovation.
> I think, at least to start, the browser would function primarily as a
> decision assistant and a conduit for ferrying messages between the
> various participants in the payment process. That should, in no way, get
> in the way of innovation by payment applications, providers, etc.
> Rather, it will assist them by letting them function with a standardized
> set of expectations. Also, note that a "user agent" or "payment agent"
> isn't limited to a "browser", rather a browser is one example of a piece
> of software that implements (or would implement) it.

The innovative payment systems I have seen were either 100% App-based or building
on an OOB-thing (like SMS callback) between the browser and a mobile device.

I don't see that anybody will be able to go beyond this level without mucking
around in the browser which is a big NO NO.  Unless you're Google or Apple.

We can come back to this issue some 24 months from now.


>> Anders
>>> On Fri, Apr 24, 2015 at 6:25 AM, Anders Rundgren
>>> <anders.rundgren.net@gmail.com
>>> <mailto:anders.rundgren.net@gmail.com>> wrote:
>>> https://lists.w3.org/Archives/Public/public-webpayments-ig/2015Apr/0145.html
>>>      "One suggestion is not to rule out local apps for the initial
>>> charter.  W3C is seeking to close the gap with native, but this is a
>>> long term goal, and in the short term we should acknowledge that
>>> developers are likely to be attracted to native apps due to the
>>> richer capabilities available to native apps compared with web apps"
>>>      Finally a description that matches the reality!
>>>      Browsers are static bloated "monoliths" that doesn't enable
>>> third-party innovation.
>>>      Anders
Received on Friday, 24 April 2015 15:40:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:39 UTC