Web Plura Payment Gateway Monitor – Failed Payments & Checkout Readiness

WooCommerce checkout can appear available while failed payments, pending orders, webhook configuration gaps, test-mode settings, currency mismatches, or checkout setup issues still affect orders. Web Plura Payment Gateway Monitor reviews local WooCommerce gateway configuration and recent order patterns so administrators can investigate payment failures, pending orders, webhook readiness, and checkout setup from wp-admin. The Free plugin works locally in WordPress. It does not call payment-provider APIs, capture payments, replay webhooks, refund orders, change order statuses, store provider secret keys, or transmit payment-monitoring data to a remote monitoring service. Key Payment Checks Use Payment Gateway Monitor to review supported local signals such as:

• enabled WooCommerce payment gateway inventory;
• failed-payment and pending-payment trends;
• aged pending and paid-but-pending order signals;
• checkout page assignment, published status, block or shortcode presence, and HTTPS;
• local webhook configuration signals where detectable;
• gateway mode, provider/plugin information, and currency mismatch warnings;
• conditional payment or gateway-fee plugin awareness;
• test-payment readiness checklist and manual gateway test log;
• local gateway risk score and WordPress Site Health checks;
• report history, printable summaries, CSV exports, and JSON exports.

Failed Payments Failed payments can create support work, lost orders, and unclear checkout troubleshooting. Payment Gateway Monitor reviews recent WooCommerce order statuses and shows failed-order counts, failed-payment rate, trend direction, and gateway-level failed-payment summaries where local order data is available. These checks help administrators investigate patterns. The plugin does not automatically diagnose every failed payment, fix gateway configuration, retry payments, or contact the payment provider. Pending and Paid-but-Pending Orders Pending and on-hold orders can hide checkout or webhook follow-up problems. Payment Gateway Monitor can highlight pending-payment orders, pending or on-hold orders older than 24 hours, and paid-but-pending signals where a local WooCommerce order has a transaction ID but remains pending or on hold. Paid-but-pending is a local diagnostic signal. It is not confirmation from a payment provider and should be reviewed against order notes, gateway settings, and the provider dashboard before taking action. Checkout Readiness Checkout can fail even when products and gateways look enabled. The plugin checks whether WooCommerce has a checkout page assigned, whether that page is published, whether the checkout block or classic shortcode is locally detectable, whether the checkout URL uses HTTPS, and whether at least one gateway is enabled. Use this before a launch, migration, checkout redesign, or payment-gateway change. It is a readiness review, not an end-to-end transaction test. Webhook Readiness Payment Gateway Monitor reviews local gateway settings for webhook-related configuration where the gateway exposes fields that WordPress can inspect. This can help administrators prepare a checklist before contacting a gateway provider or checking a provider dashboard. The plugin does not verify remote webhook registration, watch live webhook delivery, replay webhook events, or read provider delivery logs. Gateway Configuration Checks The plugin reviews WooCommerce payment gateways visible to WordPress. It can show enabled or disabled status, local test or sandbox mode signals, provider family labels where locally detectable, related plugin/version information where available, supported readiness items, wallet/express-checkout HTTPS and currency signals, and currency mismatch warnings. Provider names may appear only as local gateway labels. Payment Gateway Monitor does not call Stripe, PayPal, WooPayments, or other payment-provider APIs. Test Payment Readiness The test-payment checklist helps administrators review prerequisites before manually testing checkout. The included manual gateway test log lets an administrator record a local test date, environment, outcome, next due date, and note for each gateway. The plugin does not place real or sandbox transactions, charge test cards, simulate provider callbacks, or verify funds. Test results are entered manually by an administrator. Gateway Risk Score The gateway risk score summarizes supported local findings from the latest scan, such as failed-payment rate, missing local webhook configuration signals, currency mismatch warnings, enabled gateways in test mode, checkout setup issues, aged pending orders, paid-but-pending signals, and recent failed-payment trend direction. This score is an operational troubleshooting aid. It is not a payment-provider certification, financial rating, uptime monitor, fraud score, or guarantee that checkout will succeed. Reports and Exports Administrators can keep local scan history, review issue and recommendation summaries, print a troubleshooting summary, and export supported data for developer, agency, support, or client handoff. Supported export workflows include report history CSV, report history JSON, issue CSV, and gateway-readiness CSV. Site Health Integration Payment Gateway Monitor adds supported gateway-readiness checks to WordPress Site Health. Site Health can show whether a local scan is missing or stale and whether the latest local scan found important payment gateway or checkout readiness warnings. This is focused on payment gateway readiness. It is not a complete WooCommerce health monitor. Local Processing and Privacy The Free plugin runs included scans, reports, exports, print views, settings, manual test logs, and Site Health checks inside WordPress. It reads local WooCommerce configuration, payment gateway settings visible to WordPress, and recent order-status patterns. It stores plugin-owned settings, local scan summaries, report history, retention settings, and manual gateway test log records in the WordPress database. Reports are viewed, printed, or exported manually by an administrator. The plugin does not collect provider secrets, full customer payment details, order notes, provider dashboards, remote delivery logs, or external gateway logs. Optional telemetry is disabled by default. If an administrator enables it from the plugin telemetry settings, selected lifecycle, sanitized error, and coarse environment diagnostics may be sent to Web Plura. Local scans, reports, exports, print views, manual test logs, settings, and Site Health checks continue working when telemetry is disabled or unavailable. Uninstall removes plugin-owned options, legacy plugin-owned options, and the plugin-owned scan table. Optional Web Plura Services The WordPress.org package includes the local gateway checks, failed and pending payment review, webhook readiness checklist, manual test log, reports, print views, exports, settings, and Site Health signals described in this readme. Separately installed or hosted Web Plura services may offer account-backed support, hosted operations, scheduled monitoring, alert policies, cross-site workflows, or team reporting. Those optional services are separate from the included local Free plugin behavior and do not unlock the local features listed here. Important Limitations Payment Gateway Monitor helps administrators review supported local signals. It does not guarantee that every failed payment, checkout issue, webhook problem, or gateway configuration issue is found. The plugin does not call payment-provider APIs, store provider secret keys, process payments, capture payments, refund payments, replay webhooks, automatically contact customers, change WooCommerce order statuses, or fix gateway settings automatically. The Free plugin is WooCommerce-focused. It does not provide non-WooCommerce payment monitoring. Resources

