W3C home > Mailing lists > Public > public-payments-wg@w3.org > July 2016

Re: [w3c/webpayments] [Payment Apps] Extending invocation of payment apps with other techniques than HTTP (#156)

From: Anders Rundgren <notifications@github.com>
Date: Wed, 13 Jul 2016 07:51:20 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc:
Message-ID: <w3c/webpayments/issues/156/232379895@github.com>
>>@adrianhopebailie You should only think of native messaging as a more powerful version of Android Intents because that's all it is claimed to be.

>Then what does it have to do with the payment API? If native messaging was standardised within W3C then I'd consider messaging between the payee website and a native app in scope for us to standardize. Since it's not, I don't.

Right.  This was directed to folks writing native apps who may not be entirely happy with the current solutions.  I actually expect Google to eventually use something not yet published.  The same goes for Samsung.

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/156#issuecomment-232379895
Received on Wednesday, 13 July 2016 14:52:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 13 July 2016 14:52:15 UTC