#Piercy
1 messages · Page 1 of 1 (latest)
Hello, as far as I know, there shouldn't be a place that our node library does that. No such checkout session would typically be an error when trying to retrieve a checkout session from a different account than the one that created it. Is there anywhere that your application might try to retrive this checkout session as the platform account after creating it on the connected account?
That's the same thought I had. The only time we retrieve the checkout would be once we received a checkout.session.async_payment_succeeded or checkout.session.async_payment_failed webhook.
And we aren't receiving any of those
Ill keep digging, im sure it must be something we're doing. I just wanted to double check there wasnt a background process from the library that could cause something.
I'll see if I can find an error like this in your logs. Have you tried running it and going to your API logs to see if there is a call that shows that same error? https://dashboard.stripe.com/test/logs
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Ill log in and see if I can find it too, cheers for the help.
Not sure if it helps but I do see a call to retrieve the session coming from your platform account shortly after the checkout session is being created that is failing with this error. Looks like my initial theory may have been right https://dashboard.stripe.com/test/logs/req_q3TuaOxSlsjF9H
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Thanks for found that log, and associated event. Which has some expand options which pointed me at the exact line being called, so i should be able to figure why thats being called now. Thanks!
Nice! Great way to find that line. Glad I could help