#tomas_code
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/1276061445515251794
đ 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.
- tomas_error, 1 day ago, 4 messages
hello! Can you share what's the expected behaviour here for that specific payment you mentioned was declined due to postal code block?
Hello Alex, well the expected behaviour is same as with test cases - either a success, or an error that could be caught, but neither has happened. We are not sure where the issue lies then
can you share the PaymentIntent id for the live example you mentioned? it'll have the prefix : pi_
My apologies, but I can't seem to find one. Could this be that we're looking at a setup_intent?
ah, sorry, my bad, if it's a setup_intent, seti_
Yes, so the seti is seti_1PnL70069X7Ht4l16el2iKmU
still looking, gimme a while
sorry about the wait, i think in this case, the situation is just that we don't include the exact reason why the card was declined in the SetupIntent for this