Since the "second device" with a native payment application is pretty much the de-facto standard these days, most systems probably work as follows: - If on a desktop: checkout with XYZ-pay using QR - If on a mobile: checkout with XYZ-pay An advantage with this arrangement is that you can use the same scheme at PoS terminals as on the desktop Web. A minor "glitch" in this scheme is that the definition of mobile versus desktop is not entirely clear. A problem with building on the payment sheet in the browser is that it haven't got much traction. -- 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/257#issuecomment-742515715Received on Thursday, 10 December 2020 13:19:08 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 10 December 2020 13:19:09 UTC