#leanvitale_api
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/1368953909686829128
๐ 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.
- leanvitale_api, 2 days ago, 6 messages
- leanvitale_api, 6 days ago, 20 messages
- leanvitale_api, 6 days ago, 9 messages
๐งโ๐ป How to format code on Discord
Inline code: wrap in single backticks (`)
This:
The variable `foo` contains the value `bar`.
Will turn into this:
The variable
foocontains the valuebar.
Code blocks: wrap in three backticks (```)
Also, you can specify the language after the first three backticks to get syntax highlighting.
This:
```javascript
function foo() {
return 'bar';
}
```
Will turn into this:
function foo() {
return 'bar';
}```
Notes about **code blocks**:
- Specifying the language is optional (e.g., you can omit `javascript` in the example above)
- If you don't specify the language you won't get syntax highlighting
- When you're inside a code block (after you type \`\`\`) the `Return`/`Enter` key will add a new line instead of sending your message
- Once you end the code block `Return`/`Enter` works normally again
You can [read more about message formatting on Discord's website.](https://support.discord.com/hc/en-us/articles/210298617)
2025-05-05 15:58:55 --> refund.created [evt_3RKLjFLAwobXIPtp1PjjvmYb]
2025-05-05 15:58:55 <-- [200] POST http://localhost:3000/stripe/webhook/payout [evt_3RKLjFLAwobXIPtp1PjjvmYb]
2025-05-05 15:58:55 --> charge.refunded [evt_3RKLjFLAwobXIPtp1arMhF7h]
2025-05-05 15:58:55 <-- [200] POST http://localhost:3000/stripe/webhook/payout [evt_3RKLjFLAwobXIPtp1arMhF7h]
2025-05-05 15:58:56 --> refund.updated [evt_3RKLjFLAwobXIPtp1PrgVcnE]
2025-05-05 15:58:56 <-- [200] POST http://localhost:3000/stripe/webhook/payout [evt_3RKLjFLAwobXIPtp1PrgVcnE]
2025-05-05 15:58:56 --> charge.refund.updated [evt_3RKLjFLAwobXIPtp1pOn4p9I]
2025-05-05 15:58:56 <-- [200] POST http://localhost:3000/stripe/webhook/payout [evt_3RKLjFLAwobXIPtp1pOn4p9I]
2025-05-05 16:00:01 --> refund.failed [evt_3RKLjFLAwobXIPtp1GGteCP2]
2025-05-05 16:00:01 <-- [200] POST http://localhost:3000/stripe/webhook/payout [evt_3RKLjFLAwobXIPtp1GGteCP2]
2025-05-05 16:00:01 --> charge.refund.updated [evt_3RKLjFLAwobXIPtp17XW32CX]
2025-05-05 16:00:01 <-- [200] POST http://localhost:3000/stripe/webhook/payout [evt_3RKLjFLAwobXIPtp17XW32CX]
Hey there, taking a look into this
It doesn't appear that you use the refund failure test card
Have you observed this with any other test refunds?
Broadly speaking, yes this can happen, since we generally expect refunds to succeed but sometimes they are rejected as explained here:
https://docs.stripe.com/refunds#failed-refunds