Re: [w3c/webpayments] PROPOSAL: A new document structure for this API (#134)

@ianbjacobs wrote:
> Because the browser is going to be the primary mediator

This may be true in the first several years of deployment, but I'm skeptical that this will continue to stay true as the years roll on. For example, There are currently 4.9B IoT devices, with numbers projected to hit 20.7B in 4 years. I suspect that a number of those devices may become payment mediators.

> rather than abstract without experience

We already have semi-automated / automated payment use cases with the HTTP API, so I don't think that the discussion is abstract.

I haven't quite figured out if I agree with @adrianhopebailie's proposal, but one concrete way we'll know if we need something like it is if we start duplicating mediator conformance criteria in both specs (and I think we're already well down that path):

http://w3c.github.io/webpayments-http-api/#payment-flow-overview

---
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/134#issuecomment-222859353