dan_radar-metadata

[buoyant falcon]

👋 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/1230907997296005165

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[copper skiff]

Hello! Is there a reason you're passing in payment_method_data ? Typically you wouldn't need it if you were using an existing Payment Method

[bright willow]

I have passed the following :
"amount": "1100"
"capture_method": "manual"
"confirm": "true"
"currency": "USD"
"customer": "cus_Px64aJhDHocg86"
"metadata[env]": "stage"
"metadata[psp_order_id]": "204814********d*c2742b"
"metadata[public_psp_transaction_id]": "psp_trx_3daea4ce701fd9120e149b331a8c8e46"
"off_session": "true"
"payment_method": "pm_1P7BsJEKhObXxkvdJGICjfBD"
"payment_method_data[ip]": "8.8.8.8"
"payment_method_options[card][request_three_d_secure]": "automatic"
"return_url": "https://acs.solidgate-stage.com/api/v1/return-after-3ds/recurring/226448327/oregon/98daedb7dc22cdeb09eab825da9af07ac3aeddb6b2d1a7ba5e"
"statement_descriptor": "stripe_psp_aqa"

Is it because of the ip?

If yes, how can I pass an ip address of the user in request then?

[copper skiff]

Is there a specific reason you're doing that? Is it just for your own reference or for some other reason?

[buoyant falcon]

dan_paymentintents

[bright willow]

Do you mean ip? So that Radar works properly

[copper skiff]

Gotcha - let me check on something really quick

So as far as I can tell, there isn't a way to pass through payment_method_data[ip], but I believe your flow is supported with Radar Sessions (https://docs.stripe.com/radar/radar-session). The general idea would be that you create a Radar Session client-side (which should grab the IP address) and then you can pass in the Radar Session ID when you confirm the Payment Intent with the existing Payment Method

[bright willow]

We have a direct server-to-server integration, so we would not be able to open a radar session.

Please check if there are any possibility just to pass ip address in request.

Sometimes some functionality may be covered by gates on your side, so maybe there is a gate which allows to pass this parameter

[copper skiff]

Yeah that's what I was looking for earlier, but wasn't seeing anything that would fit what you need

[bright willow]

so it is not possible, right?

But that would be possible for first/ecommerce transactions, right?

as we pass payment_method_data with card data in request then

[copper skiff]

Yes, it'd be possible for the first transaction (when you're creating a new Payment Method)

[bright willow]

Okay, thank you!