#literatelapellabel_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1352231083965677609
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐ can you share the error you're seeing?
Hm, is AnalyticsReporter.js your file?
No its one of Stripes components
Hey! Taking over for my colleague.
Have you had a chance to add these CSP directives?
https://docs.stripe.com/security/guide#content-security-policy
Yes they've been added, I don't think its our CSP at fault, I'm wondering if its the embedded frame has its own CSP ?
What guide are you following ?
I followed the guide you've linked to but for connect embedded components
I mean what guide you are following for integrating Stripe Product
Oh I see. We've followed the connect integration for stripe hosted onboarding via embedded components
It's all working as expected but the CSP error might be a cause of concern for anyone onboarding that thinks to open the browser terminal
If it doesn't prevent your users from completing the onboarding - you can ignore the error.
OK, I do think its an error with the onboarding componets available, as disabling our CSP entirely so none is enforced still gives this issue
Is there an issue with onboarding?
only that it reports in the browser console a resource is blocked by a security policy, which may impact user trust. I did some digging and it looks like r.stripe.com is used to track calls to the embedded js files for your / stripes internal analytics purposes.
It seems unfortunate that this looks like an error related to security on our side from an uniformed user perspective
I don't expect many uninformed users to inspect your website with dev tools.
However, if you actually receive user reports concerned about this issue, feel free to reach out to Stripe Support: https://support.stripe.com/?contact=true