Mid-March we found an issue that our merchants were having with our 3DS feature.
Because of the phased roll-out for this new Chrome version, our merchants only started noticing the effects around mid-March.
From this version on Chrome is enforcing a secure-by-default cookie classification system, treating cookies that have no declared SameSite value as SameSite=Lax cookies. Only cookies set as SameSite=None; Secure will be available in third-party contexts, provided they are being accessed from secure connections. Do please note that the SameSite field is not yet a widely supported value in older browsers, as well as Safari and Firefox.
How to fix it
If you experience issues due to the new Chrome release, enable the following:
In Business Manager, go to Administration | Global Preferences | Security. On the Access Restrictions tab, select Enforce HTTPS. Click Apply.