#alessio_webhooks
1 messages ¡ Page 1 of 1 (latest)
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.
- alessio_webhooks, 8 minutes ago, 21 messages
đ 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/1239720540772765716
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
A doubt has come to mind. Unfortunately my events are older than 30 days so I can't find them in the dashboard or with the list APIs, so sorry for bothering you again.
Am I right to assume that, no matter how the Refund object has been created, I will always find it in the charge.refunds list?
If so, how are the Refunds sorted in that list?
And one last question, when we receive the charge.refunded event, the list charge.refunds is already expanded?
That even will occur for refunds and partial refunds for transactions that resulted in money-movement. It won't work for uncaptured charges.
If so, how are the Refunds sorted in that list?
Stripe doesn't guarantee object ordering, but it would usually be in descending order by timestamp of creation
But if a PI is partially captured, and a Refund object is created later on, both the Refunds should be attached to the same Charge, right?
Yes
Thanks a lot, again!