I don't have a specification to offer at this stage so regard this request as something that may or may not have a reasonable solution. The core problem is that there's quite a bunch of methods which aren't covered by the current set of specifications including: - PayPal - Schemes using an external mobile device as "payment method" to a desktop browser session. This method is gaining traction and effectively you already have it in Alipay using QR code as invocation method My question is simply if you feel that it would be _worthwhile_ looking into a possible (user-friendly) way to register external methods so that they would show up in the GUI. This is by no means perfect but the workaround (offering a button for "other methods") isn't that great either. This is particularly an issue on the desktop side which probably won't be supported by native payment applications to the same extent as for example Android. An external method would only return the selected method leaving the execution to subsequent steps performed by the merchant in similarity to "basic cards". -- 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/payment-request/issues/580
Received on Thursday, 10 August 2017 04:46:22 UTC