DeclinePilot for WooCommerce

Diagnose failed payments. Recover the right orders.

Turn failed WooCommerce payments into an actionable recovery queue with cause-aware guidance, conservative safety controls, native WooCommerce retry flows, gateway-health context, and tracked recovered-revenue attribution.

WooCommerce 11+PHP 7.4+HPOS-awareLocal-firstNo separate checkout
Core workflow

Failure → decision → recovery

DiagnoseNormalize supported failure evidence
PrioritizeClear next-best-action queue
RecoverWooCommerce Pay for order
MeasureTracked retry attribution
Why it exists

Stop treating every failed payment the same.

A failed order may need customer action, merchant investigation, a different payment method, more time—or no outreach at all. DeclinePilot is designed to separate those situations instead of pushing every failure into the same recovery sequence.

A

Failure intelligence

Normalizes supported evidence into merchant-friendly categories such as insufficient funds, authentication required, issuer/customer decline, fraud/risk block, gateway/service issues, store configuration problems, rate limits, and unknown failures.

B

Next Best Action

Surfaces actions including merchant action first, high-value opportunity, customer action needed, recover now, wait before retry, and protected.

C

Gateway health context

Compares recent failures with a prior baseline and presents operational states such as Learning, Healthy, Degraded, and Critical without pretending uncertainty is certainty.

Recovery without a second checkout

Bring the shopper back to WooCommerce.

Tracked recovery links return eligible shoppers to WooCommerce's native Pay for order flow. DeclinePilot does not create its own card checkout and is designed not to store card numbers, CVC values, payment tokens, raw gateway payloads, or full transaction IDs in its analytics tables.

Safety controls

  • Per-order message limit
  • Per-customer rolling frequency cap
  • Resend cooldown
  • Store-timezone quiet hours
  • Paid replacement-order detection
  • Fraud/risk suppression
  • Offline-payment exclusions
  • Subscription-renewal protection
  • Duplicate-payment protection
  • Stale scheduled-job invalidation

Measure what came back

DeclinePilot separates failed-payment exposure, recovery messages, tracked retries, later-paid orders, and retry-attributed recovered revenue.

Opening a recovery link alone does not count as a recovered payment. Attribution requires the shopper to enter the WooCommerce payment flow, submit a tracked retry, and later reach a paid state.

Privacy-aware operations

Keep diagnostics local.

DeclinePilot is designed to operate without a mandatory Rivenset analytics service or custom licensing server. Its local event and risk records avoid copied customer profile data and sensitive payment payloads.

Local records

Stores bounded operational fields such as order ID, gateway ID, amount/currency, normalized event or failure category, timestamps, and pseudonymous subject hashes where needed for safety limits.

Privacy tools

Includes WordPress personal-data export/erasure integration for DeclinePilot-held pseudonymous linkage and a merchant-configurable local event-retention window.

Support bundle

Provides a privacy-safe support bundle designed to exclude customer names, emails, addresses, order IDs, site URL, API credentials, payment tokens, full transaction IDs, raw gateway payloads, and custom recovery-email content.

Availability

Preparing for Woo Marketplace submission

DeclinePilot is currently in final submission preparation. Public purchase links will be added after marketplace availability is confirmed.