Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Pay payment flow breakage #281

Closed
GuiltyDolphin opened this issue Jun 29, 2022 · 1 comment
Closed

Google Pay payment flow breakage #281

GuiltyDolphin opened this issue Jun 29, 2022 · 1 comment
Labels
mitigated Issue has an in-place mitigation.

Comments

@GuiltyDolphin
Copy link
Member

GuiltyDolphin commented Jun 29, 2022

Some sites (e.g., scanlantheodore.com) experience breakage in the Google Pay payment flow option.

We've found that the following cookie domains need to be exempted in order to allow this flow to proceed:

  • accounts.google.com
  • pay.google.com
  • payments.google.com

As an example of how to reproduce this breakage, try the following flow on us.scanlantheodore.com (last verified 2022-06-28):

  1. add item to cart, go to cart and checkout
  2. select the google pay option
  3. enter account name, proceed
  4. there is an error "Your browser has cookies disabled. Make sure that your cookies are enabled and try again."
    • → exception for "accounts.google.com" in the "cookie" protection mitigates this
  5. after entering password, pay popup shows but flickers/reloads repeatedly
    • → exception for "pay.google.com" in the "cookie" protection mitigates the flickering, though the popup continues to show a loading spinner
    • → exception for "payments.google.com" in the "cookie" protection allows the payment option to load
@GuiltyDolphin GuiltyDolphin added the mitigated Issue has an in-place mitigation. label Jun 29, 2022
@laghee
Copy link
Contributor

laghee commented Jun 13, 2024

Closing out as archived since we updated to a new transparency system in PR #2137

@laghee laghee closed this as completed Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mitigated Issue has an in-place mitigation.
Projects
None yet
Development

No branches or pull requests

2 participants