Product
PayOS
In-venue payments & bill closure
Summarygenerating…
Overview
Payments complete as they always have on Square hardware. The difference: each transaction lands on a Stampede guest profile, unlocks loyalty rewards, and can trigger post-visit marketing.
How it works
Square processes the card; PayOS listens for bill closure events; the event writes to the guest profile and fires any subscribed workflows.
Core concepts
Bill closure
settled bill at end-of-service.
PCI scope
remains with Square; Stampede never handles raw card data.
Usage & workflows
Every in-venue transaction — dine-in, bar service, takeaway.
Example
A £60 bill closes; the guest profile shows the updated lifetime spend; if they're in the "big spender" audience, a thank-you workflow starts.
Note
Where to find it
Configure this in the Stampede admin app under Admin → PayOS. Permissions are role-gated — contact your account owner to request access if you don't see it.
Tip
API reference
The Stampede API exposes guest, booking, and campaign data programmatically. See developer.stampede.ai for authentication, base URL, rate limits, and endpoint reference.
Note
Need help?
Contact support via the Stampede admin app or your account manager. The knowledge base at help.stampede.ai has guided walkthroughs for common tasks.
Want to see it live?
Book a 20-minute walkthrough and we'll show you the feature in your own admin.