Product
PayOS

Overview

Summarygenerating…

Overview

Built as an official Square partner product, PayOS wraps Square Restaurant POS with Stampede's guest platform. In-venue payments, deposits, and pre-orders all enrich a single profile; loyalty attaches to the payment card; marketing workflows fire at bill closure.

How it works

Square processes the payment (with full Square security); PayOS captures the transaction metadata (spend, line items, venue, timing) onto the unified guest profile. Events (bill closed, card linked, reward redeemed) become triggers for workflows and data for analytics.

Explore PayOS

Pick a topic to dive into — every feature in PayOS has its own page.

Goal

Start here

Square Restaurant POS integration

PayOS integrates with Square Restaurant POS as an official partner — no middleware, no manual reconciliation.

In-venue payments & bill closure

In-venue payments run through Square with full security; PayOS layers on structured guest data and triggers downstream workflows at bill closure.

Deposits & pre-order payments

Deposits and pre-order payments flow through PayOS at booking time, cutting no-shows and helping kitchens prepare.

Payment card linking

Card linking attaches loyalty rewards and personalised offers to the payment card itself, so redemption is automatic at checkout.

Automatic discounts & reward redemption

Rewards and discounts are applied at checkout automatically based on the guest's profile, loyalty status, and any active campaigns.

Guest profile enrichment

Every closed bill enriches the guest profile with spend, line items, visit time, and venue — turning payments into marketing signal.

Workflow triggers

Bill closure, card linking, reward redemption, and spend-tier changes fire events that can trigger any Marketing workflow in real time.

ROI & revenue analytics

PayOS analytics connect campaign activity directly to Square sales — so ROI is measured on realised revenue, not proxies.

Onboarding scenarios

PayOS onboarding meets you where you are: existing Square merchants, migrating venues, and brand-new setups each have a path.

Core concepts

Bill closure

the event that settles a bill and emits a guest-level record.

Card-linked

loyalty reward attached to the payment card, redeemed at checkout.

Workflow trigger

real-time event that enrols a guest into a journey.

Usage & workflows

In-venue payments, deposits for reservations, pre-orders, card-linked rewards, post-visit campaigns.

Example

A guest pays via Square; PayOS writes the transaction to their profile; a "thanks for visiting" review-request SMS is sent 24 hours later through a Marketing workflow.

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.

Feature matrix

Capabilities included at each subscription tier:

Capability

Starter

Pro

Enterprise

Square POS integration

Guest profile enrichment

Deposits & pre-orders

Card-linked rewards

Workflow triggers

Revenue attribution

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.