#jmschp_best-practices
junior valveBOT
👋 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/1316796784965718127
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- jmschp_best-practices, 3 hours ago, 6 messages
stoic reef
Hello
Can you share the Subscription ID that you tested with?
It sounds like you used payment_behavior: 'default_incomplete' here
In which case you would need to manually confirm the PaymentIntent.
grizzled solstice
sub_0QVERo2ALfsUTznjb4w3N9mc
stoic reef
Ah okay nevermind.
So yeah, actually the simplest thing to do here after you update the PaymentMethod is to use the /pay endpoint to attempt to charge the Invoice: https://docs.stripe.com/api/invoices/pay
grizzled solstice
I am not setting the payment behaviour. If I set it should it work?
without having to touch the invoice?
grizzled solstice
ok
stoic reef
The best way is to manually trigger the payment attempt after the update like I mentioned above
grizzled solstice
I really didn't want to touch the invoice now! 🙂
stoic reef
Yeah for this initial payment you need to manually retry it