[w3c/browser-payment-api] add an additional event in the hopes of providing standars for push p… (#223)

In the working group meeting we have started to explore push payment methods. Historically we have punted on considerations for these kinds of apps/methods, but I think we can no longer ignore it. This pull request is not complete, but I wanted to use it to spur discussion around this and work to drive it to completion in combination with a pull request on Payment App.

Why add this functionality? From a merchant's perspective, one of the major values of the payment request api in a pull payment method scenario is that many payment apps may resolve to the same or very similar payment methods, like a tokenized credit card. However, with push payment this is not the case due to the fact that there are proprietary systems and myriad differences in processing payment regardless of the fact that the end result is currency exchanging hands. In order to further incentivize merchant adoption and to get ahead of the problem of one payment app per payment method, I think adding failure resolution (and payouts which are not captured here) to the spec will prove beneficial.
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/browser-payment-api/pull/223

-- Commit Summary --

  * add an additional event in the hopes of providing standars for push payment

-- File Changes --

    M index.html (35)

-- Patch Links --

https://github.com/w3c/browser-payment-api/pull/223.patch
https://github.com/w3c/browser-payment-api/pull/223.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/browser-payment-api/pull/223