nolan-thach-nguyen_webhooks

[manic dove]

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

📝 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.

• nolan-thach-nguyen_docs, 33 minutes ago, 8 messages

[cobalt fractal]

👋 If a subscription payment fails, we don't automatically create a new subscription, so is this something you have set up? Where you have code to create a subscription when an event like this is triggered?

[prime trench]

If that, let me check my code again. Can you answer the second question - what are possible reasons for the payment failure with stripe payment element?

[cobalt fractal]

If you can provide an example of a payment failure, I can take a look, but in general, a payment method isn't guaranteed to succeed for every payment after it has been initially entered by the customer

In relation to the new subscription that was created, I can see that it does indeed appear to have been created from an API call: https://dashboard.stripe.com/acct_1GnG4QFvG2PBfrpS/logs/req_xxI0JivUAmdppR

[prime trench]

Seem so, I'll check my code. Thank again!