#coder141418_error

1 messages · Page 1 of 1 (latest)

noble graniteBOT
#

👋 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/1375225439294984303

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

broken smelt
#

hello! that seems very strange that it would be occurring inconsistently, usually CORS errors are pretty easy to reproduce in my experience... can you share more about what your code is doing? or do you have a publically accessible version of the site (ideally running in test mode) where i can take a look?

#

also do you know if the errors people ran into included a reason?

rocky flint
#

Here is our sandbox account which is setup in test mode: https://31183.danceticketing.com/r/events/

You can enter the show, add some tickets to your cart, fill out contact info and then the payment element loads once you accept the terms and hit "Continue to Payment Page"

We also thought it was super strange that it was running inconsistently and just haven't been able to get it to happen on our end.

#

Here is the image with some acct_id's and such removed. We had this happen on several occasions but this is the first time we had gotten the buyer to send us the console log (as you can imagine that's not the easiest thing to get people to do haha)

354391.Screenshot_2025-05-22_164052.png
broken smelt
#

i can indeed imagine 😛

#

In many cases, it is caused by a browser plugin (e.g., an ad blocker or privacy protector) blocking the request.

#

if you have open comms with the customer you could maybe suggest they try in incognito to see if that works?

rocky flint
rocky flint
#

We'd asked them before to disable adblockers but many said they didn't have any on 🙃

brisk cedar
#

Just a question , Why are you making calls to stripe from the js running in the browser? I feel like since you blocked off the secret key in image that it could lead to leaking secrets?

rocky flint
#

And we've already processed a solid 250k+ transactions with only about 0.01% of them having issues

#

I just blocked out any keys whatsoever to be safe though, definitely overkill since you can just find them in our js file on the site haha

broken smelt
#

i appreciate the caution 🙂

rocky flint
# 
        // Create the customer session and get it back from the db.
        const session = await createCustomer(shopperGuid, studioId);
        
        // Ensure amount is properly rounded up and converted to an integer
        const roundedAmount = Math.round(amount * 100);
    
        const options = {
            mode: 'payment',
            amount: roundedAmount,
            currency: window.app.gateway_id === 5 ? 'usd' : 'cad',
            customerSessionClientSecret: session.customer_session_client_secret,
        };
        
        // Set up Stripe.js and Elements to use in checkout form
        elements = stripe.elements(options);

        // Create and mount the Payment Element
        const paymentElementOptions = { layout: 'accordion', paymentMethodOrder: ['card', 'apple_pay', 'google_pay'] };
        const paymentElement = elements.create('payment', paymentElementOptions);
        paymentElement.mount('#payment-element');

Is the code that's throwing the errors (specifically elements.create())

brisk cedar
broken smelt
#

i'm chatting with a teammate about this and i think we're on the same page, this is probably something client side that's goofing with the API call. it could be more than just ad blockers - it could be privacy extensions or really anything that sits between the client side call and us - i'll often suggest people try incognito mode since that usually disables all of their browser plugins in one go

brisk cedar
#

Could be an issue with the source of the request as seen by api.stripe[.]com where something on your app is messing with something along the lines of the origin when sending the request

#

Or extensions*

rocky flint
broken smelt
#

(also @brisk cedar i appreciate your contributions but we typically only allow the asker of the question and our staff to post in threads 🙂 )

brisk cedar
rocky flint
#

Also appreciate the help RipRock for what it's worth, our dev team has been kind of stumped the last few days so any ideas are welcome

broken smelt