Which settings do I need to change in DEV3 Balayo (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#salon-software#spa-booking#multi-tenant#saas-script
DEV3 Developer Forum
Every post is reviewed first. Usually reviewed within 24 hours.
Which settings do I need to change in DEV3 Balayo (payments, email, scheduled jobs) before it works for real customers? Is anything simulated by default?
#configuration#salon-software#spa-booking#multi-tenant#saas-script
Payments, SMS and push
The default is the simulated gateway, so booking and paying work without keys. You are the merchant of record: online money goes through the one gateway of the install and is paid out to salons, who cannot connect their own account. Real gateway drivers were not run against real accounts, and renewing a membership or subscription by saved card is not finished for real gateways, so the default is a pay link plus a grace period. Stripe refunds have no idempotency key yet, so review how retried refunds are handled before you take real card payments. SMS reminders are only written to the log, and real push was not exercised. There is one currency per install.
Cron
* * * * * php /path/to/balayo/artisan schedule:run >> /dev/null 2>&1
Every deadline (deposit holds, waitlist offers, memberships) is also enforced when a record is read, so a stalled cron never leaves a stale hold. The scheduled balayo:tick command catches records nobody is looking at and retries refunds.
Languages
English throughout. The home page and both apps also include Arabic with right-to-left layout; the Arabic text has not been reviewed by a native speaker.