You hear about a stuck purchase the minute it happens

When a purchase reaches PayGlue but cannot be delivered to Ghost, the owner of the publication now gets one email right away, not a nightly digest that needed three failures in a day before it would say anything. The mail names the cause. If PayGlue could not write to your Ghost site, it points at the Ghost connection page. If your payment provider's webhook could not be verified, it points at that provider's connection page and asks you to compare the webhook secret. Either way the failed events stay in your event log and can be replayed once the cause is fixed, so no purchase is lost. You get one mail per incident; the next delivery that goes through resets it. Both texts can be read and edited in the admin like every other PayGlue email.

• One email on the first failed delivery, sent from the worker, not from a nightly job
• Two texts: Ghost connection failing, or provider webhooks being rejected
• Failed events stay in the event log and can be replayed after the fix
• We are not copied on your mail. If nothing has changed after two days, we get one internal note and may ask how things are going