For Shopify, BigCommerce, WooCommerce and Shopware merchants
The refund failed. Nobody told you.
Your admin says the refund happened. The payment that fulfils it is a separate record — and when that one fails, nothing tells you. You find out when the customer does.
Read-only. Nothing runs on your storefront or in checkout.
Your store already holds both records. We read the one nothing else does.
What we catch
Three ways a refund quietly doesn’t happen
| What goes wrong | You hear | Severity |
|---|---|---|
| The refund failed outright Declined card, insufficient balance, closed account. | Immediately | Critical |
| The refund is stuck pending Accepted, never completed. The most common silent failure, because nothing reports an error. | After 2 hours | Warning |
| No money ever moved A refund with no payment transaction behind it. Almost impossible to spot by hand. | After 30 minutes | Warning |
We also watch failed payments and authorisations about to lapse. See how detection works.
Why merchants keep it
It tells you once, and only when it matters
One alert per problem
Not one per check. Each broken refund has a lifecycle, so nothing is announced twice.
Severity decides the channel
A failure reaches email and your own systems at once. A slow refund waits in an inbox.
Numbers analytics cannot give you
What share of refunds actually arrived, which gateway fails most, how long money really takes.
We never see your customers
No names, emails, addresses or phone numbers are ever requested. How we handle data.
Find out what’s already broken
We read your recent order history the moment you connect a store, so anything already failed or stuck shows up on your first visit.
Free to start on every platform. Read-only. Uninstall any time.