#sayori_docs

1 messages ¡ Page 1 of 1 (latest)

dense nicheBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1253570631304351794

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

signal current
#

I completely understand if there's documentation that explains error objects can't have expanded fields - but I haven't seen that explanation in the docs yet. Am I missing something? Or is this an unintended bug?

lusty stag
#

It's not a bug, this is expected behaviour. I'll pass on the feedback to see how we can make it clearer in our docs

#

Our docs do share how to retrieve the original Charge object for a payment failure though : https://docs.stripe.com/error-handling if you want to use that as reference for your integration. From that, it's implicit that an error object can't be expanded

Catch and respond to declines, invalid data, network problems, and more.