Will stripe-python v15 break your code?

Paste a Python file. The checker flags the lines that fail on stripe-python v15 and v16 and shows the fix for each one.

What it checks

• Dict methods on Stripe objects: .get(), .keys(), .values() and .items(), including on nested fields like metadata
• dict(obj), json.dumps(obj), looping over an object's keys, and isinstance(obj, dict)
• Removed in v15: to_dict_recursive() and stripe_id, plus decimal fields compared with strings
• Removed earlier or in v16: stripe.error, stripe.Reversal and StripeObject.request()

Each result is labeled. Will break means the pattern fails on v15 no matter what. Likely means the value comes from a Stripe call or webhook in the same file. Check means the variable's name suggests a Stripe object, such as a function parameter called event, but the checker can't see where it came from.

What it can't see

It reads one file at a time and matches common patterns, so it misses Stripe objects passed in from other modules under unrelated names, and it can flag a variable that only looks like one. The reliable check is a test that builds a real Stripe object and fails on v15 before your fix. The upgrade guide shows how to write one in a few lines.