The Fix
pip install stripe==14.4.0a2
Based on closed stripe/stripe-python issue #1428 · 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%.
@@ -1244,7 +1244,9 @@ def __init__(
kwargs = {}
if self._verify_ssl_certs:
- kwargs["verify"] = stripe.ca_bundle_path
+ kwargs["verify"] = ssl.create_default_context(
+ capath=stripe.ca_bundle_path
Fetch any resource via the HTTPX client 🤷
Follow the reproduction steps, confirm the failure, apply the fix, and repeat the same steps to verify the behavior changes.
Option A — Upgrade to fixed release\npip install stripe==14.4.0a2\nWhen NOT to use: This fix is not applicable if the application does not use the deprecated verify argument.\n\n
Why This Fix Works in Production
- Trigger: We are working towards a simplified SSL configuration API.
- Mechanism: Fixes a deprecation warning introduced in httpx 0.28 by updating the SSL verification method.
- Why the fix works: Fixes a deprecation warning introduced in httpx 0.28 by updating the SSL verification method. (first fixed release: 14.4.0a2).
- 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
- Production symptom (often without a traceback): We are working towards a simplified SSL configuration API.
Proof / Evidence
- GitHub issue: #1428
- Fix PR: https://github.com/stripe/stripe-python/pull/1431
- First fixed release: 14.4.0a2
- Reproduced locally: No (not executed)
- Last verified: 2026-02-08
- Confidence: 0.95
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.64
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“Hi! Thanks for bringing this up. We'll investigate a fix to suppress this warning.”
Failure Signature (Search String)
- We are working towards a simplified SSL configuration API.
- For users of the standard verify=True or verify=False cases, or verify=<ssl_context> case this should require no changes. The following cases have been deprecated...
Copy-friendly signature
Failure Signature
-----------------
We are working towards a simplified SSL configuration API.
For users of the standard verify=True or verify=False cases, or verify=<ssl_context> case this should require no changes. The following cases have been deprecated...
Error Message
Signature-only (no traceback captured)
Error Message
-------------
We are working towards a simplified SSL configuration API.
For users of the standard verify=True or verify=False cases, or verify=<ssl_context> case this should require no changes. The following cases have been deprecated...
Minimal Reproduction
- Fetch any resource via the HTTPX client 🤷
What Broke
Users experience deprecation warnings when using the HTTPX client with SSL verification.
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install stripe==14.4.0a2
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/1431
First fixed release: 14.4.0a2
Last verified: 2026-02-08. Validate in your environment.
When NOT to Use This Fix
- This fix is not applicable if the application does not use the deprecated verify argument.
Verify Fix
Follow the reproduction steps, confirm the failure, apply the fix, and repeat the same steps to verify the behavior changes.
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.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.