What Square + PingBell does together
Square’s Webhooks API fires events on completed payments, order updates, and customer creation. PingBell subscribes to payment.updated or order.fulfillment.updated and turns every Square transaction (online or point-of-sale) into a live counter update, a team push, and a graph point.
Use cases
- Retail shops using Square for POS with a live back-office sales counter
- Restaurants on Square for Restaurants tracking real-time ticket sales
- Boutique fitness studios using Square for membership payments
- Service businesses (salons, spas) running Square Appointments
- Multi-location operators aggregating sales across stores
Setup
- In Square Developer Dashboard, create an app (if you don’t have one). Go to Webhooks.
- Paste your PingBell webhook URL.
- Subscribe to
payment.updated(fires on successful captures). - Save, test with a $1 test transaction.
- In PingBell, customize the counter display.
Why PingBell beats the alternatives for Square users
Square’s native dashboards are designed for the merchant, not the team. Square doesn’t offer team-broadcasting tools or TV-app dashboards. PingBell adds that layer on top — live number on the wall, push on the staff phones, counters across multiple locations.
FAQ
Does it work with Square for Restaurants / Square for Retail?
Yes. Both use the same Webhooks API for payments and orders.
Can I distinguish POS from online payments?
Yes. The source_type field in the payload indicates whether a payment came from in-person (POS), online (Square Online), invoice, or link.
How do I aggregate multiple locations?
Connect each Square location as a separate source; either combine or split counters.
Does it support Square Invoices?
Yes. Invoice paid events fire through the same webhooks channel.
What about Square Appointments bookings?
Yes. Appointment-created and appointment-completed events are separate webhooks; subscribe to whichever matters for your counter.