#markendaya_code
open gorgeBOT
đ 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/1348834571549937684
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
regal gyro
Hi! Can I have the checkout session ID?
regal gyro
I am seeing the checkout session ID being appended to your success URL correctly. Could you show where and how you're are getting that error?
midnight halo
sure, how would you like me to do that?
regal gyro
Do note that our recommendation is to listen to checkout.session.completed event in your webhook. This will let you know once a Checkout Session has been successfully completed.
Sometimes your customers may not be redirected to your success URL. For example if they close their browser.
midnight halo
I'm working through the docs, and saw that I could include the session_id in the URL to pull the checkout information. I didn't know there was a webhook for checkout
regal gyro
This is our guide on how you can fulfil your orders for a Checkout Session: https://docs.stripe.com/checkout/fulfillment
This is the event I was referring to: https://docs.stripe.com/api/events/types#event_types-checkout.session.completed
regal gyro
Sure!
midnight halo
thank you!
when I test the checkout process I end up in "live" mode for the checkout
which isn't that huge of a deal, as I've created $1.00 test products, but still.
I'm using a 'test' secret key when creating the Checkout session.
or
I just double checked. I'm not.
It's a live key. sigh
regal gyro
I checked it as well, it's the live key.
midnight halo
now I get to figure out how to create a test key
found it.
So the webhook thing
reading the docs, it looks like the code I write gets fired when the customer is redirected back to my site
and I can use {CHECKOUT_SESSION_ID} in the URI to identify the session_id
but you said that not all customers are redirected back
so how do I get information on them?
regal gyro
Some additional details about what I mentioned earlier here: https://docs.stripe.com/checkout/fulfillment#:~:text=Webhooks are required
When you ask "so how do I get information on them", do you mean how do you get the checkout session ID correct? When you set up a webhook endpoint (https://docs.stripe.com/webhooks), you can listen to relevant events such as checkout.session.completed. The event contains the checkout session ID.
midnight halo
In the past I've used callbacks, where the processor posts information to an endpoint that I've specified. That post typically included a session/checkout id and some kind of status id that I could use to pull the current status of the transaction
is this the same sort of thing, just with different words?
regal gyro
Your description sounds similar to this but it would be best to go through the docs.