#mrxbox98_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/1242208403158470819
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Unfortunately not at the moment. The two ways to do this would be to:
- Make a similar check on your client and display an error based on that
- Your server can check
outcome.ruleon the decline, with that you can confirm that that is why we blocked the charge. https://docs.stripe.com/api/charges/object#charge_object-outcome-rule
I understand that neither of those are ideal, but those are the typical workarounds for this limitation. I will file or add to the feature request for this error, I definitely get how it would be a much better error
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Ok thank you