3 ms·
Browsers are restricting third party identity for privacy reasons, which means they now need to offer a specific API instead of letting developers build somethi
by jefftk 7y ago
Browsers are restricting third party identity for privacy reasons, which means they now need to offer a specific API instead of letting developers build something out of third-party iframes:
"It's important to note that many of the tricks (like hidden iframes from PSPs) that are used to make payments frictionless today are going to become useless as browsers roll out more changes to protect user's privacy (e.g. killing 3rd party cookies and storage). The privacy improvements are good but they have significant side-effects on UX. PR API and PH API offer a way for websites to invoke a payment app from another origin (eg. shop.com invokes paypal.com) without losing context (the payment app is rendered in a modal window not via a redirect) and without needing to know up front what payment methods the user supports (good for privacy)."
-- https://news.ycombinator.com/item?id=22465032 https://news.ycombinator.com/item?id=22465032