#daniele_webhooks
1 messages ¡ Page 1 of 1 (latest)
đ 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/1301225135587725344
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello! No, if a Dispute is updated, we'll generate and send a charge.dispute.updated Event. What exactly do you mean by "literally every character added or removed when writing the texts" though? Writing the texts where?
dispute created -> we receive 1 webhook when the customer opens it
charge.dispute.updated is also used when the seller starts replying to the dispute
so writing the content about why they should win it etc
and what happens with that is that stripe sends us one webhook events for every char sent
example:
"Provide more information ...."
This dispute is
one webhook sent
"Provide more information ...."
This dispute is wrong
5 webhooks sent (one for each letter of "wrong")
lol
see the list of webhook events ahah
Regarding, "so writing the content about why they should win it etc" where are you writing that content?
disregard that, it's an example
take a look at the link
the webhook events sent in correlation to that payment for charge.dispute.updated
and you can see what i'm talking about
Ah, so you're writing this text in the Stripe Dashboard. That's what I was trying to clarify. I didn't know if you were writing this in your own UI, a third-party system, etc.
I see what you mean now, give me a few minutes...
we're a platform so in this case it's one of our connected accounts writing through the stripe dashboard yep
It looks like this is an issue on our end. I'll flag it internally, and hopefully we'll be able to improve it.
thank you