RE: A platform for testing Service Worker based Payment Apps

Hi Tommy,

Just a quick note to say that using your release I have created a web based payment app that works as expected - great news.

It is also worth mentioning that Chromium works well with two of these Service Worker based apps registered.

I have noticed that your build of chromium seems to exclude support for native Android payment apps, as previously released by Rouslan. As a result I can't test these apps and interoperability using a single chromium build or even install the two build alongside each other as they share the same package name.

With the above in mind do you guys think you could address this? i.e. merge the two builds maybe or change the package id for one of the builds. I know it would make my life much easier as I am working on both types of payment apps and I also think it would be super cool to be able to demonstrate interoperability between the two types of app.

Many thanks,
Conor

P.S. Is the code for your work something you could share? I am curious to see :)

-----Original Message-----
From: Ian Jacobs [mailto:ij@w3.org] 
Sent: 05 January 2017 23:38
To: Tommy Thorsen <tommyt@opera.com>
Cc: Web Payments Working Group <public-payments-wg@w3.org>
Subject: Re: A platform for testing Service Worker based Payment Apps


> On Jan 5, 2017, at 3:44 AM, Tommy Thorsen <tommyt@opera.com> wrote:
> 
> Happy new year everyone!
> 
> In response to the increased interest in implementing Payment Apps, I've spent some time (together with Rouslan and Jinho) implementing support for the Payment App API in Chromium. There's still a fair amount of work left, but we've progressed far enough that I've been able to build a prototype browser that can be used by implementors to do some preliminary testing of their Payment Apps.
> 
> This prototype browser comes in the form of an Android APK file. It can be downloaded from this page. There are some instructions on that page that will hopefully get you up and running. If you experience problems, let me know.
> 
> The current version of the prototype browser supports installing a payment app, and invoking it from the payment request dialog. It does not yet support passing data back from the payment app to the merchant, but I'm working on this. As we progress further, and implement more parts of the specification, I will publish new versions of the APK.
> 
> Hope this can be of help to you :)

Hi Tommy,

This is great news, thank you!

Ian

--
Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
Tel:                       +1 718 260 9447



This e-mail and any attachments are confidential, intended only for the addressee and may be privileged. If you have received this e-mail in error, please notify the sender immediately and delete it. Any content that does not relate to the business of Worldpay is personal to the sender and not authorised or endorsed by Worldpay. Worldpay does not accept responsibility for viruses or any loss or damage arising from transmission or access.

Worldpay (UK) Limited (Company No: 07316500/ Financial Conduct Authority No: 530923), Worldpay Limited (Company No:03424752 / Financial Conduct Authority No: 504504), Worldpay AP Limited (Company No: 05593466 / Financial Conduct Authority No: 502597). Registered Office: The Walbrook Building, 25 Walbrook, London EC4N 8AF and authorised by the Financial Conduct Authority under the Payment Service Regulations 2009 for the provision of payment services. Worldpay (UK) Limited is authorised and regulated by the Financial Conduct Authority for consumer credit activities. Worldpay B.V. (WPBV) has its registered office in Amsterdam, the Netherlands (Handelsregister KvK no. 60494344). WPBV holds a licence from and is included in the register kept by De Nederlandsche Bank, which registration can be consulted through www.dnb.nl. Worldpay, the logo and any associated brand names are trade marks of the Worldpay group.

Received on Tuesday, 10 January 2017 18:26:17 UTC