#shimmmaz_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/1366790608856813649
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello, we do have a setting for turning Radar on for setup intents, you can enable that if you have not already. We have other anti-card testing measures that are always in place, but I see that the charge you provided got blocked by radar, so I am guessing your ask may include how to run radar sooner.
https://dashboard.stripe.com/test/settings/radar
That said, it looks like that payment failed for an on session payment, not a recurring one after the card had been saved
Hi! thanks for the support. how do I turn on radar for setup intentes
That page that I linked to has a toggle for on and off
I linked to the test page, but you can use the live version of your page to turn it on for your actual charges
https://dashboard.stripe.com/settings/radar
yep, found it, I think this would work.
I have another question. Is there a way to block cards that have a zip code in one locale and the ip is in a diff locale?
For example, this payment: https://dashboard.stripe.com/payments/pi_3RE23kJbPfCJyc411WpobbCu
We do have attributes for both in our supported attributes for rules so you could definitely define this as a radar rule
https://docs.stripe.com/radar/rules/supported-attributes#ip-address
https://docs.stripe.com/radar/rules/supported-attributes#address
Another question - do you think I should enable the 3D Secure authentication to help mitigate my issue?
We definitely reccommend supporting 3Ds in your integration in general. It is an anti-fraud measure and if you don't support it that means certain payments will just fail that could have otherwise succeeded if the user could have completed 3DS
oh I see. and what can be the impact of enabling it on customer UX?
That can depend on bank, type of 3DS etc. There is everything from completing something on their bank site to invisible captcha-like signals being sufficient to approve the transaction without additional intervention
Thank you very much for the help!