This article describes a known Adobe Commerce 2.4.1 issue where customers get signed in to the previously used Amazon accounts instead of being suggested to log in, when using Amazon Pay during checkout.
Affected products and versions
- Adobe Commerce on-premises 2.4.1
- Adobe Commerce on cloud infrastructure 2.4.1
Customers get signed in to the previously used Amazon accounts instead of being suggested to log in, when using Amazon Pay during checkout.
Steps to reproduce:
- On storefront, add any item to the shopping cart and proceed to guest checkout.
- Click the Amazon Pay button. Amazon.com sign in pop-up appears.
- Log in to the Amazon account.
- Select an address and click Next.
- Select the payment method.
- Click Place order.
- Go back to the home page and log in to the store account.
- Add any item to the shopping cart again and proceed to checkout.
- Click the Amazon Pay button.
You get automatically logged into the previously used (Step 3) Amazon account again.
Amazon.com sign in pop-up appears and you can log in or create a new account for Amazon Pay.
The issue might happen in one of the following situations:
- When the
SameSitecookie value is
LAX, the cookie will not be sent as part of any third-party calls.
- Mozilla Firefox content blocking feature prevents third-parties from tracking browser users’ activities by blocking usage of scripts and client-side storage mechanisms. Firefox uses an external vendor, Disconnect.me to provide a list of tracking sites to be blocked. Amazon Pay uses an iframe on a third-party website to return an access token after sign-in and render Address and wallet widget. With the content blocking feature, Amazon Pay iframe load requests are considered as third-party tracking requests and get blocked, resulting in the buyer not being able to proceed with checkout.
- Any situation where third-party cookies or JS are being explicitly blocked by the browser.
Make sure Amazon Pay iframe requests are not blocked by browsers.