Skip to content

Failed payment recovery for WooCommerce

Travis SteffenBy Travis Steffen · Co-Founder, GTMReviewed by Calum EwingUpdated 3 min read
Summarize with AI

Quick answer

WooCommerce recovers failed subscription payments through plugins like WooCommerce Subscriptions, which retries the card on a fixed, store-configured schedule and emails the customer to update their card. There's no native SMS, no phone, and no human follow-up, so dunning alone recovers ~20%. Revatto detects the failed payment, then runs email + SMS + human outreach under your brand that drives the customer back to update their card in WooCommerce — a human team recovers 60–85%+. It's done for you at 20% of the first recovered payment, $0 setup, $0 monthly, cancel anytime.

The gap WooCommerce leaves open

What WooCommerce recovers on its own

  • WooCommerce core handles the checkout and order; failed-payment retry behavior comes from a subscriptions plugin, most commonly WooCommerce Subscriptions.
  • WooCommerce Subscriptions retries a failed renewal on a fixed, store-configured schedule and marks the subscription on-hold until the payment clears.
  • The customer is emailed a link to update their payment method; recovery communication is email-only.
  • There is no native SMS, phone, or human outreach, and no win-back once the configured retries are exhausted.
  • WooCommerce stops at: WooCommerce's recovery comms are email-only — a renewal-failed email, but no SMS and no phone outreach.Revatto adds: Email + SMS + a human recovery specialist, all reaching out under your brand.
  • WooCommerce stops at: Plugin retries run on one fixed, store-configured schedule applied to every customer.Revatto adds: AI-timed outreach plus cross-client learning from millions of recovered payments, tuned to when a customer actually reconnects.
  • WooCommerce stops at: Once the configured retries are exhausted, the subscription goes on-hold or cancels with no further follow-up and no win-back.Revatto adds: Recovery continues past the last plugin retry, with human follow-up that actually reconnects the card.
  • WooCommerce stops at: Recovery is left entirely to a plugin you configure and maintain yourself — another tool to run.Revatto adds: A managed team runs the whole outreach sequence for you and drives the customer back to update in WooCommerce.

How Revatto recovers failed WooCommerce payments

  1. 1
    Detect the failureRevatto picks up the failed WooCommerce subscription payment the moment the renewal charge fails and the subscription goes on-hold.
  2. 2
    Read the declineRevatto maps the available decline detail to a recovery action so a soft, retry-later decline is handled differently from one that needs the customer.
  3. 3
    Reach the customerEmail + SMS + a human recovery specialist contact the customer under your brand — the channels WooCommerce's plugin email doesn't cover.
  4. 4
    Drive the card updateRevatto guides the customer back to update their payment method in WooCommerce — because Revatto does not re-charge the card on WooCommerce, recovery runs through outreach, not a silent re-attempt.
  5. 5
    Stop on successWhen the renewal clears in WooCommerce, Revatto ends the sequence automatically — no stray outreach.

How a WooCommerce decline maps across stacks

A do-not-honor decline on WooCommerce — ISO 05 (a generic issuer decline, whatever processor sits behind your store). Recovery looks the same across every stack Revatto runs on — here is how the same issuer decision is named on each.

ISO 8583
Code05
CalledDo Not Honor
Stripe
Codedo_not_honor
CalledDo not honor
Braintree
Code2000
CalledDo Not Honorgeneric issuer decline
Authorize.net
Code5
CalledDo not honorresponseReasonCode 5
NMI
Code201
CalledDo not honor
Chargebee
Codedo_not_honor
CalledDo not honor
Recurly
Codecall_issuer
CalledCall issuer
IxoPay
Code05
CalledDo not honorISO 8583 adapterCode 05 (refer to issuer)
Shopify
CodeDO_NOT_HONOR
CalledDo not honor
Whop
Codedo_not_honor
CalledDo not honornormalized — no processor-specific code (free-text categorized)
Fanbasis
Codedo_not_honor
CalledDo not honornormalized — matched by substring rule, no processor-specific code

See what Revatto would recover from WooCommerce

Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.

See Your Recovery Potential

Frequently asked questions

Recovery, done for you

The same managed recovery layer runs on every stack — including WooCommerce. Here is what it has recovered for our clients.

$55M+ ARR

Recovered for our clients

65,000+

Payments recovered

54%

Average recovery rate