#bean_best-practices
odd gladeBOT
đ 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/1352270141441708104
đ 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.
- bean_best-practices, 2 days ago, 8 messages
hoary sentinel
Hey there, do you have any examples payment intents or reuqests that encounter this error?
I'm not familiar with "ChargeStripe" so its not clear if this is something you can control or not based on how that platform operates, whether or not i can provide any guidance
That error text, as you quoted it, is not an error i'm familiar with as coming from Stripe's API