🍺 Pub & Restaurant

License keys are issued uniquely per purchase. For typical self-host plans, one production hostname is registered on first successful validation/check-in and counts toward max_activations (usually 1). Moving to another domain normally requires a controlled deactivation of the old install or purchasing an additional seat — buyers should assume the binding is permanent for that URL unless your order terms say otherwise.

The installation phones home to your configured LICENSE_SERVER_URL (license_validate.php on use, license_check_in.php periodically). On the first production activation, the API may return license_binding_notice in JSON — installers should show that text once so operators understand the hostname pairing. Your administrator should schedule daily cron/license_enforcement.php on the license hub to reconcile dormant installs, payment status, and multi-domain breaches.

Payment standing: licenses store subscription status; validation rejects non‑trial/non‑active states (e.g. past_due, cancelled) so overdue accounts align with your payment defaults.

Commission-bearing features (where the platform owner earns on downstream sales) must be enabled per product and wired to your hub ledger — the nightly enforcement job can aggregate reseller commission where configured.

Payments & gateways: each self-hosted tenant must supply their own processor keys in admin payment settings. Do not ship or embed the vendor’s production gateway credentials in customer builds.

Owner/admin customer checkout options: all self-hosted program copies use the shared payment settings layer, so the program owner/admin can decide which providers their own customers see at checkout or on invoice links.

• Stripe: Card checkout using the owner/admin Stripe-connected account or site keys, depending on the deployment model.
• PayPal: PayPal wallet and linked-card payments using the tenant’s own REST credentials.
• Square: Hosted Square checkout using the owner/admin access token and location ID.
• GoCardless: Open banking / bank-pay style checkout using the tenant’s own GoCardless access token.
• Revolut: Hosted Revolut Business checkout using the tenant’s own API key.
• SumUp: Hosted SumUp checkout using the tenant’s own API key and merchant code/email setup.
• Bank transfer: Owner/admin bank details shown to customers for invoice and manual settlement flows.
• Cash: Manual local-payment option for delivery, collection, or in-person service businesses.

Cross-network listings & directory: optional federation (sharing listings across hub programs) and tiered directory placement are roadmap items — when enabled, tenants should keep sharing on unless they accept reduced discovery; eligibility is constrained by business type and subscription tier.

Minimum server stack

• PHP 8.1+ (8.2+ recommended). CLI PHP should match the FPM/mod_php version used by the web server.
• MySQL 8.0+ or MariaDB 10.5+ with InnoDB, utf8mb4, and binary logging optional (for replication).
• PHP extensions: mysqli, curl, json, mbstring, openssl, fileinfo, intl, zip, gd (Imagick optional if image pipeline supports it)

php.ini / runtime settings

• memory_limit — 512M or higher recommended for imports, image processing, and reports
• max_execution_time — 60+ for long-running admin tasks (some hosts cap lower)
• upload_max_filesize / post_max_size — Large enough for photography, documents, and CSV imports (e.g. 32M+ each)
• allow_url_fopen — Often required for webhooks and HTTP integrations (or use curl)

Program-specific load notes

• HTTPS (TLS) is required for production so browsers allow secure cookies, payment redirects, and PWA features.
• Scheduled tasks: configure cron (or Windows Task Scheduler) for app crons under cron/ — especially license_enforcement.php daily.
• Outbound HTTPS to your configured LICENSE_SERVER_URL must be allowed for validation and daily check-ins.

Installation & setup checklist

1. Database: create empty schema and a dedicated DB user with least privilege (SELECT/INSERT/UPDATE/DELETE + DDL only during install).
2. Web root: deploy files, point document root at the public entry (per your package layout), and set directory permissions for storage/ and config/.
3. Credentials: run the guided installer / bootstrap where provided, then paste the license key issued after purchase.
4. License: on first successful production validation, the key is bound to that hostname — see licensing panel below.
5. Payments: configure your own Stripe, PayPal, Square, GoCardless, Revolut, SumUp, Bank transfer, Cash settings in tenant admin — self-hosted copies never rely on the vendor’s default gateway credentials.

Platform operators track activations, domains, and check-ins in the internal Licenses administration area; contact your vendor for domain transfers or resets.