> It would also be helpful for us to know that you're working with the people already in the Web Payments space. Have you contacted any of them? Do they have any feedback on your proposal? Hi, I'm working in the Web Payments space and have been working with @ynyhxfo. (Granted, I'm from the same company as @ynyhxfo, so maybe that's not the best example.) For what it's worth, I have [presented the payment link proposal](https://www.w3.org/2023/09/12-wpwg-minutes.html#t03) at the 2023 W3C TPAC in the Web Payments Working Group (WPWG). > Do they have any feedback on your proposal? Have you engaged with them directly? Are you finding any interest? 1. A [question](https://github.com/WICG/paymentlink/issues/3) from @marcoscaceres about using custom schemes. The stance taken by @ynyhxfo's group is that the non-HTTP schemes are the appropriate approach. 2. TPAC presentation question about the user's ability to select the payment app. 3. TPAC presentation question about the risks of malicious JS or iframe injecting a payment link on a page. Other browser vendors have not expressed interest in implementing this. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1015#issuecomment-2593225918 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1015/2593225918@github.com>
Received on Wednesday, 15 January 2025 15:33:03 UTC