W3C home > Mailing lists > Public > public-webpayments@w3.org > November 2014

Re: Discussion - Payment APIs: others are thinking about this problem space, too

From: Anders Rundgren <anders.rundgren.net@gmail.com>
Date: Fri, 14 Nov 2014 08:36:07 +0100
Message-ID: <5465B0E7.7070703@gmail.com>
To: Stephane Boyera <boyera@w3.org>, David Ezell <David_E3@VERIFONE.com>, "public-webpayments-comments@w3.org" <public-webpayments-comments@w3.org>, Web Payments CG <public-webpayments@w3.org>
On 2014-11-14 08:13, Stephane Boyera wrote:
> The article of payxintl is very interesting.
> As we can all see, the domain is moving quickly. This is a great
> momentum for the group. At the same time, it is also more pressure on us
> to move at the pace of the industry.

How about FIDO?  They have lined up more folks than anybody else
have including the payment giants and the platform vendors.

I guess Apple will be releasing information at some later date
because an Apple-only payment system will eventually die.

I do not believe in creating abstract APIs that are not backed
by a least one concrete implementation.  That would be like TCG
who toiled with the TPM (Trusted Platform Module) for 12 years(!)
only to find out that the bulk of the market had taken an entirely
different approach called TEE (Trusted Execution Environment).

Anders

>
> It is important to highlight not only the importance of API, but the
> importance of open standardized API that can create a level playing
> field for all actors.
>
> In all cases, I think we have to move further down and look into which
> API for what purpose, carrying which data etc.
> The first diagram we put on the payment agent task force is a very very
> first step in that direction. I believe we need to see if we can build a
> consensus on such a high-level view, and then start to look into each
> individual module that will help identify the needs in terms on API.
>
> steph
>
> Le 13/11/2014 20:54, David Ezell a écrit :
>> Dear IG:
>>
>> Here is a recent article on APIs in payment[1].  The point is that others are thinking about this problem, too.
>>
>> As I see it, there are two levels of API with which we are concerned:
>> 1) Interfaces for the "payment agent"[2] - probably WebIDL defined interfaces.
>> 2) RESTful web services for other as yet TBD goals.
>>
>> Examples of this second group would include discovery of payment services, potentially with dynamically changing API components.  Just one idea.
>> For discussion specific to area #1 be sure to use the [payment_agent] tag at the beginning of your subject line.
>>
>> We need to generate some concrete ideas and get the ball rolling.
>>
>> Best regards,
>> David Ezell
>>
>> [1] http://payxintl.com/payments-apis-the-last-mile-to-realising-the-holy-grail-in-payments/
>> [2] https://www.w3.org/Payments/IG/wiki/Payment_Agent_Task_Force
>>
>> "Energy is more efficient than efficiency." - attributed to FDR
>>
>>
>> ________________________________
>> This electronic message, including attachments, is intended only for the use of the individual or company named above or to which it is addressed. The information contained in this message shall be considered confidential and proprietary, and may include confidential work product. If you are not the intended recipient, please be aware that any unauthorized use, dissemination, distribution or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and deleting this email immediately.
>>
>
Received on Friday, 14 November 2014 07:36:35 UTC

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