stripe-python Support a StripeClient and custom HTTP

The Fix

pip install stripe==14.4.0a2

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

Open PR/Commit

@@ -12,6 +12,7 @@
 api_version = None
 verify_ssl_certs = True
+default_http_client = None
 
 # Resource

fix.md

Option A — Upgrade to fixed release\npip install stripe==14.4.0a2\nWhen NOT to use: This fix is not suitable for users who rely on the existing top-level API key configuration without customization.\n\n

Why This Fix Works in Production

Trigger: As discussed in #40, a StripeClient (with an HTTP client) is a better pattern than one-off changes to support custom configuration. Here's a proposed API for…
Mechanism: Introduced a configurable default HTTP client for Stripe, allowing users to override the HTTP client used by the library
Why the fix works: Introduced a configurable default HTTP client for Stripe, allowing users to override the HTTP client used by the library. (first fixed release: 14.4.0a2).

Why This Breaks in Prod

Introduced a configurable default HTTP client for Stripe, allowing users to override the HTTP client used by the library
Production symptom (often without a traceback): As discussed in #40, a StripeClient (with an HTTP client) is a better pattern than one-off changes to support custom configuration. Here's a proposed API for how this will work.

Proof / Evidence

GitHub issue: #96
Fix PR: https://github.com/stripe/stripe-python/pull/180
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.75

Discussion

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

Jump to Sources Open on GitHub

“:+1: > I'd like to make this backwards compatible change, so I'm not proposing we change the current interface, only add the new StripeClient”

@danielchatfield · 2014-07-21 · source

“It's only better if your dealing with a single Stripe account. As soon as you need to handle more than one Stripe account or Stripe…”

@kyleconroy · 2014-07-21 · source

“> It's only better if your dealing with a single Stripe account. Is that not the vast majority of users?”

@danielchatfield · 2014-07-21 · source

“You're probably correct. I've been working on a Connect app recently, so the lack of support for multiple accounts has been on my mind.”

@kyleconroy · 2014-07-21 · source

Failure Signature (Search String)

As discussed in #40, a StripeClient (with an HTTP client) is a better pattern than one-off changes to support custom configuration. Here's a proposed API for how this will work.
I'd like to make this backwards compatible change, so I'm not proposing we change the current interface, only add the new StripeClient.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
As discussed in #40, a StripeClient (with an HTTP client) is a better pattern than one-off changes to support custom configuration. Here's a proposed API for how this will work.
I'd like to make this backwards compatible change, so I'm not proposing we change the current interface, only add the new StripeClient.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
As discussed in #40, a StripeClient (with an HTTP client) is a better pattern than one-off changes to support custom configuration. Here's a proposed API for how this will work.
I'd like to make this backwards compatible change, so I'm not proposing we change the current interface, only add the new StripeClient.

What Broke

Users were unable to customize HTTP client configurations leading to limitations in handling multiple Stripe accounts.

Why It Broke

Introduced a configurable default HTTP client for Stripe, allowing users to override the HTTP client used by the library

Fix Options (Details)

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

pip install stripe==14.4.0a2

When NOT to use: This fix is not suitable for users who rely on the existing top-level API key configuration without customization.

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/180

First fixed release: 14.4.0a2

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

When NOT to Use This Fix

This fix is not suitable for users who rely on the existing top-level API key configuration without customization.

Did This Fix Work in Your Case?

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

Prevention

Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Version Compatibility Table

Version	Status
14.4.0a2	Fixed

Related Issues

No related fixes found.

Cluster: stripe-python:payments stripe-python hub stripe-python best practices All hubs All clusters

Related clusters: Configuration error Data consistency Other

Sources

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

stripe-python Support a StripeClient and custom HTTP backends (Fix)