stripe-python Support custom certificate bundle (Fix)

The Fix

pip install stripe==14.4.0a2

Based on closed stripe/stripe-python issue #501 · PR/commit linked

Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.

Open PR/Commit

@@ -1,5 +1,7 @@
 from __future__ import absolute_import, division, print_function
 
+import os
+
 # Stripe Python bindings

fix.md

Option A — Upgrade to fixed release\npip install stripe==14.4.0a2\nWhen NOT to use: This fix should not be used if the application does not require custom SSL certificates.\n\n

Why This Fix Works in Production

Trigger: Users were unable to connect through proxies requiring custom SSL certificates.
Mechanism: The library did not allow users to specify a custom CA bundle for SSL connections
Why the fix works: Adds support for providing a custom CA bundle by setting `stripe.ca_bundle_path`, allowing users to pass their own certificate bundle or extra certificate when using a proxy. (first fixed release: 14.4.0a2).

Production impact:

If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

The library did not allow users to specify a custom CA bundle for SSL connections
Production symptom (often without a traceback): Users were unable to connect through proxies requiring custom SSL certificates.

Proof / Evidence

GitHub issue: #501
Fix PR: https://github.com/stripe/stripe-python/pull/503
First fixed release: 14.4.0a2
Reproduced locally: No (not executed)
Last verified: 2026-02-09
Confidence: 0.85
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.86

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

“Implemented in 2.15.0. Users can now set stripe.ca_bundle_path to use their own CA bundle.”

@ob-stripe · 2018-11-30 · source

Failure Signature (Search String)

Users were unable to connect through proxies requiring custom SSL certificates.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
Users were unable to connect through proxies requiring custom SSL certificates.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
Users were unable to connect through proxies requiring custom SSL certificates.

What Broke

Users were unable to connect through proxies requiring custom SSL certificates.

Why It Broke

The library did not allow users to specify a custom CA bundle for SSL connections

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install stripe==14.4.0a2

When NOT to use: This fix should not be used if the application does not require custom SSL certificates.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Fix reference: https://github.com/stripe/stripe-python/pull/503

First fixed release: 14.4.0a2

Last verified: 2026-02-09. Validate in your environment.

When NOT to Use This Fix

This fix should not be used if the application does not require custom SSL certificates.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Add a TLS smoke test that performs a real handshake in CI (include CA bundle validation and hostname checks).
Alert on handshake failures by error string and endpoint to catch cert/CA changes quickly.

Version Compatibility Table

Version	Status
14.4.0a2	Fixed

Related Issues

No related fixes found.

Cluster: stripe-python:configuration-error stripe-python hub stripe-python best practices All hubs All clusters

Related clusters: Data consistency Other Payments

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.