Payment Truth for WooCommerce
| 开发者 | pluginmosaic |
|---|---|
| 更新时间 | 2026年8月19日 11:35 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Stripe shows a successful payment, but the WooCommerce order is still unpaid.
- WooCommerce marks an order paid, but Stripe reports a cancelled or failed payment.
- The order total and the amount authorized or collected by Stripe do not match.
- WooCommerce and Stripe use different currencies for the same order.
- WooCommerce and Stripe report different refunded totals.
- A Stripe order remains pending longer than the configured threshold.
- A Stripe order has no usable PaymentIntent or charge reference.
- Scans a bounded window of recent orders created by the official WooCommerce Stripe Gateway.
- Finds the Stripe PaymentIntent or charge reference stored on each supported order.
- Uses the official gateway's existing Stripe connection to read the matching provider record.
- Compares payment status, gross amount, currency, and refunded total.
- Places mismatches in one WooCommerce admin queue for investigation.
- Read-only: never captures, refunds, retries, or changes an order.
- No extra Stripe keys: uses the official gateway's existing connection.
- No customer PII stored in the findings table.
- Five-minute grace period reduces false positives during normal asynchronous updates.
- Bounded hourly scans and a manual scan button.
- Actionable scan health explains provider read errors and the next investigation step.
- Email, Feishu/Lark, DingTalk, and WeCom alerts are opt-in and fire only for newly opened findings.
- Compatible with WooCommerce High-Performance Order Storage (HPOS).
安装:
- Install and activate WooCommerce.
- Install and configure the official WooCommerce Stripe Gateway.
- Install Payment Truth from Plugins > Add New, or upload its ZIP, and activate it.
- Open WooCommerce > Payment Truth.
- Select "Run scan now" and review the findings.
- Adjust the scan window and optionally enable alerts under Settings.
屏幕截图:
常见问题:
Stripe says the payment succeeded, but the WooCommerce order is still pending. Can Payment Truth detect it?
Yes, when the order was created by the official WooCommerce Stripe Gateway and contains a usable PaymentIntent or charge reference. Payment Truth waits five minutes before reporting this status disagreement to reduce noise from normal asynchronous updates.
Does a mismatch prove that a Stripe webhook failed?
No. A finding proves only that the WooCommerce and Stripe records disagree when scanned. Check the order notes, Stripe event and payment record, webhook delivery history, logs, and recent site changes to determine the cause.
Does the plugin change order statuses or move money?
No. Version 0.2.0 is deliberately read-only. It reports evidence and links to the order so a store operator can investigate.
Does Payment Truth require another Stripe secret key?
No. It uses the authentication already configured by the official WooCommerce Stripe Gateway. Payment Truth does not store Stripe credentials.
Which Stripe plugin is supported?
The initial release supports the official WooCommerce Stripe Gateway and its stripe or stripe_* payment methods. Other Stripe gateways may store different references and are not queried.
Can WooCommerce and Stripe amounts really differ?
They can contain different stored values after manual edits, interrupted integrations, unusual capture flows, or other data drift. Payment Truth compares the WooCommerce gross order total with an authoritative Stripe amount in the currency's smallest unit. A finding asks you to investigate; it does not claim that Stripe charged the wrong amount.
Can it detect refund total mismatches?
Yes. When Stripe supplies an authoritative refunded amount, Payment Truth compares it with WooCommerce's total refunded amount and reports a disagreement.
Will it send customer data to an alert service?
No customer identity or card fields are included. An opted-in alert contains the order number, finding severity/title, WooCommerce and Stripe statuses, and an admin order URL.
Why is a mismatch not shown immediately?
Payment updates are asynchronous. Payment Truth waits five minutes before reporting status disagreements and scans hourly by default. You can also run a manual scan.
Which orders are scanned?
Only recent orders that use a supported official Stripe payment method are scanned. The lookback period and maximum orders per scan are configurable, keeping scheduled and manual scans bounded.
Why did the scan finish with provider read errors?
Payment Truth could not read one or more matching Stripe objects. The dashboard now explains the likely cause and next step. Common causes include an order and gateway connection using different Stripe accounts or test/live modes, a deleted or invalid provider reference, or a failed gateway request. Findings from records read successfully remain valid.
Does it work with HPOS?
Yes. Orders are read through WooCommerce CRUD APIs and the plugin declares HPOS compatibility.
更新日志:
- Add actionable scan-health guidance for provider read failures, account or mode mismatches, and first-scan setup.
- Distinguish a healthy scan from an empty scan or a scan with no readable Stripe references.
- Keep all reconciliation behavior read-only.
- Initial read-only Stripe reconciliation release.
- Detect status, amount, currency, refund, stale-pending, and missing-reference issues.
- Add hourly and manual scans with deduplication and automatic resolution.
- Add opt-in email, Feishu/Lark, DingTalk, and WeCom alerts.
- Declare WooCommerce HPOS compatibility.