PayTo for Car Rental: How to Cut Fees on Weekly Rent

Card fees are the quietest line item in a rental operation. Nobody budgets for them, nobody reviews them, and yet on weekly billing they compound faster than almost any other cost — because you pay them 52 times a year, per car.

Australia built a way out: PayTo. This guide covers what it is, the real numbers on what it saves, where cards still make sense, and how to switch a fleet across without disrupting renters.

What is PayTo?

PayTo is Australia’s modern direct-debit system, built on the New Payments Platform (NPP). Instead of storing a card, the renter approves a mandate — a standing payment authorisation — inside their own banking app. Once approved, you can debit their bank account directly on schedule, without card networks in the middle.

Three properties matter for a rental operator:

• Bank-to-bank. Funds move from the renter’s account to yours without Visa/Mastercard interchange — that’s where the fee savings come from.
• Real-time visibility. You see the mandate approved (or declined, or cancelled) the moment it happens, unlike legacy BECS direct debit where failures surface days later.
• Caps and consent built in. A mandate carries a maximum debit amount the renter agreed to, which makes the arrangement transparent and defensible.

How much does PayTo actually save per car?

On a $350/week rental billed through Stripe Australia, PayTo saves roughly $143 per car per year compared with a domestic card. Here is the math on published pricing (Stripe AU: domestic cards 1.7% + $0.30; PayTo 1% + $0.30, capped at $3.50 per debit):

The cap is what makes PayTo disproportionately good for weekly rentals: on higher weekly rates the card fee keeps growing with the amount, while the PayTo fee stops at $3.50. At $500/week the gap is already ~$280 per car per year. You can run your own fleet’s numbers in the savings calculator on our home page.

Why do fewer payments fail on PayTo?

Bank-account debits fail around 2.9% of the time, versus 7–15% for recurring card charges (GoCardless analysed 52M transactions; Visa and Mastercard put recurring card declines near the top of that range). Cards fail for reasons that have nothing to do with the renter’s ability to pay: expired cards, reissued numbers after fraud, hit daily limits. A bank account doesn’t expire.

For a weekly-billing business this is arguably worth more than the fee savings. Every failed charge is an arrear someone has to chase — subscription businesses lose roughly 9% of revenue to failed payments, and recovering it takes retries, pay-links and awkward conversations. Halving your failure rate halves that workload. (When failures do happen, here’s how to recover failed weekly rent automatically.)

Where do cards still make sense?

Cards keep three jobs even in a PayTo-first fleet:

• The first transaction. A walk-in renter can pay the deposit by card today and approve the PayTo mandate in the same checkout — you don’t lose the booking waiting for a bank authorisation.
• Large one-off charges. PayTo mandates carry a per-debit maximum. A charge above the cap — say an insurance excess — goes through a card or a one-off payment link instead.
• Fallback. If a renter’s mandate is cancelled, a saved card keeps rent flowing while you sort it out.

The practical answer is both rails, orchestrated: PayTo for the recurring rent (high volume, capped fee), card for edge cases. Which card processor to pair it with is its own decision — see Stripe vs Square for car rental in Australia.

How do you switch a fleet to PayTo?

Switching is less disruptive than most operators expect, because you migrate renters at natural touchpoints rather than all at once:

1. New bookings first. Make PayTo the default in your checkout for every new rental. The renter approves the mandate when they pay the deposit — one step, no extra friction.
2. Migrate existing renters at renewal. When a rental renews, send a payment link that sets up the mandate. Renters rarely object once they hear their card won’t be charged weekly anymore.
3. Set the mandate cap deliberately. Australian banks reject uncapped mandates. Set the maximum high enough to cover your top weekly rate plus reasonable charges, and no higher.
4. Wire up failure handling before you need it. PayTo debits are asynchronous — the result arrives after the debit is submitted. Your billing system needs to treat “pending” as in-flight (not failed), record real declines as arrears, and keep the schedule moving.
5. Watch for mandate cancellations. Renters can revoke from their banking app. Your system should flag revocations immediately so you re-collect payment details before the next cycle instead of discovering it as a surprise decline.

The last two steps are where DIY setups struggle: PayTo’s asynchronous behaviour doesn’t fit billing code written for synchronous card charges. Carz ships with PayTo as a first-class rail — mandates created at deposit checkout, weekly debits under the cap, async results handled, revocations flagged — as part of the payments and collections layer. Most established rental platforms don’t advertise PayTo support at all.

The bottom line

PayTo turns your biggest recurring transaction — weekly rent — from a percentage fee into a capped one, and cuts payment failures at the same time. For a 20-car fleet that’s roughly $2,860 a year in fees plus meaningfully fewer arrears to chase, for one change in how renters authorise payment. Few operational changes this small pay this well.