#daniele-de-benedetto_best-practices
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/1235503650340606032
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
What specific issue are you seeing with Radar and off-session payments?
i want to know if there is a way to avoid to trigger radar on certain payment, there is no reason to trigger the radar on the second payment on the same card
OK, but what specifically do you mean by 'trigger the Radar'? What are you seeing that is unexpected?
example i collect the first payment with off session and radar allow it, after some times i retrigger a payment intent via api on the same card, and radar blocks it, i ask if there is a way to avoid radar on those type of 'future' payments
Can you share an example of a blocked payment?
In these particular cases, no you can't prevent Radar from blocking those payments
ok why? i have already checked the card and the customer the first time that i have collected the payment, is useless for me to doesn't collect the money the second time, it's a loss
also i pay the fee for every transaction...
The clue is in the decline code on the payment: fraudulent
Beyond that I can't say anything else why it was blocked
ok but the same card one month ago was fine pi_3P0cz5G0HkO3ZPnp13UmDAPu
there is a way via api to avoid the radar check ?
Afraid not in this scenario
in general ?