#cberube
tidal cypressBOT
Hello! 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.
- cberube, 5 days ago, 2 messages
mental tapir
app.use(function (req, res, next) { res.header('Access-Control-Allow-Origin', '*'); res.header('Access-Control-Allow-Credentials', 'true'); res.header('Access-Control-Allow-Methods', 'GET'); res.header('Access-Control-Allow-Headers', 'Origin,X-Requested-With,Content-Type,Accept,content-type,application/json, application/rss+xml'); next(); });
urban kelp
Usually CORS errors with r.stripe.com have no actual affect.
As that is just an internal endpoint for analytics and fraud tracking
mental tapir
I also implement CSP rules. That might be the cause.
It is a demo for a client. I would like it to be very clean.
would you recommand specifing the ned point here as well:
res.header('Access-Control-Allow-Origin', '*'); instead of *
['*.stripe.com'. 'other.com']
urban kelp
That depends on your environment, I can't really say.
mental tapir
Any solution to get these CORS issues working without throwing errors.
urban kelp
Yeah you are already on the right track -- you need to adjust your policy to allow for this request to r.stripe.com
But I can't really tell you how you would go about that exactly as it is dependent on your server config
mental tapir
I amm aslos having this warning althought it seems to be configures correctly:
`controller-5e548789dc64dc21fd5e170343105d21.js:1 [Stripe.js] You have not registered or verified the domain, so the following payment methods are not enabled in the Payment Element:
- apple_pay
Please follow https://stripe.com/docs/payments/payment-methods/pmd-registration to register and verify the domain.`
urban kelp
You see Apple Pay when you see that warning? And you have verified the relevant domain in your account?
urban kelp
Are you using Connect here by chance?
Do you have an example PaymentIntent you can share from one of your tests?
mental tapir
I am using link-authentication-element, address-element, payment-element.
urban kelp
That's fine, Apple Pay should appear in Payment Element if you are using Safari, have a live card in your wallet, and have verified your domain
If you have a link to your test site I can also take a look that way
urban kelp
Where do I click once I go to that link?
urban kelp
Okay figured out how to get to your checkout page. Hmmm so I do see that the domain is verified in live mode on your account, which should suffice. But I see it is unverified in test mode. Try just disabling the domain in test mode at https://dashboard.stripe.com/test/settings/payment_method_domains?enabled=true
@mental tapir tagging you so you see the above
mental tapir
am using test account for the demo
urban kelp
Yeah I know but really if you have it enabled in live it should just work in both live and test
Otherwise, you'll need to have it be verified in test
Which means you could try disabling and re-enabling as well
Which may fix the issue
mental tapir
ok, will try