#marve_api

1 messages ¡ Page 1 of 1 (latest)

limber latchBOT
#

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

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

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.

granite hinge
#

We're using chckout with embedded components btw

livid lodge
#

Hi, there is not a way to access this in the API/ events in Stripe. The IP address of the customer is something we collect client-side when a PaymentIntent is confirmed for instance. However, it's not surfaced anywhere in our API.

You can see their IP address, details about the browser the customer uses on your site. You could store that information on your end whenever someone buys something on your website. However, I would not be able to comment about the compliance implication so you'd want to talk to your legal team about that.

granite hinge
#

thanks, i figured (we were hoping not to store and pass directly to tax provider), and bank country? Is that available?

livid lodge
granite hinge
#

o sorry, my bad thanks again

#

Thats all

livid lodge
#

No worries, happy to help