#ajivrajani_unexpected
cloud lilyBOT
đ 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/1272607701460979743
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
rich vigilBOT
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.
- ajivrajani_api, 6 days ago, 21 messages
humble hearth
Here's the invoiceID I am talking about: in_1PhuGlDimYQqAlsH8oTZjgAJ
unreal ether
Looks like the Payment Method that was set as the default failed too many times, which caused Stripe to consider it invalid and not use it
humble hearth
Right. So an invalid payment method results in the invoice not being auto-finalized?
Attempting to charge the customer is separate from finalizing an invoice though, right? Or is my understanding incorrect here?
unreal ether
Correct, because finalizing an invoice is considered "preparing the Invoice for payment". If there's no valid payment method, then there's no reason to finalize it
humble hearth
Gotcha. Thanks for the clarification.
Have a wonderful rest of your week!