Integrations

Works with the stack you already run

Lotably connects to the payment, session, and printing tools parking operators already use. Parking BOXX sync, ParkMobile sync, and manual or CSV sessions can run together. When another vendor offers an API, we build the connection at no extra cost (the vendor may charge for API access).

  • Parking BOXX

    Paid-session sync

    Connect your credentials and paid sessions sync every couple of minutes, matched to each lot, so officers see what drivers already paid at your stations.

    How it works
  • ParkMobile

    Paid-session sync

    Connect your ParkMobile account and choose a lot for each zone. Paid sessions sync every 2 minutes, and the plate check asks ParkMobile directly for a plate it hasn’t seen yet, so officers see drivers who paid in the app moments ago.

  • Stripe

    Payments and payouts

    Citation, daily parking, monthly parker payments, and merchant invoices run through your own connected Stripe account. The money settles to you, not to a vendor balance.

  • Plate reading

    Built in

    The officer app reads the plate from a photo, so there is nothing to buy or set up.

  • Manual and CSV sessions

    Any lot, no API

    No connected equipment? Import daily sessions by CSV or key them in, and any lot can be enforced, whatever it runs today.

  • Mobile printers

    Printed tickets

    Print tickets to Brother mobile printers straight from the officer’s phone; Zebra on Android is in testing. Ordinary phones work out of the box.

  • Email and text receipts

    Under your brand

    Ticket and pay-by-plate receipts and driver notices go out by email under your name. Drivers who buy a pass can get the receipt by email or text.

Check every enabled source and see when one needs attention

Officers check Lotably permits, guest passes, and parking passes alongside enabled outside sources. Parking BOXX, ParkMobile, and manual or CSV sessions can be enabled at the same time. Map each outside site to the correct Lotably lot before relying on its sessions.

Payment system health shows the last successful sync, failures, stale data, and unmapped sites. Officers see a warning when a relevant system cannot be verified. A warning is information for the officer; it is not an automatic stop on issuing citations.

Using another pay station, gate, or payment app? When the vendor offers an API, we build the connection at no extra cost. Some vendors charge for API access; that fee is set by the vendor and paid to them. Until the connection is live, add those sessions by hand or by CSV. Permit-card tracking does not imply gate access control.

Read the payment-system health guide →

Run something else? Manual and CSV import cover any lot today, and we scope new connections with you. Call or email us and tell us what you run.

Keep your stack. Add the enforcement layer.

Start free and set up alongside the equipment you already run, or call us to talk through how Lotably fits your vendors.

No credit card for the Free plan · Month to month · Questions? Call +1 (513) 348-3049