#Lullaby - .NET client_ip
1 messages ยท Page 1 of 1 (latest)
hi there, just checking in on this! thanks
Hi ๐ I'm stepping infor @mighty storm
What API are you trying to provide this data to?
.net library from this API
using PaymentIntent
we got the API to work perfectly fine. we just need to know the method to submit a Client_IP as well since radar depends on it
Thank you!
@worthy fog we actively discourage doing this since it requires sending raw card details server-side which increases your PCI scope. You really should use Stripe.js instead
We have a gated feature that allows you to do what you are after but it's undocumented and it's not something most devs need. Has someone recommended that to you, what's the context?
Right now, we are trying to get radar to work. we understand if reactjs method is better we can move forward to that down the road but for now, however our DEV are unfamiliar with reactJS apps
so ideally we would like to get the API to work in the .net environment with client_IP submission for now
Yeah I strongly recommend not doing this
We have another "beta feature" where you can create a Radar Session client-side and associate it with your payment
OH. ok
Also, we don't require React at all, we have normal vanilla JS integrations
lets go
I really think you should put on your developers here, they should just use PaymentElement and Radar will work automatically
yes but you said your dev is unfamiliar with ReactJS
that is no issue
tell them to look at https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements&html-or-react=html that's the non React version
perfect
(it defaults to React which bothers me too since I don't know React either ๐ )
<script async src="https://js.stripe.com/v3/"></script>
i suppose thjis is what we are referring to
well that just loads Stripe.js, there's a lot more code that is needed after that
is there a specific doc that reference how we can reference the JS (token)? to the paymentIntent
yes i understand
That doc covers everything end to end in details though
ok
you don't "reference a JS token" at all, the flow is drastically different and better
1/ Create a PaymentIntent
2/ Client-side, render the PaymentElement and automatically confirm the PaymentIntent