Limo company credit card processing: keep your own merchant account

For most limo companies, the best credit card setup is a merchant account in your own name, connected to your dispatch software, rather than processing bundled into the software. You keep your negotiated rate, your processing history and your saved cards when you change software. Built-in processing is easier on day one, but you pay the vendor's rate for as long as you stay.

Card fees come off the top of almost every trip you run. The corporate account that books every week, the wedding deposit, the 4am airport run paid on a card at booking: each one pays the processor before it pays you. That makes your processing rate a cost worth the same attention as insurance or fuel.

This guide explains the two models in plain terms, runs the arithmetic on what a rate difference costs, and covers the parts people forget until they hurt: chargebacks, saved cards and double charges.

Merchant account vs built-in processing: what's the difference?

There are two common ways a limo company ends up taking cards.

Your own merchant account

You open an account with a processor or gateway, such as Authorize.Net, Stripe, Square or a merchant services provider. You negotiate or accept a rate. Your dispatch software connects to that account and sends charges through it. The money settles to your bank under your agreement with the processor. If you change dispatch software, you connect the same account to the new system.

Built-in processing (payment facilitator model)

The software company is, or partners with, the processor. You sign up for payments as part of the software. Setup is quick because the vendor has already done the heavy lifting with the card networks. In exchange, the rate is the vendor's rate, and the account lives inside the vendor's platform. This model is often called a payment facilitator, or PayFac.

Neither model is wrong. Built-in processing makes sense for a brand-new company with no processing history and no time for applications. The trouble starts when a growing operator is still on a rate chosen for someone else, and moving it means moving everything.

Why the processing rate matters: the arithmetic

Rates look small because they are percentages. Multiply them by a month of card volume and they stop looking small.

Say your company runs $40,000 a month through cards, and the difference between two rates is 0.5 percentage points:

• $40,000 × 0.005 = $200 a month
• $200 × 12 = $2,400 a year

That is the cost of half a point, before any per-transaction fee. The per-transaction fee matters too. If those $40,000 come from 400 charges averaging $100, a $0.30 fee is 400 × $0.30 = $120 a month on its own.

Now a fuller example, using a published rate. As of September 2026, the Moovs Standard plan lists a card rate of 3.4% + $0.30 on its pricing page. On the same $40,000 in 400 charges:

• 3.4% of $40,000 = $1,360
• 400 × $0.30 = $120
• Total: $1,480 a month

Suppose your own negotiated rate works out to 2.9% + $0.30. That number is only for the arithmetic; use the real figure from your own statement.

• 2.9% of $40,000 = $1,160
• 400 × $0.30 = $120
• Total: $1,280 a month

The difference is $200 a month, the same half point as before. Pull out last month's processing statement, find your effective rate (total fees divided by total volume), and run the same sum against any plan you are considering.

Why portability matters more than the rate

The rate is what you pay. Portability is whether you can leave.

When processing is part of the software, changing software usually means changing processor at the same time. That brings a new application, possibly new underwriting, and the job nobody enjoys: asking every regular client for their card again because the saved cards stayed behind in the old platform.

With your own merchant account, processing and dispatch are separate decisions. You can change software without touching your processor, or change processor without touching your software. Your saved cards live in your own gateway account. Your processing history stays under your name, which helps when you ask for a better rate later.

For an operator with corporate accounts, this is the big one. A travel desk that has a card on file with you does not want a call asking for it again because you changed vendors.

What Moovs and Limo Anywhere do with payments

Both are established platforms, and both offer in-house processing. As of September 2026:

• Moovs. Payments run on Moovs Payments, which is built on Stripe. The card rate is built into each plan on the Moovs pricing page: 4% + $0.30 on Test Drive, 3.4% + $0.30 on Standard and 3% + $0.30 on Pro. Moovs is well built and well reviewed. The trade-off is that the rate comes with the plan, not with your negotiation.
• Limo Anywhere. The Limo Anywhere pricing page lists in-house processing, Limo Anywhere Pay, powered by Fullsteam. Ask whether you can keep your own merchant account on the plan you are considering, and what it costs if you do.

Whatever vendor you talk to, ask the same three questions: who is the processor, can I bring my own merchant account, and where do my saved cards go if I leave. We compare the platforms in more detail on our Moovs comparison page and Limo Anywhere comparison page, and in our guide to Moovs alternatives.

