Re: Payment Initiation - platform integration

On 2015-09-16 11:45, Adrian Hope-Bailie wrote:
> Looking at the draft spec from Digital Bazaar for the CG and considering
 > both, our language in the charter, and also some of the comments from the
 > charter AC review I wondered what precedent there may be in defining how
 > a browser should process an API call that requires interaction with the platform (host OS).

This is IMO (next to the SOP issue...) the most important technical question!

>
> The best example I could find is in the Web Notifications PR published
 > earlier this month: http://www.w3.org/TR/2015/PR-notifications-20150910/#displaying-notifications

I don't understand much of this spec :-(  But I doubt it has any bearings on invocation of wallets and such.


>
> I would like to get the groups' (both IG and CG) views on the parallels here between the action "Displaying Notifications" from the Web Notifications recommendation and a potential "Initiating Payments" section we'd put in a recommendation from our WG.
>
> The pertinent line from the Web Notifications rec is:
> "Display notification on the device (*e.g. by making the appropriate notification platform API call*)." - emphasis mine.
>
> While I know not all platforms upon which browser's run today have mature "payment APIs" in the same way that they have relativley mature "notifications APIs" this open-ended approach seems appealing in that it avoids the browser needing to become complex payment processing applications.
>
> Rather, the messages passed to the navigator.payments API in the browser should simply be passed directly to the platform's payment API (following any security or privacy scrutiny or permissions checks we define).
>
> The timing seems right for us to work with the platform vendors

Indeed.


(many of whom are also browser vendors that have expressed interest in
working on this problem) to define a common vocabulary and logical messages for this flow.

I seriously doubt this.  AFAICT, they are simply "monitoring" the IG/CG activities.
In fact, they all have their own plans regarding payment systems.

Anders



>
> *Example:
> *
> On a mobile platform I see this working similarly to the way Android intents may function. The browser passes the payment initiatiation request to the platform and the user is prompted with the app selection dialogue they are accustomed to for selecting the app they want to use for that action (the same way you select which app to use when sharing a photo for example).
>
> Thoughts?

Received on Wednesday, 16 September 2015 11:44:46 UTC