Re: [w3c/payment-request] PaymentRequest - Bluetooth connector (#865)

>> If it is that simple it should be simple to host an example showing how this would work in practice.

> Precisely, but the burden of proof falls on you to create such an example.

@marcoscaceres @adrianhopebailie No, a solution proposed by somebody needs to be proven by the proposer which in this case (effectively) is the Web Payment WG.  BTW, it sounds like a pretty fuzzy process having to install service workers for external (mobile phone based) payment handlers.  Current solutions (_which do not use PaymentRequest in the PC end_) do not introduce such requirements. 

_This_ proposal builds on extending already rolled out concepts such as the Apple Pay MacOS/iOS "combo" and FIDO2/WebAuthn.  The latter does (AFAIK...) not depend on push services or service workers.

Since one vendor already have a (_vendor specific_) solution, it really boils down to what the other vendor (having an 80% market share) wants to offer as a remedy.  It is of course way simpler building a Chrome/Android specific solution.  Note where you read it first 😀 @danyao @rsolomakhin 

-- 
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/865#issuecomment-483500704