#hans-as_sepa-debit-confirmation-failure
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/1222101560398581810
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
If you've setup a CSP on your website, please include the following CSP directives https://docs.stripe.com/security/guide?csp=csp-js#content-security-policy
Hey Jack, thank you for your suggestion but CSP has already been set correctly in our application. Every other payment method is working as expected (at least we tested cards and PayPal).
It seems Stripe is blocking loding the page needed for SEPA payments in a frame. Please see screenshot attached!
Stepping ion here. Can you confirm the function/code you're using that initialises the API calls that return the CP errors?
If you can share the full code that would be helpful
the interesting part is:
console.log('now confirming payment');
const { error } = await stripe.confirmPayment({
elements,
clientSecret,
confirmParams: {
return_url: ourReturnUrl,
},
});
console.log('done confirming payment');
The problem is we never reach the "done confirming payment" message
Can you share all the code including the handler that invokes that function?
Every other payment method is working as expected (at least we tested cards and PayPal).
Likely expected as neither of those are redirect PMs
ok, here is the Stimulus Controller with the Stripe Integration: https://gist.github.com/hans-aboutsource/11cc43d9030abf8d8061c04738dbe815
What is a 'Stimulus Controller'?
https://stimulus.hotwired.dev/ is the framework we use to develop our client side Javascript. In general the connect() method is called when opening the payment form and onSubmit() is called when the form is submitted.
Stimulus is a JavaScript framework with modest ambitions. It doesn’t seek to take over your entire front-end—in fact, it’s not concerned with rendering HTML at all. Instead, it’s designed to augment your HTML with just enough behavior to make it shine.
You're probably best off writing in to my team so we can take a deeper look at your issue: https://support.stripe.com/contact/email?topic=api_integration
Worth noting that we don't have first-class support for Stimulus so there might be compatibility issues there. If you can include the link to your code and the CSP policies you configured that'll be great!
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
ok sure, will do that. As I said earlier, the integration was working before and last night it broke out of the blue 😕
Yeah there's no reports of widespread CSP issues here so unlikely to be something at our end
understood. Thank you for your help!
Hey, we also get this issue from Stripe's end
Hey GazalaM, have they been introduced in the last 12 hours, too?
Yes, exactly
From 7pm Yesterday Berlin time (CEST)
@peak bay Is there a way to escalate this issue?
To confirm this is happening on test mode SEPA payments with the Payment Element?
@worn kettle have you also configured CSP rules?
yes! We just started implementing Stripe and do not have a Live application yet. Also from Germany, btw.
For us, we noticed it on Live mode as well, right @vapid vessel?
Is there somewhere I can reproduce this issue?
My tests redirect fine. If you can share a pi_xxx ID too
yes on live mode as well. You can test it for a while at www.finn.com/de-DE (try checkout till payment submission)
OK, I can reproduce now. Escalating
Hi, just want to add we at mieterengel also have the same problem in production and staging. Only for sepa, all other payments work for us so far.
We noticed that we are using an older version of stripe-js and react-stripe-js and are currently testing if using the newest version fixes the problem for us. Can any dev from another company tell us if you are using the newest major version or also something older when experiencing this problem?
I don't think its related to the version: We're using <script src="https://js.stripe.com/v3/"></script> (newest major version) and have the problem as well.
Thank you
We're working on fixing the issue – will report back once addressed. Appreciate your patience
hans-as_sepa-debit-confirmation-failure
Happy to share that this should be fixed now