What the alert would cover
| Risk type | Why it matters | Example alert |
|---|---|---|
| Checkout failure | Customers cannot complete payment | Stripe checkout error after plugin update |
| Payment stuck pending | Store may have collected money but not processed the order correctly | Successful Stripe payment remains Pending Payment |
| Amount mismatch | WooCommerce and the processor may disagree on what was collected | PayPal discount applied twice or Stripe captures less than order total |
| Shipping or tax undercollection | Orders may be fulfilled before the full total was captured | PayPal total missing shipping or Stripe captures less than WooCommerce total |
| Refund issue | A refund can affect customer support, accounting, inventory, and payout records | Refund succeeds in one system but not another |
| Webhook or capture failure | Orders can fail silently or customers may be unsure whether they paid | OrderProcessor.php:109 with webhook verification failures |
| Reconciliation risk | Payouts, reports, and accounting records may not match order records | Gateway captured amount, WooCommerce total, and payout report disagree |
What counts as signal: visits to /stack-alerts/, email requests with stack details, repeat visits from recovery or issue pages, or a real store owner/developer/agency describing their payment stack.
Save your stack
Use the dedicated stack page to choose tools and alert types. The page visit itself becomes a measurable signal in Vercel Analytics.
Already dealing with an issue?
If a payment appears successful but WooCommerce is pending, or totals do not match, start with the recovery checklist before changing order status, refunding, capturing, disabling plugins, or clearing evidence.