#tsahnar_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/1434800380411379713
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hey! This seems to be a Risk evaluation issue
And the transaction is flagged due to an elevated risk of fraud
Could i get you to reach out to Stripe Support - https://support.stripe.com/contact , they'll be able to advise you on your question there!
I know this is a risk issue. But I would like to understand if I need to change something in my API integration. Are we passing the correct values?
Hey, could i get you to write in for this issue, this may require additional time to look into before we can provide any advice
I'm not sure whether adding the IP address to the mandate info would help here. But you can try this for yourself, to see whether the Radar rule is affected
Generally it's preferred to use one of the recommended integrations: https://docs.stripe.com/radar/optimize-fraud-signals
If you're creating payments from your backend for a user who isn't present, you can first collect a Radar Session for them, and then later pass in the Session ID: https://docs.stripe.com/radar/radar-session