#frisbee_checkout-bug
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/1400168576949686352
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
๐ Do you have request ID I can look at? When did the call to retrieve the Session take place? After it was confirmed or prior to confirmation?
here's a request ID
req_hsmuujepH4GodO
I call to retrieve a few minutes ago.
What do you mean by "confirmed or prior to confirmation"?
If a Checkout Session has been created, but payment details haven't been submitted yet, the PI would not yet exist.
I'm seeing this was confirmed a while back however and there was a PI in the reponse to the initial confirmation. Digging a little further
I have the checkout session id and the payment intent id saved in our database -- it just seems like I can longer access the payment intent object via the checkout session object
Sorry, still investigating.
I appreciate your patience, looking to see if any of my team members are familiar with this behavior.
Hi there ๐ I'm jumping in as my teammate will need to step away soon. Let me take a closer look at when that retrieval request was made in comparison to when the Payment Intent.
There was in a change in an API version where Checkout Sessions stopped creating a Payment Intent when the session is first created, now they wait until its time to process a payment to create the associated Payment Intent. I'm working on double checking what version introduced that change.
Oh, hm, but there isn't a Payment Intent associated with this Checkout Session at all, weird. I'm going to need to spend a couple minutes looking through things more closely.
Can you make that request again, the same way you made req_hsmuujepH4GodO, and copy/paste the raw output of that here?
Sure
Hm, yeah, that definitely looks odd. Still looking to see what I'm missing here.
Oh hey... I noticed that the issue only happens with older checkout session objects.
I didn't run into this problem with a newly created checkout session.
Oh nevermind... it looks random
Oh, interesting! Can you share the ID of a Checkout Session where the payment_intent field is populated as expected?
Ah, dang
Just double checking, you're using Ruby for this, version 13.4.1 of our library?
here's a checkout session id that works.
cs_live_b1oVdOcgJhqtJKQES0oYDch14VxgGuNJLQsCT15Pw6uqarw0MyAHRDN7k3
And is this a recent request you made?
https://dashboard.stripe.com/test/logs/req_RuQ05F4TrcTRpA
If so, can you change the value you're using for expand to only include ['payment_intent']?
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
yes 13.4.1 is correct
We expand a few properties but I simplified the request to only payment_intent
For example:
req_cnU67SnEP52Orb
And you're seeing the same thing?
(I wasn't sure if we may avoid expanding the Payment Intent if payment_intent.latest_charge.balance_transaction was null)
Yes, both versions shows NULL
Hm, this is really weird and I don't have an immediate answer about what is going on here. I'm going to do some testing on my send to see if I can manage to reproduce this behavior.
Hrm... I do seem to find that payments made in 2024 have this problem but not in 2025
I was just stepping back through things, and making sure that the Payment Intent object does exist. And I do see it...
Do you have the Stripe CLI installed by chance?
i don't currently have it installed
I randomly checked some payments and it looks like payments made in 2021, 2022, 2023, and 2025 are fine
It's just 2024 that has the issue
Or Postman or something similar?
What I'd like to double check is that it's the raw response from the API that is missing the Payment Intent object, and not that the version of stripe-ruby you're using is dropping it for some reason.
i don't have postman either.
let me see if i can install the stripe CLI real quick
In the meantime, I'm going to look for older Checkout Sessions from my test account from 2024.
I'm seeing the same thing for at least one Checkout Session in my account, I'm looping in the right teams to look into this further.
I just installed stripe CLI,
I was able to reproduce this issue with the command
stripe checkout sessions retrieve cs_test_b193Cu8eUWuQCZbLQ0L1uvtMuiEkwWW4RzVzMPuCUw4AlZ8KkmXwkbbJnw
Thank you for that confirmation!
can i step away for an hour?
Yeah, I think I have all the information I need to get this to the right teams to keep investigating.
Thanks
@gloomy basin We're investigating internally. I recommend reaching out to support directly https://support.stripe.com/contact to be kept up to date on this issue and the fix