IN THIS ARTICLE▾
An EFT debit-order mandate collects monthly self-storage rental more reliably over a full tenancy than card-on-file billing does.
"We just charge the card on file" is a common answer when a storage operator describes how they collect monthly rental. It's an understandable choice, card-on-file billing is quick to set up, familiar from e-commerce, and doesn't require the tenant to complete a debit-order mandate at the desk. For a genuine month-to-month, self-service business model, it looks like the simpler option.
The friction shows up over the life of a tenancy, not at sign-up. Cards expire. Cards get replaced after fraud or loss. Cards decline on insufficient funds in ways that are, structurally, no less common than a failed debit order, and every one of those failure modes requires the tenant to go back and re-enter new card details before billing can resume. Over a tenancy that runs for months or years, that failure rate compounds in a way it doesn't for a single e-commerce purchase.
This piece compares the two rails specifically for monthly recurring storage billing, not for one-off transactions where card is unambiguously the better fit.
Why card-on-file works well for one-off purchases
Card payments are excellent for what they were built for: a single, in-the-moment transaction where the customer is present, actively authorising the exact charge, and the relationship ends once the purchase completes. E-commerce, retail, and once-off service payments all fit this shape well.
Why the shape changes for a multi-month tenancy
A storage tenancy isn't a single transaction, it's a recurring relationship that can run for months or years, with the same card expected to keep authorising the same (or a variable) amount every cycle without the tenant actively doing anything. That's a different demand on the payment method than the one it was originally designed for.
Three things happen over a long tenancy that don't happen in a single e-commerce transaction. Cards expire, every card has an expiry date, and a rental that outlasts the card's validity period simply stops collecting until the tenant proactively updates their details. Cards get replaced, lost, stolen, or reissued cards break the billing chain immediately, with no notice to the facility until the next failed charge. Cards decline, insufficient funds, issuer-side holds, and processor-level declines interrupt collection in ways a tenant may not notice until they get a call about an overdue account.
Each of these requires active tenant intervention to resolve, updating card details, re-entering a new number, which means the facility's collection depends on the tenant remembering to do so, exactly the dependency automated billing is supposed to remove.
Why an EFT debit-order mandate holds up differently
A debit-order mandate authorises the facility to collect against the tenant's bank account directly, rather than against a card that expires and gets replaced independently of the tenant's banking relationship. Bank accounts don't expire on a three-year cycle the way cards do. A mandate signed once at move-in continues to authorise collection for the length of the tenancy without a card-refresh step interrupting it.
This doesn't mean EFT debit orders never fail, insufficient funds and account closures happen on this rail too. What's different is the failure doesn't have a structural expiry date built into the payment method itself, which removes one entire category of interruption that card-on-file billing carries by default.
What this means for a facility's month-to-month recurring revenue
Fewer interruptions mean fewer tenants needing an active follow-up call just to keep their existing account current, which is a different, lower-effort kind of follow-up than chasing an actual default. It also means the operations team spends less time on "please update your card details" admin and more time on the accounts that are genuinely in arrears.
What this isn't
It isn't a claim that card payments have no place in a storage facility's billing. Move-in deposits, packing-supply purchases, or a tenant's genuine preference for card can all be accommodated, the comparison here is specifically about the primary rail for ongoing monthly rental collection, not every transaction type a facility handles.
It isn't a claim that EFT debit orders never fail. They do, for the same underlying reasons any collection can fail, insufficient funds, disputes, closed accounts. The comparison is about which rail is structurally more resilient over a long tenancy, not about which rail is failure-proof.
It also isn't an argument against offering card as an option for tenants who specifically prefer it. Recurv can run recurring card collection alongside EFT debit orders for facilities that want to offer both, the point of this piece is simply that defaulting to card-on-file as the *only* rail for long-running monthly billing carries a reliability cost worth knowing about upfront.
Related reading
See how Recurv handles recurring billing for long-term storage.
View Long-term Storage use case →