Read-only subscription forensics for WooCommerce
Reconcile what Woo expected with what the gateway did.
Surface missing, duplicate, orphaned, mismatched, and state-divergent renewals without touching payment or subscription data.
PURPOSE / BOUNDARY
WooCommerce subscription operators investigating revenue leakage or inconsistent renewal state across the store and payment provider.
BUYER CHECK / RECOGNIZE THE PROBLEM
WooCommerce subscription operators investigating revenue leakage or inconsistent renewal state across the store and payment provider.
Not for automatic payment recovery, dunning, refunds, charge capture, or direct subscription-state repair.
FROM MANUAL REVIEW TO OUTPUT
Store and gateway exports use different identifiers, status vocabularies, and timestamps. A one-off spreadsheet may find obvious misses but is difficult to rerun consistently or audit. RebillLens normalizes both sides, applies the same matching rules, and retains the evidence behind each anomaly.
Supply expected WooCommerce renewals and the corresponding provider transaction records.
Compare references, subscriptions, amount, currency, status, and dates within an explicit tolerance.
Triage missing, duplicate, orphaned, mismatched, and state-divergent records without changing money or orders.
INPUT / SAMPLE FIXTURE
Edit the sample if you want. This preview is processed in memory and is not saved.
No writes, payments, messages, or provider changes.
OUTPUT / EVIDENCE
Run the supplied sample to see prioritized, explainable findings here.
USE CASES / HONEST LIMITS
SOURCE-BACKED CONTEXT
WooCommerce documents native failed-payment retries, subscription reporting, and a Subscriptions Health Check. RebillLens does not duplicate or replace those controls; its narrower purpose is to reconcile what WooCommerce expected with what a separate payment provider recorded.
Official diagnostic guidance for subscriptions that may need attention.
Official explanation of the recurring-payment retry system and its test boundaries.
CLEAR ANSWERS / BEFORE CONNECTION
The public sample demonstrates the diagnostic rule system. Provider permissions and customer-specific coverage are verified before a connected pilot.
It compares the renewals the store expected with transactions reported by the payment provider, using references, subscription IDs, amount, currency, status, and timing to identify records that do not line up.
The rules can flag missing provider transactions, orphaned transactions, duplicate matches, amount or currency mismatches, schedule differences, and local states that disagree with provider outcomes.
No. The forensic audit is deliberately read-only. It does not capture, retry, void, refund, edit orders, or move subscriptions between states.
No. It is a triage value based on flagged records. Customer intent, gateway rules, disputes, taxes, refunds, and the underlying subscription state must be reviewed before any recovery action.
PRACTICAL GUIDES
Diagnose WooCommerce subscription auto-renewal failures by checking schedules, order notes, gateway records, and state mismatches before retrying.
Reconcile WooCommerce subscription renewals with gateway transactions using stable references, timing, amounts, statuses, and explicit exception rules.
Investigate duplicate WooCommerce renewal orders without causing another charge by comparing scheduled actions, order notes, and gateway transactions.
Understand how WooCommerce renewal orders differ from gateway transactions, then map references, amounts, times, and statuses for safe reconciliation.
PAID VALIDATION GATE
We verify API coverage, permissions, data retention, and the exact paid workflow before connecting production accounts. This keeps early customers out of an unsafe beta.
Indicative launch pricing: From $250 per forensic audit. Final scope, price, tax, deliverables, and refund terms are agreed before paid work begins.
Request a paid pilot review