[w3c/webpayments-payment-apps-api] Design considerations for payment app registration: recommended apps, user consent, and optional registration (#21)

The core idea behind the original question in https://github.com/w3c/webpayments-payment-apps-api/issues/8 was to help create a better user experience around the payment app registration process. After some discussion, we mostly agreed that registration is definitely necessary to allow the user agent to specify things like enabled payment methods or instruments and to give the user the freedom to use their preferred apps.

This PR adds to the registration design considerations, pretty similar to the summary Ian gave at https://github.com/w3c/webpayments-payment-apps-api/issues/8#issuecomment-235642972 but with some clarification around user consent and non-requirement of registration in order to invoke it, see the relevant section with changes at https://jnormore.github.io/webpayments-payment-apps-api/#registration-and-unregistration. I thought it was worth illustrating how an invocation of a recommended app would work as well (in the Payment Request API spec), there’s no open PR but the changes on my fork are https://github.com/jnormore/browser-payment-api/commit/34c72dfa7121e5a9e3cc98319d3caed2fb23429d and spec can be viewed at https://jnormore.github.io/browser-payment-api/#paymentmethoddata-dictionary

cc @lyverovski
You can view, comment on, or merge this pull request online at:

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

-- Commit Summary --

  * Add design considerations for payment app registration, covering user consent and optional registration

-- File Changes --

    M index.html (36)

-- Patch Links --

https://github.com/w3c/webpayments-payment-apps-api/pull/21.patch
https://github.com/w3c/webpayments-payment-apps-api/pull/21.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/21