#growvery-radar-payment
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- growvery, 32 minutes ago, 29 messages
Hi @solar pumice , we can only help with technical questions about our API here. So we can't help you with this. As noted in the previous thread, you'll need to work with our Support team on this issue.
I have a payment id and an example of issues is that, we are testing not sending IP address maybe hoping to get lower risk scores it is not working and even I did not send Ip address, Radar says IP address is associated with early fraud warning even though it is not passed at all
this is a separate issue
about sending ip
pi_3OUYDlEe25OxKjhD1OLgGWIR this payment id, I did not pass IP but Radar says IP is passed
Yeah sorry I'm not sure why the Dashboard shows that. It is possible that is just a Dashboard bug as I'm not seeing any IP Address passed since this was a server-side request and you did not provide an IP yourself.
Overall I understand this is frustrating but we really only focus on the API and integration questions here. We know ~nothing about the inner workings of Radar so you do have to work with our Support team on this.
yes but this is the main problem, even thought I did not pass anything other than name, card and name it blocked it with 88 risk score and there is no logical reason to block this card, in my account radar is blocking everyone with high risk score no matter what I passed, I pass everything possible it blocks, I pass small info they blocks, no way around it
Real quick - I deleted that screenshot since it had some personal address information it
I also want to add - when I look at the payment on my end it doesn't say quite the same thing (I don't see it say "The IP address is associated with a previous early fraud warning")
So really I think the next step for you is to push on support to take a closer look at why it was blocked