#beardage_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/1410488545831030834
π Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- beardage_code, 1 day ago, 18 messages
- beardage_code, 1 day ago, 7 messages
Hi @onyx oxide do you see any error in the browser console?
nope unfortunately not, they all just hang and then eventually report a timeout, one sec I'll grab a screenshot
looks normal here, I do see this error in the console from some point "pay.js:332 DEVELOPER_ERROR in loadPaymentData: An error occurred in call back, please try to avoid this by setting structured error in callback response"
then after pressing play and loading for 30 secs or so, it returns this
Ok, do you have a public URL that I can visit and test your integration, can you also share with me the code you wrote in handleExpressSubmit and onReady ?
I can provide a url but you'll have to make an account (it'll redirect you to auth and back)
Can you DM a a login credential?
here's the handleExpressSubmit and onReady
give me just a bit please, have to deploy another service and the action takes a bit
Looks like you didn't call await elements.submit(); in handleExpressSubmit function
https://docs.stripe.com/elements/express-checkout-element/accept-a-payment?client=react#submit-the-payment here's the complete example code
we are using the checkout provider and useCheckout, should I also be using useElements? The difference in those parts of the docs has definitely been confusing for me personally π
Ah I see, so you are using checkout session with express checkout element https://docs.stripe.com/checkout/one-click-payment-buttons?payment-ui=embedded-components ?
Can you show me the code in fetchClientSecret function ?
https://docs.stripe.com/checkout/one-click-payment-buttons?payment-ui=embedded-components#handle-one-click-payments yeah this part of the tutorial is what I've been using
so fetchClientSecret is hitting this function that requests a secret from our backend service, I can grab the code on the other side if that's helpful too
sent credentials via dm
OK, let me take a look
currently deploying a fix that should take care of the remaining csp errors in the console
Ok, let me know when it's ready to test
I can reproduce the same problem. Taking a closer look
awesome thank you
Getting the same time out error in both Apple Pay and Google Pay
yup it seems like every enabled express payment option times out the same way
I may fall asleep soon, but if you think of anything please let me know π
Hello @onyx oxide, we have sent you a direct message, please check it at https://discord.com/channels/@me/1410509090186068060
- πThe message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
I just send you a direct message, can you use the link to contact Stripe support? They will pass the support ticket to us and we will continue helping you through emails.
yup will do in the morning, thank you for taking a look!
No problem. When you reach out to support, can you also share with them the relevant code in text form?
sure not a problem