#walto_api

1 messages ¡ Page 1 of 1 (latest)

worldly lanternBOT
#

👋 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/1433446191714013204

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

sinful fog
#

hi, looking into this now

#

from what I can tell this error is particular to the bank used for the transaction. I'd recommend reaching out to our main support channel for more information on why this is occurring https://support.stripe.com/?contact=true

onyx sluice
#

The error itself isn't really important, I need to recreate it (or similar) on my dev environment so I can handle it, so looking for a way to trigger an ApiErrorException when I call create setupIntent

sinful fog
#

I see, unfortunately I'm not entirely sure what caused that error. we maintain a set of test account numbers that simulate various scenarios but I'm not sure which would correspond exactly. you could try pm_usBankAccount_riskLevelHighest and see if that matches

Use test cards to validate your Stripe integration without moving real money. Test a variety of international scenarios, including successful and declined payments, card errors, disputes, and bank authentication. You can also test non-card payment methods and redirects.

onyx sluice
#

Ya I tried that, unfortunately that returns a proper setupIntent and not an error response like we received on production. Sounds like there is not way to test for receiving an error on create SetupIntent, which is unfortunate.

sinful fog
#

agreed for that particular error. you can try reaching out to main support to see if they have more information on what causes the error and how to simulate it, but I'm not seeing a test scenario for that particular situation