#tut557_code

1 messages ¡ Page 1 of 1 (latest)

grand hullBOT
#

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

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

charred treeBOT
olive forge
#

Hello, I know that the client reference ID will show up on API objects but I am less familiar with the dashboard, so I don't know if it is expected to show up there. Can you retrieve the session via the API and see if this value is set properly on the session object?
https://docs.stripe.com/api/checkout/sessions/retrieve

quartz anchor
#

where can I get the checkout session code so I can access it?

olive forge
#

That doc has example code for cURL and each of our client libraries

quartz anchor
#

no, not as in software code, code as in the "name" of a checkout session, so the program knows witch one I want the one in the documentation is just a test code, but I found it here now. and yes the client ID is there, thank you very much

olive forge
#

And gotcha, that is good to know that that worked. My colleagues on our support team may know more about seeing this in your dashboard https://support.stripe.com/?contact=true
The one workaround that I know of to see this client ID in your dashboard would be to look for the checkout session completed event at the bottom of the payment's page. That event will have the full checkout object which should have this ID

#

Whoops, wrong thread for the message that I just deleted. Sorry for the confusion