• Product page: https://wplura.com/products/web-plura-payment-gateway-monitor
• Documentation: https://wplura.com/docs
• Support: https://wplura.com/support
• Terms: https://wplura.com/terms
• Privacy: https://wplura.com/privacy

0.1.53

• Open New Dashboard by default, retain later Legacy choices, and align Free submenu presentation.

0.1.52

• Made New Dashboard workflow errors clearer and accessible while preserving existing checks and actions.

0.1.51

• Unified Settings navigation and reused the shared section-tab style where existing plugin pages use WordPress tabs. Routes, settings, data, and actions are unchanged.

0.1.50

• Standardized New Dashboard tabs as a consistent, keyboard-accessible horizontal strip across desktop and mobile. Dashboard data and actions are unchanged.

0.1.49 Embedded telemetry reporting in Settings with a bounded local delivery history, seven-day chart, and event details. 0.1.48

• Added a shared Web Plura Settings page with consent, telemetry data, and error reporting details, plus a WordPress.org plugin directory on About. Existing consent and local features remain unchanged.

0.1.47

• Refined New Dashboard links, tabs, buttons, table colors, and responsive presentation. Moved the review request to a dismissible admin notice.

0.1.46

• Kept the New Dashboard review button readable under alternate WordPress admin color schemes.

0.1.45

• Kept compact New Dashboard donut values readable through the chart inspector without clipped labels.

0.1.44

• Made every New Dashboard scan measure readable with horizontal scrolling on narrow screens.

