Stripe vs Square for Car Rental in Australia

Stripe or Square is one of the first infrastructure decisions a rental operator makes, and one of the stickiest — once fifty renters have cards saved with one provider, switching is a project. The honest answer is that they are built for different jobs: Stripe for online and recurring payments, Square for the counter. Weekly car rental needs both jobs done, which is why the comparison is worth doing properly.

This is that comparison, on Australian pricing, for the specific workload of a rental fleet: a deposit at booking, then the same card or bank account charged every week, plus the occasional toll, damage or excess charge on file.

How do Stripe and Square fees compare in Australia?

Stripe is cheaper online; Square is cheaper in person. Published AU pricing (Stripe, Square), applied to a $350 weekly rent charge:

Two things jump out. First, for the charge that repeats 52 times a year per car — the rent — Stripe’s card rate beats Square’s by ~$75 per car annually, and Stripe’s PayTo beats both by a wide margin because the $3.50 cap stops scaling with the amount (the full breakdown is in PayTo for car rental: how to cut fees on weekly rent). Second, Square’s flat percentages with no fixed cent fee make it slightly friendlier on small amounts — but rental billing is not made of small amounts.

Context worth knowing: the RBA is banning card surcharging from 1 October 2026 and cutting interchange caps (RBA media release, 2026). Once you can no longer pass card costs to the renter, the processor’s rate comes straight out of your margin — which makes the per-rail differences above matter more, not less.

Which handles recurring weekly billing better?

Both can charge a saved card on schedule; Stripe gives you more rails and better plumbing around it. The recurring workload has three parts, and the providers diverge on each:

• Saved instruments. Both support cards on file for weekly off-session charges — parity here. Stripe additionally supports PayTo mandates: the renter authorises once in their banking app, and every subsequent debit is bank-to-bank. Bank debits also fail far less — ~2.9% vs 7–15% for recurring cards (GoCardless, 52M transactions) — which means fewer arrears to chase every single week.
• Getting the instrument saved. Stripe has hosted checkout: you send a link, the renter pays the deposit and saves their card (or approves a PayTo mandate) from their phone, unsupervised. Square has no hosted subscription-setup link — saving a card means the renter is at your counter or reads the number over the phone. For walk-in-heavy operations that is fine; for remote handovers it is friction.
• Failure handling. Whoever you pick, declines are a when, not an if, and what matters is that your billing layer retries intelligently and sends the renter a self-serve pay link instead of you chasing (see recovering failed weekly rent payments). Both providers report outcomes by webhook; neither manages rental arrears for you.

What about setup effort and day-to-day usability?

Square is easier to start alone; Stripe is easier to build on. Opening a Square account and taking a payment the same afternoon is realistic — the dashboard is built for merchants, not developers. Stripe’s dashboard is more capable (per-charge webhook logs, granular refunds, risk detail) but assumes someone technical is wiring it up, and features like PayTo and hosted checkout only pay off once integrated into your billing flow.

In practice this difference disappears when the provider sits behind fleet software: the operator works in the booking screen — charge, refund, retry — and never touches either dashboard except for reconciliation. That makes the durable comparison the one above: rates, rails and failure behaviour, not admin UI.

Where does Square clearly win?

The counter. Square built its business on in-person payments and it shows: card readers from around $65, terminals that work out of the box, tap-to-pay, and a 1.6% flat in-person rate that beats Stripe’s online pricing. If your renters mostly walk in — pay the deposit at the desk, tap a card for a toll charge at return — Square’s hardware experience is genuinely better than anything Stripe offers an operator this size, and the money shows up in one simple dashboard.

Square’s weaknesses mirror that strength: the online/card-on-file rate is the highest in the table above, there is no PayTo or any bank-debit rail, and there is no hosted link for setting up recurring billing remotely. A fleet that bills every car weekly on Square cards pays roughly $400 a year per car in fees — about $218 more than the same car on PayTo.

Which should you choose for your situation?

The verdict depends on how your renters pay you, not on brand preference:

1. Weekly rentals billed remotely (gig-driver fleets): Stripe. Hosted checkout for the deposit + saved instrument, PayTo for the capped-fee weekly rent, cards as fallback. This is the lowest-fee, lowest-failure configuration available in Australia today.
2. Walk-in counter business with short rentals: Square. The hardware, the in-person rate and the simplicity outweigh the online premium when most payments happen face to face.
3. Both kinds of volume (most established operators): run both. Square at the counter, Stripe for recurring rent. The usual objection — reconciling two providers — is real if you work from two dashboards, which is why your fleet software should treat the provider as a detail: Carz supports Stripe, Square and PayTo on the same booking ledger, with every payment linked to its booking and its status derived from the provider’s webhook rather than a human tick (why that matters: never manually mark a payment as paid).
4. Already on one, tempted by the other: do not migrate saved cards for a marginal rate difference — migrate renters at natural touchpoints (new bookings, renewals) if the math justifies it, the way fleets phase in PayTo.

What does this cost across a fleet?

Fees compound quietly at 52 charges per car per year. A 20-car fleet at $350/week pays roughly $8,000 a year on Square cards on file, $6,500 on Stripe cards, and $3,640 on Stripe PayTo. The spread between the most and least expensive configuration is about $4,400 a year — real money for a decision most operators make once and never revisit. You can put your own fleet size and weekly rate into the savings calculator to see your number.

The bottom line

Stripe and Square are both good at what they were built for; the mistake is asking one to do the other’s job. For the payment that defines a rental business — the same amount, every week, per car — Stripe’s pricing and PayTo rail win on the numbers. For the counter, Square’s hardware and in-person rate win on experience. Pick for your dominant payment pattern, or pick both and let your software make the pair feel like one system.