Product
POS and door webhooks. Phone alerts. A trail you can hand over.
impayr sits next to the systems you already run. Orders and door scans come in over webhooks. When a tab looks like overservice, the bartender's phone takes over the screen until they acknowledge. Flags, acks, and resolutions seal into an evidence packet. Square is live. No new terminals.
What it is
Watch the pour. Interrupt the phone. Keep the packet.
impayr is not a new POS and not a camera network. It watches drink velocity as orders land, matches a tab to a door scan without keeping the name, and puts a full-screen CRITICAL on a server's phone before the night gets away from you.
- 01
POS & door events
Signed Square order webhooks and door-scanner events, venue-scoped. Compute runs off the request path so the terminal never waits on us.
- 02
Staff alert & ack
When a tab hits CRITICAL, the bartender's phone goes full-screen. They check the guest, offer water, tap a resolution. One ack clears it on every device looking at that night.
- 03
Sealed evidence
Flags, acknowledgments, and timing hash-chain into a ledger. Export a chargeback packet or an insurer summary as PDF.
How it attaches
Webhooks. No new hardware.
If the POS can fire a webhook and the door can post a scan, impayr can sit next to the night you already run. The handheld is a browser on the phone already in a server's pocket.
- 01
POS webhook
A venue-scoped URL receives signed order events. Square is the live adapter today: HMAC-SHA256 over the raw body, HTTP 200 in well under two seconds, then background compute.
- 02
Door webhook
Scan events enter the same spine. Names and dates of birth are read only to build a salted identity hash, then dropped. Durable records keep the hash, not the guest.
- 03
Staff handheld
Open a URL. Pick a name from the roster. Enter a PIN. The device waits idle until a tab crosses CRITICAL. Then it takes over the screen.
Technical
What actually runs.
Operator-facing, not a feature grid. This is the machinery behind flag, acknowledge, and prove.
- Signed webhooks
- POS ingest verifies a Square-style HMAC on the raw request body against the venue key, then ACKs HTTP 200 in well under two seconds. Heavy work is off the request path. Invalid signatures never persist.
- POS adapters
- Vendor envelopes become a generic order: line items, opaque tab refs, masked last-4 only. Square is the live adapter. Clover, Shift4, Lightspeed, and TouchBistro use the same webhook contract as those adapters land. They are not live production integrations, and they are not partnerships.
- Risk engine
- Drink velocity is primary. A Widmark-style BAC band is secondary and always labeled as an estimate. Never a bare numeric BAC. Never a medical claim. Bands are LOW, ELEVATED, HIGH, CRITICAL. A Critical alert fires on the transition into Critical, not on every recompute of an already-critical tab.
- SSE alerts
- A committed Critical event reaches connected handhelds over Server-Sent Events as a full-screen CRITICAL: fact line, estimated intoxication band, tab ref, and the ack form. One staff ack clears it on every device looking at that night.
- Append-only ledger
- Flags, acknowledgments, and resolutions append. Corrections append a new row that points at the one they supersede. Each entry carries a hash of its fields plus the previous hash, so a later edit is detectable. Tamper-evident, not tamper-proof. Retention expiry is a disclosed sweep, not a silent rewrite.
- Hash matching / privacy
- Door identity is a per-venue salted SHA-256 of a canonical name and optional DOB. Durable storage is hashes, timestamps, menu facts, staff IDs, bands, and compliance status. Raw webhook bodies live in a short operational buffer (about 48 hours), then go. No PANs, CVVs, or card expiry. No raw PII long-term.
- PDFs for counsel and insurer
- Chargeback packets assemble card-present representment evidence from records already held: door-hash corroboration when a high-confidence match exists, an itemized service record, and the sealed trail. A separate insurer summary is period aggregates (nights, alerts, ack rate, resolutions), not a prediction. Absent matches are disclosed, never dressed up.
On the floor
No bartender friction.
impayr informs. It never nags the terminal, never auto-blocks an order, and never pretends to be the POS.
- 01
Three-tap ack
On CRITICAL: visual sobriety check, water offered, then one resolution tap (guest OK, slowed, cut off, and the rest). The resolution tap is the submit. Two checkboxes plus one action. That is the roughly 3-tap flow.
- 02
Full-screen CRITICAL
The handheld does not badge in a corner. When the tab crosses the band you set, the screen is the alert: headline, served-drinks fact, estimated band, tab, ack.
- 03
PIN roster
Staff pick themselves from the venue roster and enter a 4 to 6 digit PIN. The session is a signed cookie, not a name in the clear. Unknown IDs never land.
- 04
Beside the POS, not instead
Orders keep ringing on the terminal you already own. A recorded cut-off is a documented staff decision. impayr never blocks the pour from the POS.
POS
If the room already runs Square.
impayr attaches over webhooks. No new terminal hardware. Square is the live adapter. The others are systems high-volume rooms already trust. Same attach path as those adapters ship. Not live integrations today. Not partnerships.
Square
Live adapter
Signed order.updated webhooks, venue-scoped URL, HMAC over the raw body. This is the POS ingest we run today.
Clover
Not live
Webhook in, vendor-neutral order out. Designed to sit beside the terminal you already have, not replace it. Not a production adapter today.
Shift4
Not live
Same spine as Square: signed events, off-path compute, handheld ack. Integration story, not a production claim.
Lightspeed
Not live
Attaches as another POS adapter on the generic contract. No Lightspeed-shaped live ingest in production today.
TouchBistro
Not live
Nightclub and restaurant floors already on TouchBistro keep that terminal. impayr listens. It does not swap the rail. Not live today.
What we do not claim
A trail. Not a shield.
impayr records what flagged, who acknowledged, and when the sequence sealed. It does not confer legal immunity, guarantee a chargeback or lawsuit outcome, or discount insurance premiums. BAC bands are estimates. Hash matches are corroboration, not a verdict on a guest.
Get started
See the trail on your floor.
Request a demo. We'll walk a night from clear tab to sealed evidence, mapped to how you already serve.
Prefer email? demo@impayr.com