Aplauso supports three isolated data environments. Each serves a different purpose, and it's important to understand the distinction before going live - otherwise test transactions can pollute your real data, or real payouts can be triggered during testing.
The Three Environments
Live - Production
Use for: Real guests, real tips, real payouts.
- All transactions are processed through your live Stripe account.
- Tips move real money. Payouts hit real bank accounts.
- Analytics and reporting reflect actual business performance.
- This is the mode your venue operates in day-to-day.
Sandbox - Testing
Use for: Setting up, testing integrations, training staff, QA before launching.
- All payments use Stripe test mode - no real money moves.
- Use Stripe test cards (e.g.
4242 4242 4242 4242) to simulate payments. - Tips and ratings appear in the dashboard but are clearly marked as sandbox data.
- Employees can practice the app without affecting real earnings.
- Sandbox data is completely isolated from Live data.
Demo - Presentations and Training
Use for: Sales demos, investor presentations, onboarding walkthroughs.
- Pre-populated with realistic-looking demo data (employees, tips, ratings, analytics).
- Payments go through a demo Stripe environment - nothing real happens.
- Ideal for showing stakeholders how the platform works without setting up a real account.
- Demo data cannot be modified or deleted.
How to Switch Environments
In the personal dashboard, use Settings > Payment to switch between Live and Training. The banner at the top of the dashboard also links directly to that setting whenever you are outside live mode.
- 🟢 Live - green badge
- 🟡 Sandbox - yellow badge
- 🔵 Demo - blue badge
How Environment Changes Are Applied
Environment changes are applied to the employee, department, or property being tested. The dashboard and kiosk then follow the server-resolved environment automatically.
- Employees can switch their own employee record when self-service environment controls are available to them.
- Property Admins can move a property between supported environments from the property settings flow.
- The dashboard badge updates after the server confirms the change.
Warning: Switching environments in the middle of a shift can confuse staff. Move the relevant employee or property into Sandbox deliberately before testing, then return it to Live when testing is complete.
Environment and the API
All Aplauso API endpoints accept an optional environment parameter in the request body or query string:
GET /v2/analytics?environment=sandbox
POST /v2/tips
{
"environment": "live",
...
}
The default environment is always live - if you omit the parameter, the request affects live data. Always specify "environment": "sandbox" during integration testing.
Stripe Test Cards for Sandbox
When testing in Sandbox mode, use these Stripe test card numbers:
| Card Number | Scenario |
|---|---|
4242 4242 4242 4242 | Successful payment |
4000 0000 0000 0002 | Card declined |
4000 0025 0000 3155 | Requires 3D Secure authentication |
4000 0000 0000 9995 | Insufficient funds |
Use any future expiry date and any 3-digit CVC.
Frequently Asked Questions
Can sandbox tips accidentally trigger real payouts?
No. Sandbox is completely isolated. Stripe test-mode transactions never process real charges.
Do employees see sandbox tips in their balance?
Sandbox tips appear in the employee's dashboard only when the dashboard is also in sandbox mode. The balances are separate and will not trigger real withdrawals.
What happens when we switch back from sandbox to live?
Sandbox transactional data for the affected scope is purged during the return-to-live process. Guest identity records are not purged because they are shared across environments.