#lliu_docs
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/1361780388157984858
đ 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.
- lliu_code, 5 days ago, 14 messages
Hello
As far as I know, we geolocate using the IP
Are you asking about payment flows and how payment methods are presented OR are you asking about a specific API?
does that mean when Payment Element is bootstrapped in a custerm's broswer, the IP of the customer is taken into the consideration of what payment method options to appear?
Yes
but it also depends on if you're using Dynamic Payment Methods OR Static Payment Methods when you create the Intent
can alaborate a bit?
Dynamic payment methods automatically load payment methods activated in your dashboard based on if customer meets the eligibility criteria - https://docs.stripe.com/payments/payment-methods/dynamic-payment-methods
how to force a dynamic payment methods or static payment methods? is that a setting in dashboard? or that is part of the payment intent creation param?
If you're on a newer API version then it's enabled by default. So if you don't explicitly pass payment_method_types -- then we by default use dynamic payment methods
If you're on an older API version then you can use automatic_payment_methods parameter to enable it - https://docs.stripe.com/api/payment_intents/create#create_payment_intent-automatic_payment_methods
i see. we are using 2024-06-20 ... that considered a new one?
Yup, that's recent enough