#eoghanobrien
raw novaBOT
Hello eoghanobrien, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
• eoghan-checkout-csp, 4 hours ago, 14 messages
bold flax
Are you using stripe.redirectToCheckout anywhere in your code? if not, it's a Server-side Checkout Session creation and redirect
heavy fox
Not using stripe.redirectToCheckout
I'm wondering why/if the redirect must happen on the server-side specifically
it works in most situations that I've seen to just use window.location.href to redirect
bold flax
I see, so you want do a client-side redirect? Sure it also works
heavy fox
We've been seeing errors like this with a couple of "enterprise" customers with browsers locked down with limited permission policies. Ever seen that before? That's the core reason for asking about the redirect
They're hitting that browser issue when redirected to the hosted stripe checkout page on a custom domain
bold flax
The message says content is blocked. Did the site owner add your domain and stripe domains (https://stripe.com/docs/ips) to their allow list?
heavy fox
Just read through that, who exactly is the site owner in this case (assuming we are), our customers are seeing the screenshot above on the hosted custom domain for stripe checkout only
they never see that on our site
bold flax
My guess is your customer's network has policy to allow only certain domain, can you ask your customer to access your website in a different network (i.e., phone tegethering) and see if they are getting the same error?
heavy fox
We have done that but that's not always an option, their IT admins often ask them not to use company cards outside the network, on another browser, another computer etc
bold flax
So you are saying they only see the error when accessing your website in their office network?
heavy fox
I believe so, at least from the few that have reach out to our support team
bold flax
OK, then it's clear that it's their network problem, and you should reach out to their IT admins.
bold flax
Add your domain and stripe domains (https://stripe.com/docs/ips) to their network allow list
heavy fox
has this come up before or is this a shot in the dark, the customer is already frustrated, we don't want to make things worse.
bold flax
I have no insights on how your customer configure their network, and I'd suggest you to work with their IT admin to conclude a solution.
heavy fox
we have many thousands of customers, you're suggesting we need to work with every IT admin of every customer affected by this issue?
bold flax
I'm afraid that I can't be much of help if your customer's network policy is blocking your and Stripe domains.
heavy fox
okay, should we be asking customers to allow only the first list of domains under the heading Stripe domains (https://stripe.com/docs/ips#stripe-domains)
in the context of Stripe Checkout
bold flax
Yes, and also make sure their DNS config allows stripe domains to be resolved to the following IP addresses https://stripe.com/docs/ips#ip-addresses
heavy fox
okay, thank you. we'll give it a shot