The W3 press release and a relevant Chrome link,<p><a href="https://www.w3.org/2023/06/pressrelease-spc-cr.html.en" rel="nofollow noreferrer">https://www.w3.org/2023/06/pressrelease-spc-cr.html.en</a><p><a href="https://developer.chrome.com/articles/secure-payment-confirmation/" rel="nofollow noreferrer">https://developer.chrome.com/articles/secure-payment-confirm...</a>
W3C should standardize cookie policy banners, and popups. This monstrosity of a feature should have always been a browser feature, not a burden for web developers.
It's not clear to me from the article how this is supposed to work.<p>My favourite payment system is still the Dutch iDeal: marchant creates a payment request, redirects the user to their own bank, the user uses thhe bank's authorization system to authorize the payment, informs the merchant that payment is successful, and then redirects the user back to the merchant who now knows the transaction is successful, without having to know anything about how the user paid.
How is this going to integrate with my banking app, though? I quite like the Apple Pay or iDeal approaches. I don't really want my browser to confirm payments to be honest.
Edit: looks like I made a fool of myself. I didn’t know about Apples other implementation of a similar feature.<p>It seems nice but I think Apple will never implement this for Safari, even if standardized. It’d bypass their AppStore and make the web even more “app-like”, which they already aren’t crazy about.
Interesting that this is built on top of FIDO/webauthn.<p>I'm still somewhat worried about webauthn but recent news around it has (imo) been moving in a more positive direction and I'm less worried about it than I used to be. So I would really love to be cautiously optimistic about this.<p>Assuming webauthn turns out well, this seems to be a pretty natural and pretty useful extension.