Everything operators ask us

Signup takes under five minutes: company, first location, admin account and card. Once the first payment clears, your console is active and your renter-facing site is provisioned.

No. Adding locations, vehicles, categories and rates is all done through the console UI — no code, no imports required.

Book a demo and we'll walk you through the console on realistic data. Signup itself requires a card because your first month's payment activates the account — and you can cancel before any billing date.

Your card is vaulted with the payment provider at signup and charged monthly on your billing date. Invoices are itemized with provincial taxes and visible on the Billing page.

We retry automatically for several days and notify you. Accounts move to past-due before any suspension — updating your card restores everything instantly.

Yes. Move between plans as your fleet grows — vehicles, history and settings carry over.

None. Monthly billing, cancel anytime.

Stripe and Moneris for online card payments, Moneris Go pinpad terminals for in-person rentals, plus manual cash/debit recording for the counter. Each tenant picks their gateway in their merchant config.

Security deposits are card pre-authorizations — captured only if needed, voided on clean returns, with a full audit trail.

Never. Cards go straight to the provider's vault; we only keep a masked token (e.g. Visa •••• 4242) for display.

Yes — client admins manage the whole company, location managers run a branch, and agents handle counter operations. Access scopes per location.

Every charge runs through a 13-province tax engine — GST/HST/PST/QST with the right category rules per charge type, shown line-by-line on invoices and agreements.

Bilingual rental agreements (EN/FR) generate automatically per reservation with digital signature capture, plus check-out/return photo inspections that tie damages to charges.

Yes — customers can be flagged do-not-rent with a reason, and the flag surfaces at booking time.

Fully. Every tenant's fleet, customers, reservations and payments are scoped to their client ID at the database layer — there's no cross-tenant access path in the API.

JWT access tokens with refresh rotation, bcrypt password hashing, role-based authorization on every endpoint, rate limiting, and an audit log of sensitive actions.