When GooglePay/ApplePay dialogs are triggered on the cart or checkout pages (both shortcode and block-based), the customer's shipping address is submitted to the backend to update the cart. Within these dialogs, the customer can further interact with the ECE, such as:
Changing the shipping address
Selecting a different shipping method
If the customer dismisses the payment dialog without completing the payment, the underlying cart/checkout page remains in its original state without reflecting any updates from the GooglePay/ApplePay dialog interaction.
This behavior leads to an inconsistency: the changes appear lost on the cart/checkout page but are correctly stored and shown after a page refresh or navigation.
To improve user experience and maintain state consistency:
Either the cart/checkout page should revert to its prior state (before the dialog interaction), or
It should reflect the most up-to-date state from the GooglePay/ApplePay dialog.
This affects both blocks and shortcode implementation.
This affects both cart and checkout pages.
Description
When GooglePay/ApplePay dialogs are triggered on the cart or checkout pages (both shortcode and block-based), the customer's shipping address is submitted to the backend to update the cart. Within these dialogs, the customer can further interact with the ECE, such as:
If the customer dismisses the payment dialog without completing the payment, the underlying cart/checkout page remains in its original state without reflecting any updates from the GooglePay/ApplePay dialog interaction.
This behavior leads to an inconsistency: the changes appear lost on the cart/checkout page but are correctly stored and shown after a page refresh or navigation.
To improve user experience and maintain state consistency:
This affects both blocks and shortcode implementation. This affects both cart and checkout pages.
https://github.com/user-attachments/assets/dac977c2-2dbc-429d-96f3-fc718cb4f7b4
Acceptance criteria
Designs
N/A
Testing instructions
Dev notes
Additional context