#ml74_code
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/1396809393105932388
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hi there!
how are you accepting payments? Checkout Session, Payment Element, something else?
Hello, using Payment Element
and does this error impact the payment flow?
Yes, we call stripe.createConfirmationToken() then send that to our server to process the payment, but we seem to be hitting this issue now at some point between calling createConfirmationToken and the fetch call to our own server
but we seem to be hitting this issue now at some point between calling createConfirmationToken and the fetch call to our own server
so the payment doesn't go though because of this error? are you using iframes to embed the Payment Element?
The payment fails - the request to our API is never triggered. We don't use iframes at all, which is why this is so odd.
would you mind sharing the website where you're facing this issue?
It's this demo event: X
ok how to get to checkout?
Just select any amount of tickets and proceed
You should get a button along the bottom?
I don't see the Pay securely
oh it's under the cookies
what's failing is not the PaymentElement confirmation token but rather a POST to https://boris.glistrr.com/demo/v1/widgets/events/987/tickets/transactions/59253/payment
and it's a cors issue
so you need to allow inbound HTTP requests with glistrr.com domain from your server at boris.glistrr.com
I believe it's set to * already on boris.glistrr.com since we have widgets hitting that endpoint from various domains
I just found it odd that it wasn't triggering the request at all in the browser (or at least logging it)
So I thought the issue was coming from the step before
at sendPaymentRequest (59253?guid=7ztV3AZRrKCyZY7_1753100246.1578:1681:28)
at sendPaymentRequest (59253?guid=7ztV3AZRrKCyZY7_1753100246.1578:1716:24)```
this isn't Stripe related though
you need to look at your server logs
Ok, I'll dig further here. Thank you!
let me know if you need any more help