#stevewestpalm_unexpected

1 messages ยท Page 1 of 1 (latest)

agile mulchBOT
#

๐Ÿ‘‹ 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/1224711282767167541

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

quartz acorn
modest turtleBOT
upbeat ore
#

Hi ๐Ÿ‘‹ can you tell me more about your concern and share the IDs of related objects? I'm a little confused because customer accounts are not a concept in Stripe and therefore can't be canceled.

If you're talking about a Subscription that has moved to a canceled status, then nothing can restore that Subscription. canceled is a terminal state for Subscription objects.

quartz acorn
#

Regarding the subscription, in the event log it moved to a canceled status due to nonpayment? How was the customer able to be charged after updating their payment details? Was this just a "back payment" on an outstanding invoice?

upbeat ore
#

I'm not sure, did those payments come from code you're running or an automatic process? Can you share the ID of one of the payments you're referring to?

quartz acorn
#

Is this what you are looking for?

upbeat ore
#

Not really, that just shows the Subscription being cancelled.

Previously you said:
"How was the customer able to be charged after updating their payment details?"
I'm looking for clarity on how that payment was created. Is that a payment that you created and processed?

quartz acorn
#

Sorry. The payment was created in Stripe by us for a subscription that the customer initiated with our company. Now that I understand that canceled is a terminal status, I think the solution is to extend the payment retries before automatically canceling the subscription. Is there a recommended industry standard for payment retries before cancel that should be set in Stripe?

upbeat ore
#

No, I don't have specific recommendations on what retry logic you should leverage. I believe that may vary based on your business needs and what industry you're in, and that you're best suited to determine that.

quartz acorn
#

Thanks for your help. I appreciate it!