#scott_code
mystic edgeBOT
👋 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/1366630405570039921
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
solar frigate
Hi! The errors we typically show in the iFrame are customer facing errors. Some errors like processing_error are meant for the merchant so they may not appear in the iFrame.
At the moment, there isn’t a way to check whether an error message will or won't appear inline. You'll need to run tests to see which error codes appear in the iFrame.
However, I'll make sure to pass this as a feedback on to our team.
cloud arrow
Hi!
To be clear, I'm seeing that there are some customer facing messages which are not shown in the iFrame, such as when a test card is used in a live environment. In this case the iFrame shows no error, so we must report it outside the iFrame - but that means it will be duplicative of errors that are shown in the iFrame.
Thanks for your help
solar frigate
Using a test card in the live environment is a very specific use case, likely due to a merchant testing rather than a customer attempting to pay with a test card. This is why you won't see a customer-facing error for this.