Re: [w3ctag/design-reviews] Payment link type in HTML (Issue #1015)

stephenmcgruer left a comment (w3ctag/design-reviews#1015)

Hi TAG,

Thanks for bearing with us. I'd like to respond to Martin's concerns over integration effort needed, and the potential impact on other browser makers. We are big supporters of the web having multiple implementations, whether it is the existing engines like Blink, WebKit, or Mozilla, or the exciting new engines coming out of projects such as Ladybird. And we agree that care should be taken to design standards and specifications with the whole web ecosystem in mind, including the multitude of browsers. We always welcome feedback from the TAG or other venues, and take it seriously.

However, that does not necessarily mean we will stop investing in solving a problem or tackling a problem area due to concerns over it being difficult or costly. There are difficult and important problems to solve on the web, problems where the browser can provide real benefits for users (and where the web needs to compete against other platforms) - and in our opinion, payments is one of them. We do not intend to shy away from such problems, and we in fact view them as a key area for browsers to have healthy competition (which in turn we believe leads to a thriving web platform).

All that said, in the case of paylinks we believe that long term they can be specified based on existing web specs - that is, as 'declarative Payment Request' calls, backed by the existing Payment Handler concepts. @rsolomakhin and I [have written a high-level description of this idea](https://github.com/WICG/paymentlink/pull/16), if interesting to the TAG. If and when another browser or payment provider commits to implementing this kind of plan, we're excited to work with them to flesh it out. Until then, we still intend to start with paylinks as they are defined currently in the explainer. As a first step on the longer-term path, we [have proposed that](https://lists.w3.org/Archives/Public/public-payments-wg/2025Jan/0006.html) paylinks be adopted by the WPWG, and it appears that there is interest in that group to do so.

We hope this addresses some of the TAGs concerns, and are happy to discuss further.

Thanks,
Stephen

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1015#issuecomment-2690997098
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1015/2690997098@github.com>