Overview
Juno Pay@Table for Oracle Simphony lets guests scan a QR code on the table, see their bill, split it, add a tip and pay. This article provides the one-page onboarding overview as a PDF download. It shows the seven steps from ordering the solution to the first paid table, who is responsible for each step, two optional add-ons, and what you and 934 each bring to the project.
Applies to
| Product | Juno Hospitality Suite |
| Solution | Juno Pay@Table |
| Integration | Oracle Simphony (Simphony STS Gen2 API) |
| Audience | Property and F&B managers, system integrators |
What you'll find here
A one-page PDF overview of the Juno Pay@Table onboarding, with a short summary of the seven steps and the optional add-ons below.
Download the onboarding overview
The onboarding overview Your Juno Pay@Table Onboarding is available as a PDF download (attached to this article).
Before you start
- An Android device is required for each terminal.
- If you use PAX terminals, an employee number must be set up and used.
- Install the Juno app on every Android device you will use as a terminal before go-live. The PDF contains a QR code for the download.
The seven steps at a glance
| Step | What happens | Who |
|---|---|---|
| 1. Order the solution | Properties, terminals and guest payments. 934 sets up your Juno Portal. | Customer |
| 2. Simphony STS Gen2 API configured | An API account per property, plus the fallback tender and tip service charge in EMC. | Oracle, customer, system integrator |
| 3. Property connected | 934 stores the API account and reads your POS: revenue centres, tables and tenders. | 934 |
| 4. Confirm tenders | You confirm the fallback tender, the tip service charge and the card-brand tenders. | Customer |
| 5. Verified before hardware | Every Simphony call is tested from the browser, including one test round. | 934 |
| 6. Activate terminals | Install the Juno app on each Android device before go-live. During go-live your Customer Success Manager (CSM) provides the activation sheet with the QR code. Scan the sheet with the Juno app and use Tap on Mobile. | Property staff, 934 CSM |
| 7. Go live | One real payment per payment rail on a test table, then service. | Property staff, 934 |
At go-live, your CSM provides one activation sheet per device. The Juno app scans it and receives its whole configuration.
Optional add-ons
- Your branding: available on request. Header image, colours and tip presets in the guest experience.
- Place table codes: one signed QR code per table. Guests scan it, split the bill, add a tip, pay and receive a receipt by email, as a PDF or in Apple Wallet.
What you bring and what 934 brings
- What you bring: your Simphony organisation and location references, an Oracle API account per property, your acquiring contracts and Android devices for your terminals.
- What 934 brings: your Juno Portal, the terminal app, the guest web app, table codes and the payment gateway property.
- Afterwards: the Oracle session renews itself every 7 days. The API account password is only needed again if that renewal chain breaks. Releases and table codes are managed from the Juno Portal.
Need more help?
For questions about the onboarding, contact your Customer Success Manager or support@weare934.com. Have your property name and the step you are working on ready.
Comments
0 comments
Article is closed for comments.