|
|
|
|
|
|
by WatchDog
1416 days ago
|
|
|
I worked for a payment gateway years ago, when safari rolled out their initial blocking of third party cookies back in 2013 it broke some of our transaction flows yes. There are a bunch of different kinds of payment gateway integrations, with various tradeoffs. However a common pattern, at least at the time, was to use an iframe with the payment form in it. Our form was multi page, and used cookie based sessions to track state between pages, so when they started being blocked, the payment form stopped working for safari users.
The solution we chose at the time was to put the session id into the URL, but that has it's own security issues. There are other ways to address that particular issue that don't involve cookies, but would have required a significant rewrite of the system. Some potentially legitimate ongoing use cases for 3rd party cookies, would be remembering payment details, and one click checkout across various sites that use the same payment gateway. |
|
|