testmode_charges_only: Stripe Subscription Fix
Root cause
Stripe returns testmode_charges_only when a live subscription flow is incorrectly using test-mode API credentials or objects, causing production renewal attempts to target resources that only allow test charges.
Symptoms
- • Live customers fail while internal test subscriptions still appear to work
- • Stripe logs show requests against test-mode objects from a production storefront
- • Subscription creation or renewal breaks after an environment or secret rotation
- • Merchants see no bank decline because the request never reaches live card processing correctly
How to fix it
Audit every Stripe API key source
Check your environment variables, secret manager values, and deployment settings for publishable and secret keys. Confirm that live checkout and live webhook handlers are both using live-mode credentials. Mixed environments commonly appear after staging values are copied into production during a release.
Open in admin →Verify object mode on affected requests
Inspect the failed PaymentIntent, SetupIntent, or customer object and confirm whether it exists in test mode or live mode. A live request cannot safely continue if it references a test-mode customer or payment method. Recreate the necessary billing objects in live mode once the correct keys are in place.
Open in admin →Redeploy and re-test production billing
After correcting credentials, redeploy the service and run a controlled live-mode verification on a real low-value payment path if your process allows it. Also validate that webhooks are pointed at the matching mode endpoint. Do not retry production subscriptions until keys, webhook secrets, and object modes are fully aligned.
Frequently asked questions
Why does testmode_charges_only usually appear after deployment changes?
Because the error is commonly caused by environment drift: a test secret key, webhook secret, or customer object is accidentally wired into a live deployment. Code can look correct while production still fails because secrets or referenced objects come from the wrong Stripe mode. Secret rotations, staging copyovers, and rushed releases are frequent causes.
Can I recover existing subscriptions after fixing testmode_charges_only?
Yes, but only after you confirm the live environment is fully clean. Any affected customers or payment methods created in test mode may need to be recreated in live mode before billing can resume. Once credentials and object modes match, you can trigger fresh live billing attempts or ask customers to reauthorize payment if necessary.
Detect this error automatically
Free cross-stack scan finds all billing errors in 60 seconds.
Run Free Scan →