Find the Stripe failures a retry won’t fix.
A declined card is normal. A renewal that fails on every retry because its saved Stripe customer no longer exists is not.
With the official WooCommerce Stripe Payment Gateway plugin, Operanse separates ordinary declines from broken saved payment details and store configuration faults, names the affected orders and shows Stripe’s error code, from the first affected order.
This page is the Stripe detail. For orders, payments across every gateway and what an outage costs, see order and payment monitoring.
Stripe reasons, failure-rate monitoring and revenue estimates are on Monitor ($39/site/month) and Insight ($99). The trial is 14 days of Insight.
- statement
- Stripe refused 3 subscription renewals with “resource_missing”. An ordinary card decline is not reported this way.
- orders
- #48213, #48190, #48177
- kind
- renewal, WooCommerce Subscriptions
- what to check
- the customer’s saved payment details; a retry alone will fail again
Which failures need you, told apart
After a migration, a Stripe account change or a plugin switch, a few customers can fail on every renewal without moving the overall failure rate at all.
Ordinary declines are counted, not alerted one by one
Insufficient funds, expired cards and bank refusals happen. Operanse watches their rate against what is normal for this store at this hour.
Broken saved details are reported from the first order
A missing Stripe customer or payment method needs attention even if only one order is affected. You get the Stripe code and the WooCommerce orders to open.
Configuration faults are reported
An invalid API key, an account restriction, mixed live and test settings or a payment method that is not activated are kept apart from shopper-side declines, with what to check.
Temporary Stripe-side errors are kept separate
They are not confused with a broken saved detail or a store fault. A code that has not yet been classified is reported once, so it is seen.
One cause, one notification
For failures that should not happen, the email and Slack finding arrives within about ten minutes of the first affected order. Thirty more orders failing for the same cause do not produce thirty more notifications.
The incident becomes critical when a configuration fault affects five orders in an hour, or broken saved details affect ten. Critical alerts also go by SMS and WhatsApp, according to your alert settings and plan limits.
Operanse does not make the repair or retry the payment.
Keep Stripe’s dashboard. Add the store’s side.
Stripe shows payments, decline rates and fraud screening. Operanse adds which WooCommerce orders and subscriptions are affected, whether the failures are unusual for this store, which attempts are retries, the estimated revenue at stake and what changed shortly before. Calls from the site to Stripe’s servers are watched too: if half or more of at least five calls fail over 15 minutes, that is critical.
Clear limits on what Operanse sees
Reason codes need the official plugin
The WooCommerce Stripe Payment Gateway plugin supplies Stripe’s short codes, such as
insufficient_funds,card_declined,resource_missingandinvalid_api_key. Other Stripe plugins and WooPayments still get failure counts, rates, retries, order monitoring and the calls to Stripe’s servers, without the codes.Some later failures have no reason code
Failures Stripe reports to the store later by webhook, including some delayed payment methods, are counted without Stripe’s reason.
Incoming Stripe webhooks are not monitored
It cannot tell you whether Stripe’s webhooks to your store are failing. Your store’s own outgoing WooCommerce webhooks are a separate check.
No card numbers, no customer details
Only short codes, order numbers and counts are collected from Stripe failures; never Stripe’s full message, customer or card details. The agent is read-only. Security
Set it up
Create an account at app.operanse.com and add your store.
Install Operanse Agent from WordPress.org and paste the pairing token.
Keep the official WooCommerce Stripe Payment Gateway plugin active to include Stripe’s failure reasons.
Fault reports based on Stripe’s reasons need no learned baseline. Comparisons with this store’s normal failure rates start once it has about 48 hours of history; a weekly pattern takes about two weeks.
Watch, the free plan, alerts when the store can no longer take payment and when subscription renewals fail; the Stripe detail above is on Monitor and Insight. Pricing
Frequently asked questions
What does resource_missing mean for a failed renewal?
Stripe could not find a referenced resource. For a renewal, that can be a saved Stripe customer or payment method that no longer exists. Retrying alone will not repair it; check the order’s saved payment details.
Will I get an alert for every declined card?
No. Ordinary declines are counted. Operanse alerts on unusual failure rates and reports broken saved details and configuration faults separately.
Does it work with WooCommerce Subscriptions?
Yes. Renewals are watched separately from checkout, retries are kept apart from first attempts, and broken saved details are reported from the first affected order.
Can it fix a failed renewal?
No. It names the affected orders and what to check. It does not change subscriptions, update saved payment details or retry charges.
Find the failures a retry won’t fix.
Know which orders need attention, what Stripe reported and the estimated revenue affected. Start with 14 days of Insight.
Stripe is a trademark of Stripe, Inc. Operanse is not affiliated with or endorsed by Stripe.