Chargebacks and AVS: how to protect yourself

A chargeback is a customer telling their bank they did not authorize a charge or did not get what they paid for. In ground transportation the usual story is a no-show dispute, a cancellation argument, or a card used by someone other than the cardholder.

You cannot prevent every dispute, but you can make them easier to win and less likely to start:

• Use address verification (AVS). AVS checks the billing address the customer gives against what the card issuer has on file. Requiring it makes a stolen card number harder to use, because the thief also needs the right address.
• Keep a record of what happened when. A time-stamped log of dispatch, driver arrival and passenger pickup is the evidence a bank asks for.
• Capture proof at the curb. Arrival confirmation tied to the pickup location, and a required photo when the passenger does not show, turn "the driver never came" into a question you can answer.
• Put your cancellation policy where the customer agrees to it. Before the card is charged, not in an email after.
• Charge the card the customer expects. Mark whether a card is personal or business so month-end charges land on the right one.

In LimoGrid, the optional AVS requirement on Authorize.Net uses the billing account's ZIP. The trip time log, attachments on reservations, no-show handling, and geofence and attachment gates in the driver app give you the paper trail when a dispute comes in.

Saved cards: the client who books every week

Saved cards are what make repeat business easy. The executive assistant who books by email at 11pm should not have to read a card number over the phone every time.

Two things matter here: where the card data goes and who can charge it.

On Authorize.Net, LimoGrid uses Accept.js, a hosted card form, so card data never touches your servers. Saved cards are stored as customer profiles in the gateway's vault. Each account can hold several cards, you can update or delete them, and a dispatcher can charge a saved card straight from the reservation. For new customers, a PayLink lets the passenger enter and save their own card, so nobody on your team handles the number at all. We cover that workflow in pay links for limo companies.

Idempotency: why a retry should never double-charge

Here is a scene every dispatcher knows. You click charge, the screen hangs, the Wi-Fi drops, you click again. Did the customer just pay twice?

The fix is a technical one called an idempotency key. Every charge request carries a unique key. If the same request arrives twice, because of a retry, a double click or a flaky connection, the system recognizes the key and processes it once.

LimoGrid uses idempotency keys on payments and invoice charges, so a retried request does not double-charge. It is not a feature anyone puts on a brochure. It is the difference between a quiet Tuesday and a refund plus an apology email to your best corporate client.

How LimoGrid handles credit card processing

LimoGrid is not the processor. You connect your own merchant account: Authorize.Net, Stripe, Square or Midwest. The rate you negotiated stays yours.

• No markup on your cards. No per-trip charge on any paid plan, and processing fees go to your processor, not to us. See pricing.
• Charge and void from the reservation, with saved cards per account.
• PayLink to collect payment for a reservation or an invoice, with tips.
• Corporate invoicing with one payment applied across several open invoices. More in corporate account billing and on the billing page.
• Net profit reporting. The sales revenue report shows net profit after driver pay, tax, credit-card and badge fees, so you can see what card fees actually cost you each month.

Frequently asked questions

Do limo companies need a merchant account?

If you take cards, you need some kind of processing account. A merchant account in your own name gives you control of the rate and makes it easier to move software without re-collecting saved cards. Built-in processing is faster to set up but ties the rate to the software vendor.

What is a good credit card processing rate for a limo company?

It depends on your volume, average ticket and card mix, so compare your own effective rate (total fees divided by total card volume) against any offer. Even half a point matters: on $40,000 a month of card volume, 0.5% is $200 a month, or $2,400 a year.

Which processors work with LimoGrid?

LimoGrid connects to Authorize.Net, Stripe, Square and Midwest. You keep your own account and your own negotiated rate.

Can I keep my saved cards if I switch dispatch software?

With your own gateway account, saved cards stay in that account rather than with the software vendor. With built-in processing, ask your current vendor how saved cards are handled when you leave before you sign anything new.

How do I stop double charges when a payment screen hangs?

Use software that sends an idempotency key with every charge, so a retried request is processed once. LimoGrid does this on payments and invoice charges.

If you want to see your own processor connected to a dispatch board, with saved cards, AVS and PayLink working together, book a demo and bring last month's processing statement. We will run the numbers with you.