Which parts of DEV3 Slotwise are simulated by default, and how do I switch them on?

Payments

The default gateway is Simulated: checkout shows a test card page with Pay and Decline buttons and charges nothing. To take real payments, open Settings → Payments, choose Stripe, PayPal or Razorpay, set the keys (they are stored encrypted), and register the webhook https://your-domain/dev3/webhooks/payments/<gateway> in the gateway's dashboard. The same gateway collects businesses' subscriptions and customers' deposits; each business's deposits are charged in its own currency.

Test with sandbox or test-mode keys first: the real drivers have not been run against live accounts. Subscription renewals on Stripe, PayPal and Razorpay leave the renewal invoice open until the gateway's webhook confirms payment, so the webhook must be reachable. Only the simulated gateway charges renewals by itself.

Cron and queue

Add one cron entry that runs Laravel's scheduler every minute:

* * * * * cd /path/to/slotwise && php artisan schedule:run >> /dev/null 2>&1

In cPanel choose Once per minute and use the full PHP path if needed. System → System health shows when the scheduler last ran. The scheduler runs:

• slotwise:send-reminders every 5 minutes: email and SMS reminders that are due
• slotwise:expire-holds every 5 minutes: releases bookings whose deposit was not paid in time
• saas:renew daily: renews subscriptions, ends trials and scheduled cancellations, and expires past-due accounts after the grace period
• dev3:demo-reset nightly, only when DEMO_MODE=true

Without the cron entry no reminders go out and unpaid holds keep their slots. The queue is sync by default (jobs run inside the request; nothing to set up). For a busy platform, set QUEUE_CONNECTION=database and run php artisan queue:work under Supervisor so emails go out in the background.

Mail

Until you set up mail, outgoing email is written to the log. Open Settings → Mail in /admin, choose SMTP and enter the host, port (587 for TLS or 465 for SSL), username, password and from address. Confirmations with calendar invites, reminders, reschedules, cancellations, invitations and invoice receipts all use it. In demo mode mail always goes to the log.

Two-factor sign-in

Every account can turn on two-factor sign-in from its profile (avatar menu → Profile): an authenticator app (TOTP) with 8 single-use recovery codes, or a 6-digit code by email (needs working mail).

• To require it for the platform team in /admin, turn on Settings → Security → Require 2FA for staff. For business teams (/app), staff (/staff) and customers (/account) it stays optional.
• A super-admin can click Reset 2FA on a user's row. If you lock yourself out, run php artisan dev3:2fa-reset you@example.com on the server.
• Secrets and recovery codes are encrypted with APP_KEY; if you change APP_KEY, reset 2FA for the affected users.
• In demo mode the one-click demo logins never ask for a code and 2FA can't be turned on.