A dead terminal at a busy till is a queue, an abandoned basket, and a store manager phoning head office. Across thirty sites, the problem is not fixing it — it is knowing which one, and knowing before the call.
Your whole estate at once, with the detail available when you need to drill in.
This matters for anyone whose terminals fall in PCI scope, so it is worth stating plainly rather than burying.
A transaction event carries an amount, a currency, a status, an optional payment type, an optional product name and quantity, and a timestamp. That is the shape of the data model. There is no field for a card number, a cardholder name, an expiry, or a CVV, and nothing in the ingest API accepts them.
PulseGrid is deliberately built to monitor the fact that a payment happened, not to touch its contents. Your acquirer and payment application keep that responsibility.
PulseGrid does not talk to your hardware directly. Your software — whatever runs on the machine, or the middleware behind it — posts events to a REST API as they happen. That means no gateway to install, no agent to maintain, and no vendor lock on the device side.
The whole integration is five steps, and most teams have the first events flowing in an afternoon:
Terminals belong to locations, and locations belong to your organisation, so a franchise group or a retail chain sees the estate rolled up rather than site by site.
Invite your team with Owner, Admin and Member roles. Every figure is reported in one currency you set for the organisation, stamped at the moment each event is ingested — so a multi-country estate does not silently mix units in the same total.
No. The transaction event model has fields for amount, currency, status, payment type, product name, quantity and timestamp. There is no field for a card number, cardholder name, expiry or CVV, and the ingest API will not accept them. PulseGrid monitors that a payment occurred; it never handles its contents.
No. PulseGrid does not process payments, settle funds or route authorisations. It is a monitoring and reporting layer that sits alongside whatever you already use.
Yes. Terminals roll up into locations and locations into your organisation, so you can look at the whole estate, one store, or one terminal, and filter analytics by location and date range.
It flips to offline once it has missed the heartbeat window you set for your organisation, and an email alert fires. You can set alert preferences per terminal so a known-flaky unit does not drown out the rest.
Each organisation reports in a single currency, set by you and stamped on every event at ingest. That keeps totals meaningful instead of silently adding different units together.
Start free with three terminals. No card required, and the developer console has a simulator so you can watch events land before touching hardware.