#ignasidedieu_webhooks
wet needleBOT
👋 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/1338846645877477478
📝 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.
- ignasidedieu_api, 36 minutes ago, 15 messages
- ignasidedieu_expanding-responses, 4 days ago, 37 messages
- ignasidedieu_api, 5 days ago, 17 messages
- ignasidedieu_docs, 6 days ago, 4 messages
hoary horizon
👋 happy to help
I see that my colleague answered your question earlier
anything specific I can help with?
hard cedar
Yes, this is a different issue.
hoary horizon
this guide https://docs.stripe.com/payments/payment-intents/asynchronous-capture#listen-webhooks shows you what events you should listen to to get the balance transaction object
hard cedar
Okay, so the only solution is to subscribe to charge.updated event
hoary horizon
you can change the capture_method to automatic instead of automatic_async the new default https://docs.stripe.com/api/payment_intents/create#create_payment_intent-capture_method but we don't really recommend that
due to latency issues when using the automatic capture
hard cedar
I've updated to "automatic" when creating the checkout_session
hoary horizon
and even with that you're still not getting the balance transaction?
hoary horizon
would you mind elaborating a bit more?
hard cedar
Sure sorry. We create are creating a Payment Intent object calling your endpoint POST /v1/payment_intents, after creating we receive a webhook of type payment_intent.succeeded where we try to get the Charge value and find that the "balance_transaction" is null
Oh sorry my bad, we are not setting the value to automatic when creating the payment_intent
For now probably we are gonna use this "automatic" approach. What are the inconvinients that we could experience?