Payment Status Doctor for WooCommerce vs Quantely Activity

Payment Status Doctor for WooCommerce helps store owners, developers, and support teams review WooCommerce orders where payment signals and order status may not match. The plugin focuses on manual, local diagnostics. It scans WooCommerce orders, highlights suspicious payment/status mismatches, builds safe support reports, and compares gateway-level health signals. Payment Status Doctor for WooCommerce does not change order statuses, capture payments, refund payments, retry payments, replay webhooks, or call Stripe, PayPal, or other external payment APIs. The plugin is intended for WooCommerce administrators and is available from WooCommerce → Payment Status. Scanner The Scanner tab reviews pending, failed, and on-hold WooCommerce orders for paid-looking signals such as transaction IDs, payment-looking order notes, and gateway payment signals. Suspicious orders are shown with a risk level, reason, masked transaction ID, order edit link, and copyable support report. Reports The Reports tab compares successful payments, suspicious payment/status mismatches, and normal unsuccessful or incomplete orders for a selected period. Reports are generated from WooCommerce order data and are not stored permanently. Gateway Health Gateway Health groups diagnostic results by payment gateway so store owners can see whether suspicious mismatches appear isolated to one gateway or spread across multiple gateways. Settings Settings control Scanner pagination, payment signal keywords, report display options, risk thresholds, and privacy/safety defaults. Privacy and Masking Sensitive data masking is always enabled. Tables, copied reports, copied summaries, and CSV exports avoid exposing customer personal data, full transaction IDs, raw order notes, billing addresses, shipping addresses, phone numbers, customer IP addresses, and raw gateway payloads. All analysis runs locally inside WordPress.

Lightweight, privacy-conscious pageview and event logging plugin that runs inside your own website. Quantely Activity is built to capture activity reliably under imperfect conditions through server-side recording and optional client-side signals, while supporting filtering for bots, unwanted pages, IP sources and selectable WordPress logged-in roles. Quantely Activity can be used for: Monitoring site behavior Reviewing traffic patterns Security and bot analysis Feeding downstream analytics layers Quantely Activity is turn-key: install it, and pageviews and events should begin appearing shortly after. Raw activity data is retained for a configurable short period, helping keep the plugin lightweight and privacy-conscious. What Quantely Activity is Quantely Activity is a capture and monitoring layer. It is designed to record activity on your site in a structured and reliable way, with a strong focus on signal capture and data integrity. Unlike many analytics tools, it does not focus on marketing analytics, attribution modelling, or behavioral profiling. It also does not rely solely on browser JavaScript. A server-side baseline helps ensure pageviews are still captured when scripts or beacons fail. Hybrid capture engine The plugin combines server-side pageview capture with optional browser-side signals. Typical flow: Browser request ↓ Server pageview baseline ↓ Browser attach (Beacon) – engagement pings – interaction events ↓ Correlation via pageview identifiers ↓ Bot classification and exclusions ↓ Deduplication and storage This architecture helps keep capture reliable under real-world conditions where browser-only tracking can miss signals. Event correlation and deduplication Quantely Activity links browser-side signals back to the pageview where they occurred. Engagement pings, clicks, form submissions, and similar events can be correlated to their originating pageview. Built-in deduplication helps avoid duplicate records when similar signals are captured from both browser and server-side sources. This keeps the activity stream more accurate and easier to interpret. Fully on-site All captured activity is stored in your own WordPress database. Quantely Activity does not send captured activity data to external services. IP addresses are never stored in plain form, and the plugin does not perform cross-site tracking. Privacy-aware design The plugin is designed with privacy-conscious principles in mind: No plain IP addresses stored Short configurable retention window Optional honoring of GPC / DNT signals No external tracking services Data remains on your own site This gives site owners visibility into activity while keeping capture local and controlled. Hooks Quantely Activity exposes a small developer API for integrations and downstream processing. qmon_hit_before_insert — Filter a normalized hit array before it is stored. qmon_hit_recorded — Action fired after a hit has been stored. This is the main integration point for forwarding or persisting captured records. qmon_event_normalize — Filter a normalized event payload before it is finalized. qmon_event_db_dedupe_window_sec — Filter the database deduplication window for events. qmon_bot_verdict — Filter the bot-classification verdict before it is finalized.