#xaositect_api
fresh haloBOT
đ 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/1270765222399053884
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
stark sinew
Just to make sure I understand: succeeds on setup, fails for later payments when the user is on session, but succeeds for payments when the user isn't around?
faint river
Seems to be what happened here
It seems like maybe there was an offline gesture, maybe they called their bank and the bank retried?
stark sinew
Unfortunately we don't have a test card with that speciifc behavior. I think the closest you can get would be to set up a radar rule in test mode that rejects payments for some specific amount and use that for the payments you want to fail and use other amounts for the ones you would want to succeed
Is there a reason that our normal success/decline cards wouldn't be sufficient for testing here?
faint river
Well there's only one test card that one can apply to a customer that then declines
stark sinew
We do have a test card that can be saved successfully but declines for any payments we call it "decline after attaching" in our doc https://docs.stripe.com/testing#declined-payments
faint river
âď¸ yeah that one
stark sinew
Right, I am trying to understand what test you are running that that is not sufficient for. I may not be imaginning this correctly but I would think that simulating separate scenarios for an on session success, on session decline, off session success, and off session decline would mean that your integration could handle this scenario
faint river
Looking at the logs again, I'm not sure that my understanding of what is happening is correct
So... sorry for the trouble. I'm going to go look at these again and see if I can get a more accurate picture of what happened here.
It seems like it was an in-app gesture to re-attempt payment here https://dashboard.stripe.com/logs/req_pvaz7Xagl5NvMh
You can close this thread for now. Sorry again.
stark sinew
No worries, glad you were able to get a clearer picture of what happened.