#felipe_unexpected
tropic tinselBOT
👋 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/1384637135490912389
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
tight beacon
Hi, can you share more ? Can you add more about your business use case? What integration document are you using? We document how subscriptions work here: https://docs.stripe.com/billing/subscriptions/overview
fresh stream
sure. I have this stripe subscription integration for a couple of months now
users pay for parallel devices as subscription
and for some reason when their payment fails and they pay for it afterwards, their subscription is finished and a new one is created
tropic tinselBOT
pliant hearth
👋 taking a look
Okay so for the example you shared above, sub_1R25q8Jggz2YjwQBarjx7usr, it looks like it was deleted via a Dashboard request: https://dashboard.stripe.com/logs/req_1zIARMkCxp1J1G
So that was an action that you or someone with access to your account took directly on that Subscription
fresh stream
hmm, is it possible that this was done via api?
pliant hearth
No the cancellation was specifically done via the Dashboard, you can see the Dashboard user that canceled it via the request I shared above.
pliant hearth
Sure thing
fresh stream
the problem is: the new subscription is created, and the other one keeps being reatempted
instead of just counting as a payment suceeded on the first subscription
it creates a new one
so a girl from the team cancelled it
the problem from what I see is that it keeps creating new subscriptions
instead of fixing the exisitng ones
when a payment succeeds after a failure
pliant hearth
Not sure what you mean by that... a Subscription doesn't just get created randomly, nor does Stripe create Subscriptions for you.
For the second Subscription above, sub_1ROQJ0Jggz2YjwQBJwAlOAVk, it was created due to the completion of a Checkout Session, specifically the Checkout Session generated by this request: https://dashboard.stripe.com/logs/req_TWMmeyYNjqGQwa
So that was done by one of your customers completing your checkout flow
fresh stream
so the same customer created a new subscription
instead of paying the one that failed?
pliant hearth
I can't tell you that -- I can only tell you that a customer went through the Stripe Checkout flow (likely redirected from your website) to create sub_1ROQJ0Jggz2YjwQBJwAlOAVk
fresh stream
alright