0.1.43

• Improved New Dashboard KPI readability on narrow screens.

0.1.42 Added a WordPress.org review link to both dashboard views. 0.1.41

• Reorganized the optional New Dashboard into gateway health, scan history, and guarded scan tasks.

0.1.40

• Restored Old Dashboard payment context and exact values in the Free New Dashboard, including saved scan defaults and WooCommerce guidance. All four tabs now fit narrow mobile widths; the Old Dashboard is unchanged.

0.1.39

• Refined the New Dashboard with source-backed chart and exact value table presentation. Existing data and the Old Dashboard are unchanged.

0.1.38

• Restored the visible Dashboard submenu under Payment Gateway Monitor; it opens the saved dashboard view.

0.1.37

• Refined New Dashboard card layout for available content width, preserving recorded values and Old Dashboard behavior.

0.1.36

• Added keyboard-accessible inspection of exact recorded chart values in the New Dashboard; the original dashboard and stored data are unchanged.

0.1.35

• The New Dashboard highlights an existing product workflow as its primary action, while retaining the original dashboard and its data.

0.1.34

• Added a shared, optional telemetry consent screen with explicit accept and decline choices and a session-scoped admin invitation. Local features remain available without consent.

0.1.33

• Optional telemetry now sends only documented event properties after administrator consent. Local features remain available with telemetry off.

0.1.32

• The new dashboard Overview groups four KPIs, a real-data featured ECharts chart, priorities, status, and operational context. The original dashboard is unchanged.

0.1.31

• The new dashboard now shows a link-style “Switch to Old” control matching the existing “Switch to New” control.

0.1.30

• New-dashboard tabs now honor section links and browser history while retaining keyboard navigation and activity pagination.

0.1.29

• The new dashboard now explains when a trend needs another retained result and shows an honest empty Workflows state when no task or page is available.

0.1.28

• The new dashboard now shows clear section-specific messages for missing results and history while preserving real zero values and chart data alternatives.

0.1.27

• Added shared, page-scoped About and Upgrade presentation across the Free plugins while preserving product-specific content and routes. Added the local About page.

0.1.26

• Added stored warning messages and severity plus pending-payment and trend columns to the new dashboard activity.
• Kept the original dashboard unchanged and improved the shared mobile workflow layout.

0.1.23

• Updated the new dashboard score chart to an accessible semicircle gauge using existing local scores.

0.1.22

• Added a per-user Old/New dashboard switch with one visible Dashboard menu entry and refreshed the new dashboard header.

0.1.13

• Improved dashboard text contrast under WordPress Midnight admin colors; existing local features and actions remain available.

0.1.12

• Improved the local payment dashboard layout and risk history chart while keeping exact scan history and controls.

0.1.11

• Record a bounded maximum pending-order age alongside local scan totals for optional consented monitoring. Existing local checks and exports remain available.

0.1.10

• Clarified the Free payment risk dashboard and added an accessible local risk history chart beside the exact scan table.

0.1.9

• Fixed first-time telemetry opt-in so the consent event queues only after an administrator enables that category.

0.1.8

• Added a responsive Free and separate service comparison to the Upgrade page.

0.1.6

• Added optional, consent-gated WPlura telemetry settings for lifecycle, sanitized error, and coarse environment diagnostics while keeping local payment monitoring independent.
• Refreshed the WordPress.org readme for clearer checkout failure, payment gateway, order issue, and local monitoring search intent.

0.1.5

• Added a compliant informational Upgrade submenu that explains included local monitoring and links to separately available Web Plura resources without restricting built-in features.

0.1.4

• Added a Free-owned report extension surface with the legacy report section hook as fallback for reversible Pro cloud report replacements.

0.1.3

• Added a Free-owned dashboard extension surface with the legacy dashboard card hook as fallback for reversible Pro cloud monitoring replacements.

0.1.1

• Updates the wp-admin and WordPress.org plugin icons to the official Web Plura brand assets.

0.1.0

• Initial release.