Account or mode does not match
A payment in test mode or another Stripe account will not explain a live order in this store.
Stripe + WooCommerce · Match one payment
Stripe Payment Not Showing in WooCommerce
Stripe and WooCommerce can disagree because they are showing different records or different payment stages. Follow the PaymentIntent and its Charge back to the order before assuming the money or the order has disappeared.
Where the reference or status can diverge
The exact identifier often narrows the problem faster than a screenshot of the payment list.
Payment exists but the capture is not final
An authorization or unfinished payment flow should not be treated as a completed charge for fulfillment.
The store did not apply the event
A delivery failure, wrong webhook secret or gateway error can prevent a paid-state update.
Trace Stripe → gateway → WooCommerce
- Open the WooCommerce order and copy its Stripe reference from the gateway details or notes. Determine whether it identifies a PaymentIntent or Charge.
- Find the corresponding payment in Stripe and inspect the related charge, captured amount, currency and mode. Check later refunds separately.
- Inspect the notification delivery that should update the store. Compare the destination and signing configuration with the installed gateway’s instructions.
- Check WooCommerce gateway logs for the same reference and time. A delivered notification can still fail during the order update.
Official references for the checks above:
Restore synchronization, not another payment
Resolve the confirmed cause
Correct the account, mode or notification fault established by the trace. Follow the installed Stripe gateway’s documented reconnect or retry procedure; avoid copying a webhook secret from a different destination.
Verify the result
Confirm the original Stripe charge is reflected once in the correct order. Test the same event path in test mode. Do not ask for a new payment while the first capture remains unresolved.
How Business Watchdog checks the Stripe/store relationship
Business Watchdog resolves supported Stripe references and compares independently read captures with the WooCommerce order. A linked capture that is not recorded by the store can become a discrepancy after the configured grace; an unresolved reference remains a matching problem.
- Order and payment data are compared only within the connected, supported coverage.
- Missing or stale data is shown as incomplete, not as a healthy result.
- Alerts can be delivered by e-mail or Telegram when the corresponding supported rule applies.
Where the coverage stops
The service does not infer that every Stripe payment belongs to this WooCommerce shop. Test/live coverage, shared-account attribution and gateway metadata must be sufficient. It does not edit gateway configuration or repair order records.
How to connect monitoring safely
- Connect WooCommerce and the Stripe restricted read key as separate data sources. Never provide a full secret key for monitoring.
- Check the live/test setting and the gateway references. For WooCommerce test-mode coverage, review the plugin requirement shown in the dashboard.
- Verify source freshness and the first reconciliation results before enabling the relevant notifications.
PayPal cannot provide strictly read-only credentials; Business Watchdog restricts its own requests and explains this before connection. Read the security and access details
Questions worth separating
Are pi_, ch_ and evt_ interchangeable?
No. They identify a payment flow, a charge and an event respectively. Use the relationship between them rather than comparing their strings.
Does a successful webhook delivery prove the order is correct?
No. Also inspect the gateway result and the order’s recorded payment state.
Related troubleshooting guides
Keep the next discrepancy visible
Connect your store and the supported payment provider. Review the coverage and first synchronization before relying on the results. Features and limits depend on your plan.