Webhook health degraded
This article explains what to do when payment statuses in MapleGather fall behind because webhook delivery from your payment processor is failing.
What’s happening
Section titled “What’s happening”MapleGather receives notifications from your payment processor (called webhooks) to update payment statuses, mark invoices as paid, and fire receipts. When webhook delivery fails repeatedly, payment states in MapleGather may be behind the processor’s actual state — for example, a payment that succeeded in Stripe may still show as Pending in MapleGather until the next successful delivery.
Not built yet. The designed warning banner (three or more Stripe deliveries failed in 24 hours), the per-processor Webhook health cards and their per-failure actions aren’t built: the Payment processor page doesn’t show webhook failures today, and MapleGather has no control to re-verify a signing secret, retry a delivery or re-register the webhook endpoint. MapleGather won’t warn you when deliveries fail — you’ll usually notice it as a payment whose status in MapleGather doesn’t match the processor’s dashboard.
How to fix it
Section titled “How to fix it”- Check the payment’s status in the processor’s dashboard (Stripe or PayPal) before acting on what MapleGather shows.
- Stripe outage or network issue: no action is needed once Stripe recovers. Stripe automatically retries failed webhook deliveries for up to 72 hours, and the payment status in MapleGather catches up when a delivery succeeds.
If that didn’t work
Section titled “If that didn’t work”- If the Stripe block on the Payment processor page shows Your Stripe connection needs attention, select Reconnect to re-run the Stripe connection.
- If PayPal is the processor that’s behind, see PayPal connection failed or auto-renew canceled.
- MapleGather doesn’t show a failed delivery’s cause. Until deliveries succeed, keep checking a payment’s status in the processor’s dashboard before acting on what MapleGather shows.