Is there anything DEV3 Balayo does not do?

Good to know

• You are the merchant of record. Online money goes through the one gateway of your install and is paid out to salons, so salons cannot connect their own Stripe account.
• Card terminals are recorded, not integrated. The till notes a card payment taken on a terminal; it does not talk to the terminal.
• There is no card-on-file no-show fee. Deposits are supported; charging a saved card after a no-show is not.
• Auto-renew on a real gateway needs developer work. Memberships and salon subscriptions renew by a pay link and a grace period by default; charging a saved card automatically on a real gateway needs buyer work.
• Stripe refunds have no idempotency key yet. A gateway timeout after a refund was accepted can be retried, so review retried refunds before you take real card payments.
• The staff app needs a connection. Visits, stages and the till are written on the server as they happen.
• One currency per install.
• SMS reminders are only logged. They are written to the log and not sent.
• "Add to calendar" copies the .ics text. The client app has no share sheet for it.
• Desk booking is in /business, not the staff app. The staff app has no booking endpoint.
• The apps were tested on simulators only. They were not run on physical devices, and the Android and iOS builds are debug builds.
• Payments, SMS and push are simulated by default. The simulated gateway works out of the box. Real gateway drivers were not run against real accounts, and real push was not exercised.
• Arabic has not been reviewed by a native speaker.
• Use MySQL or MariaDB on a live site. Tests run on SQLite, where row locks do nothing; the concurrency checks run on MySQL 8.
• Name: Balayo is a working name checked by a web search only, not a trademark clearance. Check it before you launch under it.
• No hosted demo. Every salon, client and record in the screenshots is fictional. The photos are free-licence stock photos and are credited in the package.