#ek1338_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/1296034983915294773
π 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.
- ek1338_code, 12 hours ago, 42 messages
- ek1338_code, 1 day ago, 4 messages
π happy to help
Some more additional detail (screenshot is the response of my Java server endpoint) .
The full error (text field from discord was too short) is:
Uncaught (in promise) IntegrationError: fetchClientSecret failed with error "The fetchClientSecret function should always resolve with a client secret as a string. The function that was provided resolved with a value type of undefined."
at embedded-checkout-outer-8413047acd0aee5f4e385f2e208bd260.js:4:14077
It is all local, so I can not share, sorry
can't you use something like ngrok to tunnel?
And on the Dashboard, all requests for creating this session come back green, so from server side checkout-session wise it should be fine
I am not familiar with that ngrok tooling sorry
would you mind sharing the backend code?
I think you're just returning the string
instead of a json { client_secret: "cs_test_xxxx" }
you can find the code of the backend here https://docs.stripe.com/checkout/embedded/quickstart?lang=java
Great observation! Argh, and I even tried it yesterday with client_secret. But, it is actually clientSecret. Tried it with that json key and now it renders. Always those little things, ha. Thx for gr8 support!
let me know if you need any more help
Thanks! Maybe a short follow-up. I try to shortcut the implementation of /create-shipping-options by just returning {type:'object', value: {succeeded: true}} on my server (as in tutorial).
But the stripe form somehow seems to know that no actual update was done. I will implement that later, but interesting how it knows that i did not actually update my session
(I've also entered sth. in Address line 2 - same result)
I am not sure why the Stripe widget gives me the error Shipping details missing. Please update the Checkout Session with a complete shipping address and try again. even though I filled out every detail in the Shipping address form
my server is returning the simple JSON {type:'object', value: {succeeded: true}} as in https://docs.stripe.com/payments/checkout/custom-shipping-options#customize-shipping-options (just without actually updating the stripe session with a new shipping price - I will that later. For the moment I am just irritated why the stripe widget is giving me the error in terms of the Shipping details missing, even though everything is filled out in the form)
my assumption is that stripe somehow sees, that my server is actually not really updating the stripe-session on the server-side (but only returning the simple json). And therefor the error
I think you just need to add Address Line 2
No, I tried that, same error
let me check
you haven't done this step https://docs.stripe.com/payments/checkout/custom-shipping-options#customize-shipping-options:~:text=Sessionβs line items.-,Update,.,-server.js though
Yeah, exactly π Okay, that was also my assumption. Probably stripe will somehow see, that I just was doing the shortcut (returning plain json) without actually updating the session. Alright, will implment that later, thanks!
sure