jesterp-ip-addresses | Stripe Developers | Page 1

edgy cradle Dec 13, 2021, 10:57 AM

#

Hello! We publish a list of IP addresses that api.stripe.com might resolve to: https://stripe.com/docs/ips#ip-addresses

Domains and IP Addresses

Ensure your integration is always communicating with Stripe.

sage iron Dec 13, 2021, 10:59 AM

#

<Gasp>... That's awesome! This has been a problem with other processors for me in the past... Hence the question. Thank you for that, I'm sorry I somehow missed this in the docs, and thank you.

#

Quick followup: am I right that if I admit that list of IPs i can use any of the widgets on your https://stripe.com/docs/payments docs? This is very good news for me if so, thank you again.

Payments

Find a guide to integrate Stripe's payments APIs.

edgy cradle Dec 13, 2021, 11:04 AM

#

Yep, the PCI-compliant Stripe.js components just wrap calls to those same APIs

sage iron Dec 13, 2021, 11:05 AM

#

I cannot find an emoji that sufficiently expresses my excitement. So, accept the text instead, thank you so much, you've made my day!

edgy cradle Dec 13, 2021, 11:07 AM

#

🥳

#

You will likely need to also add some domains to an allow-list: https://stripe.com/docs/ips#stripe-domains

Domains and IP Addresses

Ensure your integration is always communicating with Stripe.

sage iron Dec 13, 2021, 11:17 AM

#

The problem with domains is that you need a way to read them from the client, and since the point of TLS is to prevent you seeing that, that doesn't work. As a rule anyway, i'm wrong. We don't filter anything on the DNS request side to the clients so that should be okay. I'll put together a mockup today and check it out, I'll post back here if I hit a wall. Have a good one!

edgy cradle Dec 13, 2021, 11:19 AM

#

The main blocker you'd have is loading Stripe.js from the CDN (as you cannot host it locally)

#jesterp-ip-addresses