Product
PayOS
Deposits & pre-order payments
Summarygenerating…
Overview
When Table Bookings requires a deposit (large party, peak time, private dining), PayOS takes the payment at the booking step. Pre-orders let guests choose dishes ahead of time and pay for them with the deposit.
How it works
The bookings engine hands off to PayOS at confirmation; once payment clears, the booking is held. Pre-order line items attach to the booking record.
Core concepts
Deposit
amount taken at booking time and credited against the final bill.
Pre-order
itemised selections paid ahead of the visit.
Usage & workflows
Large parties, peak service, private dining, prix-fixe events.
Example
A 12-top Saturday booking requires £30/head; the kitchen receives the pre-order manifest a day ahead, plating time drops by 15 minutes.
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.