Stripe
Card payments run as direct charges on your own connected account. You are the merchant of record: you hold the funds, you own the refunds and the disputes, and the payout lands in your bank rather than passing through ours.
Integrations
It plugs into what you already run.
No migration of your email address, no new payment provider, no separate app for your drivers to install before they can work. The things you already pay for keep doing their jobs.
- Your mailbox
- IMAP + SMTP
- Payments
- Stripe Connect
- API
- Keys + webhooks
Your mailbox
Your inbox stays yours.
Each company connects its own mailbox directly. There is no shared sending address, no broker sitting between you and your clients, and no OAuth consent screen that a provider can revoke on a Tuesday and take your enquiries with it.
- Transport
- IMAP for reading, SMTP for sending
- Credentials
- Held per company, not per platform
- New mail
- IMAP IDLE watch, with polling as the fallback
- Sent items
- Read back, so replies you send elsewhere still thread
- The address clients see
- Yours - the one they already write to
Everything else
Six connections, each one optional except the money.
Google Maps
Distance, duration, geocoding and address autocomplete. A parsed address is only pinned when Google returns a verified match - an approximate one leaves the coordinates empty and raises a confirm-with-the-customer warning instead of guessing.
Flight tracking
Airport transfers can watch the flight through AeroDataBox, per leg. It is off unless you turn it on, and it alerts rather than silently moving your pickup time - shifting the booking automatically is a separate switch that ships off.
Push notifications
Browser push over VAPID and native push through Firebase Cloud Messaging, both from the same subscription list. Missing keys degrade to no push, not to a broken app.
Developer API
Server-to-server keys with default-deny scopes: a key reaches only the endpoints you granted it, and is rate-limited on its own budget. Outbound webhooks carry delivery history and a manual test fire. Business plan.
Anthropic
The one AI vendor, named rather than described as a partner. It reads incoming enquiries and drafts quotes; what it produces is a draft you approve, not a message that leaves on its own.
What is not here
The integrations we do not have.
A short list, because a long one usually means most of it is a logo on a page. There is exactly one AI vendor and it is named above - no OpenAI, no Gemini, no rotating pool of models you cannot audit. Accounting packages are export-and-import today rather than a live sync, and text messaging is not a product you can switch on.
Questions
Do I have to change my email address?
No, and that is the point. You connect the mailbox you already publish. Clients keep writing to the same address, and the replies leave from it.
What if my mail host is not on your list?
There is no list. If your provider speaks IMAP and SMTP - and effectively all of them do - you enter the host, the port and the credentials, the same details your mail client already uses.
Does my client see Stripe or 4fleet on the statement?
Neither. The charge sits on your own connected account, so your trading name is what appears. The payment link carries your branding for the same reason.
Can I get my data out through the API?
Yes, on the Business plan, with an API key scoped to the endpoints you choose. If you are not on Business, ask us and we will export it for you - the data is yours under the terms, and we are not going to hold it behind a plan.
What happens if an integration is down?
The parts degrade separately. Without maps you lose distance on a quote, not the quote. Without flight data a transfer runs as an ordinary job. Nothing here takes the app down with it.
Connect one mailbox and watch what lands.
The first enquiry that arrives after you connect is the whole demonstration.