#s123317_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/1478132773263900712
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello! Taking a look ๐
Hi! Thank you.
this is an example. we have hundreds of blocked payment when usualy for a campaign of 4.5 milions there is 13k blocked.
Stripe Salesforce Connector examples. Contribute to stripe/salesforce-connector-examples development by creating an account on GitHub.
Hi @low rapids - if you have a question, please start your own thread in #help ๐
@void bloom It looks like these payments are legitimately being blocked by Radar. This isn't something my team specializes in so please reach out to https://support.stripe.com/contact for help. Thank you!
I requesteed support also. tomorrow we will try a few things. Its complicated to know how to feed the radar for off session payment.
Anyone online that could help with Radar ?
Unfortauntely no, support is the only team that can help with this.
Thank you
What do you mean by "how to feed the radar"?
I mean i see there is no information. For exemple with CC payment with have IP... but when it's automated, the system do not return IP of the customerr, seems not everytime there is an address with the payment methode, we also don't use radar for future use. Maybe this could help? Tomorrow we are planing to add adress element to force linking biling adress to the payment methode et to activate radar for future and then check. But maybe the set up we have is already good. We did it with proserve stripe team 2 years ago. I don't know if there was significant change since then of this procedure.
Most of errors are "unknown risk"
It's unlikely your inegration (e.g. the elements you're using) is causing this. Radar is suspecting something fraudulent and support should be able to investigate further. Good luck!
thank you