QR use cases about webpayments

[cyberphone]

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.

[Goosth]

Thanks Nick for the writeup. I think @ianbjacobs 's comment makes sense that the case 4 could still be dealt with by adding an URL to the QR code, even if it is not the same as the content of the QR (which in this case is Non-Url).

[halimnadergrace]

> R

[Malvoz]

Relating to the browser capabilities aspect, I'd like to note that there's a QR/barcodes HTML proposal: whatwg/html#5801.

[ianbjacobs]

Closing after a long period of inactivity.