內容簡介
Web Plura Payment Gateway Monitor 是一款專為 WooCommerce 設計的外掛，幫助管理員檢查支付閘道的配置及訂單狀態，從而有效解決支付失敗、待處理訂單及結帳準備問題，提升商店運營效率。
【主要功能】
• 檢查支付閘道配置及狀態
• 追蹤失敗支付及待處理訂單趨勢
• 檢查結帳頁面及其設定
• 評估 webhook 配置的準備狀態
• 測試支付準備清單及手動測試日誌
• 提供報告歷史及匯出功能
外掛標籤
開發者團隊
② 後台搜尋「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
External Services
This free plugin does not connect to external services for its included local scans, reports, exports, print views, manual test logs, settings, or Site Health checks.
The plugin reads local WooCommerce configuration, payment gateway settings visible to WordPress, and recent order-status patterns. Reports are viewed, printed, or exported manually by the administrator. Payment provider secrets, full customer payment details, order notes, provider dashboards, remote delivery logs, and external gateway logs are not collected by this plugin.
Optional telemetry can be enabled by a site administrator from the plugin telemetry settings. It is disabled by default and is not required for local monitoring. When enabled, the plugin may send selected categories to Web Plura at https://api.wplura.com/v1/plugin/telemetry/events:
Usage analytics: plugin lifecycle, version, and consent-change events.
Error diagnostics: sanitized plugin-owned error metadata.
Environment diagnostics: coarse WordPress version, PHP version, multisite status, locale, and plugin version metadata attached to consented events.
The recipient is Web Plura. The data is used to understand plugin reliability and compatibility. The plugin does not send gateway settings, order records, checkout data, payment or customer data, webhook payloads, manual test notes, transaction identifiers, personal records, passwords, API secrets, JWTs, authentication headers, request bodies, full file paths, raw stack traces, or unrelated personal information. Consent can be withdrawn later from the plugin telemetry settings, and local payment monitoring continues working when telemetry is disabled or unavailable.
Optional Web Plura services are separate from the Free plugin’s included local operation. If an administrator chooses to use a separate hosted service, review that service’s documentation, terms, privacy policy, and consent controls before sending store data.
