#nemanja_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/1277691713837858971
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
There are a number of decline test cards you can use here, but none that will give those exact mesages after being attached: https://docs.stripe.com/testing#declined-payments
I would recommend using the exising cards to test your workflow, starting at the failed payment step and progressing from there.
Do you have any suggestions on how we can test these scenarios since we have a way to test the other cases? These three cases are temporary in nature, and we attempt to process the payment two more times before blocking the card in our system.
You can attempt to make a payment to the Subscription using one of the other test cards that will fail and provide the expected errors. You'd just need to skip the step where you attach them to the customer, and instead use them to try to pay the outstanding invoice directly
We have a flow in our application that involves first attaching the card and then processing the payment. What you suggested is not an option for us because we are trying to perform integration tests.