Square events, straight into ntfy
Every new payment, refund, or dispute — posted to ntfy the moment it happens. No ntfy app to install, no monthly automation subscription.
The gap this fills: Square doesn't ship an official ntfy app. If you want new payment, refund, or dispute to show up in ntfy the moment it happens, the usual options are a paid third-party bot, custom code, or routing everything through a $20–50/month automation platform just to move one webhook from one URL to another. ZestyGlue does exactly that one thing for $9/month.
What it looks like
ZestyGlue
Square — Payment.Created
42.50 USD
status: COMPLETED
A real Square event, shown as ZestyGlue formats it for ntfy.
Setup — about two minutes
- Create the connector. In ZestyGlue, start a new Square → ntfy connector. You'll get a unique webhook URL right away.
- Point Square at it. In the Square Developer Dashboard, go to your app → Webhooks → Add Endpoint, paste in your ZestyGlue webhook URL, and select the event types you want.
- Copy the Signature Key. Square shows a Signature Key for your webhook subscription — paste that into ZestyGlue's connector setup so every event can be verified as genuinely from Square.
- Point ntfy at ZestyGlue. Pick any topic name — e.g.
https://ntfy.sh/your-secret-topic — enter it into ZestyGlue, and subscribe to that same topic in the ntfy app or web client.
Under the hood: Square signs its webhook using both your endpoint's URL and the request body together — if you ever change your ZestyGlue connector's URL, update the endpoint URL in Square's dashboard to match, or verification will fail.
Events you can forward
payment.created
payment.updated
refund.created
dispute.created
Questions
Is my Square Webhook Signature Key safe with ZestyGlue?
It's encrypted at rest with Fernet symmetric encryption before it ever touches disk, it's never logged, and it's never displayed again in the dashboard after you enter it — only a masked placeholder is shown.
Does this work with Square's sandbox/test environment?
Yes — point a sandbox webhook subscription at the same connector while testing, then switch to your production Signature Key when you go live.
Can I track disputes separately from regular payments?
Yes — subscribe to dispute.created as its own event type alongside payment.created if you want disputes called out distinctly.
Do I need to self-host ntfy?
No, the free public ntfy.sh server works fine for most people — just pick an unguessable topic name.
What happens if my ZestyGlue subscription lapses?
Events are silently dropped rather than causing errors on Square's side — Square never sees a failure response, so it won't retry aggressively or flag your webhook as broken. Your dashboard will simply stop showing new events until you resubscribe.