#titani0us - IP override
noble cobalt
It defaults to our backend server. We've processed thousands of transactions this way over recent years, but thought fraud detection capabilities in Stripe would likely serve us better if we could pass the client ip instead.
prime jungle
How are you passing the IP currently?
Or where is the IP being stored that you would like the customer IP be stored?
noble cobalt
We aren't explicitly passing it at all. It defaults to the ip associated with our production server.
prime jungle
Where are you seeing this IP?
I am happy to look in to this but am not immediately familiar with where this IP info is
noble cobalt
In the API docs you can see client_ip in the response object after creating a charge or customer card token: https://stripe.com/docs/api/tokens/create_card
In the Stripe UI, you can also see the ip address associated with charges or related charges.
For us it's always our server ip. Years past when our account was new we had to create a rule in radar to approve the charge if it came from our server ip address (which was explicitly specified in the rule).
prime jungle
Ah thank you for the clarification on that. I will ask amy colleagues about this as I am not immediately sure if that is overridable
noble cobalt
Cool, my gut says probably not but I thought we would at least ask since it seems as though the ip address is considered in Radar checks. Thanks!
prime jungle
If you are handling these PANs server side we may have something for you. If you describe your situation to our support team, they can see if that solution will work for your account https://support.stripe.com/?contact=true