#connor_best-practices
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/1217536022460502036
đ 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.
- connor_ach-integration, 5 days ago, 23 messages
It's easy to check our data against country, but region makes things difficult. As of right now, our best option is to check lat/lng against Geojson region data from Openstreetmaps. However, we would like to use Stripe's standard definition if it exists instead to maintain consistency and conformity
Hi, can you confirm how you're integrating with Stripe? Like, are you using Stripe Checkout, Payment Elements, or something else?
PaymentIntents API. The location data isn't really included in any of the payloads we send right now. Is there any way to pass Stripe an array of lat/lngs that the itinerary covers and shift the rejection responsibility to the API?
What are you using on the client side to collect the payment method details? I think we prohibit that on our end already. Is there a specific issue you're seeing?
I apologize for being a little vague, I can't give too many details about the product, so I'll provide an analog:
Given that you're asking about high-risk jurisdictions, you would need to talk to our Support team. Our support team will be able to assist you better than I can: https://support.stripe.com/contact
Let's say we're a hotel booking company that lets people see pricing for any hotel anywhere. For every hotel, we know the country and lat/lng. According to our Stripe contract, we need to reject booking of hotels within those restricted regions. However, as far as I know, Stripe doesn'r provide a way for us to check those hotel lat/lngs for whether or not they are in a restricted region
I'm afraid I can't help here, please reach out to our support team: https://support.stripe.com/contact