#madmark00178_checkout

1 messages · Page 1 of 1 (latest)

eternal mesaBOT
#

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

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

cosmic summitBOT
#

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.

reef lava
#

Hi 👋 do you have more context or details about what you're referring to? Are you able to reproduce this behavior in testmode, and/or can you share the ID of a Checkout Session where you saw this behavior?

cosmic summitBOT
eternal mesaBOT
#

madmark00178_checkout

shrewd surge
#

I cant reproduce the issue in test mode, its working totally fine in my dev environment

#

I guess i should just ask, if someone checks out with a credit card and it goes through, is there any reason their status would go to 'incomplete' or 'incomplete_expired'

unborn kiln
#

👋 hopping in here since toby has to head out soon

#

I assume you're talking about the stsatus of a Subscription? The only reason the Subscription would be in that state is if payment didn't actually complete succesfully

#

If you have specific object ID examples feel free to share them and I can take a closer look

shrewd surge
#

Yeah one sec

#

As an example, here's a customer who had the problem: cus_PhS3zyOPOtlLqV

#

That one has some clear issues during payments actually, lets look at this one: cus_PhQKzFOoYliBPy

#

Can you look at a customer id like that or no

unborn kiln
#

Yup those customer IDs work!

#

Can you clarify where or at what point you're seeing incomplete/incomplete_expired? For cus_PhQKzFOoYliBPy I see that they have an active Subscription with status: trialing and I'm not seeing anything about incomplete

shrewd surge
#

I don't actually see when its happening because my webhook updates my DB straight away. i have to put in some debug statements to figure this out but i wanted to check if on your side you can see if there was ever a status of incomplete sent out

unborn kiln
#

Statuses of incomplete and incomplete_expired are possible when you work with Subscriptions, but at least for these customers they're being created immediately with status: trialing

shrewd surge
#

Okay

unborn kiln
#

I'd guess that something is wrong with the update calls to your DB or maybe you're not handling a specific case in your webhook handler code

shrewd surge
#

K I’ll do some more research

#

Just so I’m sure, what should my site be allowing/disallow if someone’s status is incomplete or incomplete expired

#

Just let them access the billing portal to fix a payment?