[w3c/webpayments-payment-apps-api] Native payment app support and others changes. (#46)

Changes in this patch:

1) Supporting native payment apps.
 - Origin bound confirmation of native app signatures.
 - Extension point in app manifest for platform specific payment apps
   or any other custom user agent logic.
 - Ability for user agents to download the manifest without
   ServiceWorker involvement from a well defined location. (App
   identifier to manifest location mapping is TBD.)

2) Allowing payment method to optionally restrict the list of payment
   apps that can use it. Specifics TBD.

3) Introducing constrained URLs for payment app identification.

4) Supporting user agent recommended payment apps.

5) Raising the issue of payment option support. Payment options add an
   extra level of abstraction with unique UX challenges. The note in the
   patch goes into further details.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/webpayments-payment-apps-api/pull/46

-- Commit Summary --

  * Native payment app support and others changes.

-- File Changes --

    M index.html (96)

-- Patch Links --

https://github.com/w3c/webpayments-payment-apps-api/pull/46.patch
https://github.com/w3c/webpayments-payment-apps-api/pull/46.diff

-- 
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-payment-apps-api/pull/46

Received on Thursday, 22 September 2016 16:31:51 UTC