SCRIPT LAB GUIDE / SOLUTION GUIDE
Paiements
One workspace for transactions, history, terminals and payment security for Estate OS and Ads OS. Open Workspace management → Payments, with each service’s permissions.
GETTING STARTED
The steps at a glance
- Prepare the listing in its service
- Collect payments with shared objects
- Track transactions
- View events and reminders
Questions & troubleshooting
4 articles · Open a question to see the steps.
Sort list
Where do I find payments and history?Payments · Utilisation
- Open Transactions or History in Workspace management → Payments.
- The Source service filter distinguishes Estate OS and Ads OS. Team permissions limit accessible data.
- A listing’s history links always open that object’s events. Visit rewards remain in Pay2Visit.
How do I manage terminals and HUDs?Payments · Objects
- Terminals and HUDs groups shared platform devices, including older Estate OS terminals.
- Enable or disable selected terminals. These shared actions require management rights for the relevant services.
- HUD owners groups authorised tenants without duplicating people who own multiple HUDs.
- Blocking a user prevents new payments only on your platform.
Is a new licence required?Payments · Accès
- Payments is included with Estate OS and Ads OS rental services.
- Listings, rates and tenants stay managed in their source service. Grouping does not change existing rentals or transactions.
Where do I set access, notifications and security?Payments · Navigation
- Workspace management → Payments groups Transactions, History, Terminals and HUDs, Security and Blocked users. Rental Network remains the shared rental engine; it adds no separate service to manage.
- Team and access groups each person’s permissions and allowed notifications. Each service’s configuration defines its settings and outgoing events.
- Go to… searches accessible destinations and visible page sections. Save useful pages in My shortcuts.