Accept crypto payments at your self-storage facility

Why self-storage rent fails for reasons that have nothing to do with the tenant

Self-storage looks, from the outside, like the simplest recurring business in existence. You rent a locked box by the month. There is no inventory, no perishable stock, no service to deliver after move-in day, and the customer's belongings are sitting inside your collateral. Occupancy times rate equals revenue, and the whole thing runs on autopay.

Operators know it is not that simple, and the reason is specific: your customer is not there.

A restaurant sees its diner. A gym sees its member walk through the turnstile and notices when they stop coming. A storage facility often never sees the tenant again after the day they closed the roll-up door. The relationship is a unit number, an email address, a phone number and a stored payment credential — and of those four, three go stale on their own.

Now consider who ends up in a storage unit. The list is unusually mobile, and unusually likely to be mid-transition:

• Someone who sold or left a home and is between places — the classic move-in.
• Someone who moved to another country and left furniture, tools or family belongings behind, intending to sort it out "next year".
• Students storing a room over a long break, often with a parent abroad paying for it.
• Military, contract and rotational workers on deployment or long assignments.
• Snowbirds and seasonal residents who are physically in the facility's city for four months a year.
• Families holding a deceased relative's belongings while an estate is settled, sometimes from three different countries.
• Business tenants — e-commerce sellers holding stock, tradespeople storing tools, event and catering companies, sales reps with sample cases — who need an invoice, not a receipt.

That is a tenant base defined by relocation. And relocation is precisely what breaks the stored card, the local direct debit, and the phone number that receives the one-time code.

Four revenue lines that behave nothing alike

Monthly rent. The business. Recurring, due on a fixed day, month-to-month, and expected to keep charging for an average tenancy that in this industry is measured in many months or years, not weeks. It is also the single most fragile recurring charge you could design: a fixed amount, billed indefinitely, to a credential that belongs to someone who has physically moved.

Move-in and one-offs. The first month, the admin or set-up fee, the lock, the deposit where you take one, a truck or van rental, packing supplies. Time-critical: the tenant wants the unit today, and often is arranging it from the road, in the middle of a move, from a phone.

Prepaid terms and discounts. Six or twelve months up front in exchange for a rate — the healthiest cash in the business, and the payment most likely to be a large one-off from someone in a different banking system.

Fees and ancillaries. Late fees, lien and notice fees, overlock fees, cleaning or damage charges on move-out, boxes, tape, mattress covers, padlocks at the counter. Small, frequent, often paid in person by whoever happens to show up.

Four billing shapes, one manager — frequently one manager covering several sites, or a facility with no manager on site at all.

What a failed rent payment actually costs a facility

Involuntary churn is the quiet one. When a card fails on a monthly rent charge, almost nothing about the tenant has changed. Their belongings are still in your unit. They still want the unit. They simply have a new card number, or their bank declined an unusual recurring cross-border charge, or the step-up authentication went to a number that belongs to a different country now. Your system logs it as delinquency. It is not delinquency; it is a credential problem being processed as a moral failure, and it is the same failure mode we described in crypto subscriptions without chargebacks.

The delinquency machine is expensive to run. Late notices. Calls. Emails to an address the tenant checks monthly. Overlocking the unit — which is staff time, a second lock, and a physical trip to the door. Gate code suspension. Statutory notices. Advertising and running an auction. And through all of it the unit is occupied but not earning, which is worse than empty, because empty can be rented tomorrow.

Auction recovery is not a business model. Every operator knows what a lien sale actually returns against months of unpaid rent, notice costs, staff hours and the cleaning of the unit afterwards. It is a legal remedy, not a revenue line — and it exists because the payment failed, not because the tenant wanted out.

Rent can be reversed months later. Card scheme dispute rights run for a window measured in months, as set out in network materials such as the Visa Core Rules. A tenant who moved out in March and disputes January through March in June is disputing space you actually provided. Your evidence is a signed rental agreement and a gate-access log — genuinely good evidence, being read months later inside a process designed around parcels and tracking numbers.

Bank debits get returned too. Where rent is pulled by direct debit or ACH, the debit can come back — insufficient funds, closed account, or a consumer claim that it was unauthorised. Nacha's operating rules define return categories and time frames for exactly that, including a consumer's right to return an unauthorised debit well after the transaction date. From the facility's side, a return that arrives weeks later against a unit whose door has been open all month is indistinguishable from never having been paid.

The tenant abroad simply cannot pay you. This is the case that has no operational answer at all. Someone emigrated and left their belongings. They want to keep paying. Their new bank will not send a small recurring international payment cheaply, their old card was cancelled with their old account, and the remittance app they use pays out in local currency to a person, not to an invoice with a unit number on it. The World Bank's own remittance cost data makes the structural point: cross-border transfer cost is charged per transfer, not per percent, so a modest monthly rent is one of the worst possible amounts to send internationally. Twelve times a year, the friction is larger than the late fee you would charge.

The cash tenant at the counter. In many markets a real share of storage rent is still paid in cash by someone who drives over on the 3rd. That is unbanked or under-banked revenue with a security problem, a reconciliation problem and a record-keeping problem attached — and it does not disappear just because your software has an autopay screen.

The unmanned site. The industry has spent years moving toward remote management, kiosks and roaming managers who cover several facilities. Those sites still need to take money at the gate for a lock, a late fee or a walk-up rental, and installing an acquirer-issued card terminal at an unstaffed building is not an attractive answer.

And the payouts nobody budgets for. Cleaning crews between tenancies, the security patrol, gate and door maintenance, the locksmith who cuts overlocks, the haul-away crew after an auction, the part-time weekend manager, the referral partner who sends you every mover in town. A long list of small, frequent, individually-transferred payments.

Why cards, direct debits and wires each break on a storage unit

None of these rails is badly built. Each one assumes something a self-storage tenancy violates.

Card autopay assumes a stable credential and a stationary customer. Recurring card billing works beautifully for a customer who stays in one market and keeps one card for years. A storage tenant is, by definition, a person in motion — that is why they needed storage. The card behind the rent is the most likely thing in the relationship to change, and when it changes, nobody tells you.

Cards assume a merchant who can prove delivery. The dispute framework was built around goods in transit: tracking numbers, delivery confirmation, signatures. What you delivered is availability of a space for thirty days. Your proof is a rental agreement and a gate log. That is real evidence, and it is being evaluated by someone who has never read a storage lease, months after the month in question.

Direct debit assumes a domestic bank account that stays open. It is cheap and it works — until the tenant emigrates, closes the account, or claims the debit was unauthorised. Then you get a return, after the fact, with the door already having been open all month.

Wires assume a large amount and banking hours. An international transfer has a cut-off, a value date, a chain of intermediaries and a fee structure that makes sense on a shipment of machinery. On a monthly storage rent, twelve times a year, forever, it is an absurd instrument — and the tenant abroad knows it, which is why they stop.

Remittance apps assume a person, not an invoice. They move money to a relative's hands or local account, in local currency, at a rate the sender does not control, with no field your management software can match to unit B-214. Some tenants use them anyway, and your manager spends the morning working out who paid what.

All of them assume the payer's country lets money out easily. A large share of tenants in Latin America, and of emigrants paying for units they left behind, live with currency controls, transfer quotas, cards blocked for foreign recurring charges, or an official exchange rate nobody transacts at. For them a dollar-denominated stablecoin is not exotic — it is what they already hold. We wrote the general version in getting paid from abroad without a bank account.

How Payzum lets a self-storage facility accept crypto payments — at the gate and from abroad

Payzum is a non-custodial, crypto-only payment processor. Both halves matter here.

Non-custodial means the money never sits in a Payzum balance. It goes from the tenant straight to wallets your business controls. There is no processor float, no settlement batch, no reserve and nothing for a third party to hold back while the mortgage on the building, the property tax and the payroll fall due on fixed dates. The settlement is the payment.

Crypto-only means the rail is on-chain and the payment is final once confirmed — roughly 0.4 seconds on Solana, around two seconds on Base and Polygon. A tenant in another hemisphere can pay at 23:40 on a Sunday and your manager sees unit B-214 current before Monday's walkthrough. And because you can auto-convert to USDC or USDT, "crypto" does not have to mean price movement; see USDT vs USDC for payments for the difference between the two.

The instruments, mapped to how a facility actually bills

• Recurring subscriptions — the monthly rent. This is the flagship for this vertical. Rent charged on your billing day with nothing behind it that can expire, be reissued, or trip a step-up authentication on a phone in another country. A plan ends when the tenant ends it or you end it — not because a bank in a different hemisphere posted out new plastic.
• Invoices with an expiry, a unit reference and overpayment detection. Every invoice carries the unit number and the period, so a payment reconciles itself instead of arriving as an unlabelled transfer. Overpayment detection catches the tenant who rounds up, pays two months in one go, or adds the late fee to the rent without telling anyone. The expiry is set to the date that actually matters: your late-fee cut-off.
• No-code payment links. For move-in fees, the first month, a prepaid six- or twelve-month term, a truck rental, a cleaning charge on move-out, or a lock sold over the phone. Sent by email or WhatsApp to a tenant who is mid-move, in another city, on a phone.
• Hosted checkout and a drop-in plugin. Behind the "pay my unit" button in your tenant portal or website, so someone who wants to settle at midnight can, without calling the office.
• POS with a fresh QR per sale and PIN cashiers. At the counter for padlocks, boxes, tape, mattress covers and walk-up rentals, and at a kiosk or roaming-manager site where any phone becomes the terminal. One PIN per staff member with per-cashier analytics — which is how a multi-site operator gets a clean record of retail sales without a petty-cash tin. Mechanics in turning a phone into a crypto POS and crypto POS with PIN cashiers.
• CSV mass payouts and EVM stablecoin payouts. One file for the cleaning crew, the patrol, the locksmith, the haul-away team and the weekend manager — on Polygon, Arbitrum, Optimism, Base, BNB Chain or Avalanche, plus BTC/LTC/DOGE batches. The format is walked through in bulk crypto payments by CSV.
• REST API with signed webhooks. Your facility management software learns the unit is current the second the payment confirms: the account is marked paid, the dunning sequence stops, the gate code is restored by your own system, and nobody re-keys anything.

What actually happens on the 1st

The subscription charges, or the invoice for unit B-214 goes out with the unit number and the period as its reference. The tenant opens it wherever they are, pays from the stablecoin balance they already hold, and it confirms in seconds. Your manager sees the unit current, attributed correctly, with the reference attached. The funds are in your wallet — not in a processor's account, not in a batch that settles Tuesday, not in a rolling reserve.

If someone pays two months at once, or adds a late fee, overpayment detection surfaces it immediately instead of at month-end. And the payment does not come back in June.

The change is not primarily about speed. It is that the month is paid and stays paid — so the overlock, the notice and the auction stay reserved for tenants who genuinely stopped paying, rather than for tenants whose card issuer sent out a new number.

Honest scope: finality cuts both ways

On-chain finality removes chargebacks. It also removes your ability to reverse a payment that was made in error. Those are the same property seen from two sides, and a storage operator should understand it before switching anything on.

In practice it means two things. First, prorated move-out credits and refunds become payments you initiate, from your wallet, on your books, on your timeline — more control than a card rail gives you, and more responsibility. Overpayment detection and a clear refund clause in the rental agreement do real work here. Second, your rental agreement's provisions on billing day, late fees, notice, access suspension and move-out proration should be clear before you use a rail that does not permit third-party reversals, because the agreement is now the whole agreement.

What this rail does not do

Payzum is a payment rail. It is not your lien statute, your auction process, your notice requirements, your rental agreement, your insurance or tenant protection plan, your access control, your zoning or your tax engine. Self-storage lien and sale procedures are set by law and vary by jurisdiction, and nothing about the way a tenant pays changes a single step of them. Neither does it change what may be stored in a unit or your right to enforce that.

And the honest limit of any payment rail: no rail makes a tenant pay. A tenant who has abandoned their belongings will still abandon them, and you will still run the process the statute requires. What this removes is the far larger category of tenants who fully intended to pay and were stopped by an instrument — plus the payments that arrive late, arrive short, arrive unlabelled, or get pulled back months after the space was provided.

Volatility is a setting, not a risk

The objection every operator raises first: "I run on rate and occupancy — I cannot hold something that moves." You do not have to. Accept whatever the tenant holds and auto-convert to a dollar-denominated stablecoin — USDC or USDT — so what lands in your wallet is a dollar amount against a dollar-denominated rent. The chain is the transport; the stablecoin is the unit of account.

How it works, step by step

1. Connect your wallets. Create the Payzum account and point it at wallets your business already controls — most multi-site operators run one per facility so the site-level reporting stays clean. Turn on auto-convert to USDC or USDT and enable 2FA. Nothing sits with Payzum at any point.
2. Set up rent as a subscription per unit. Rate and billing day, per tenancy. When you raise the rate at the scheduled review, you change the plan — there is no stored card to re-authorise and no bank to re-approve a new amount.
3. Give every invoice a unit reference. Unit number plus period, expiry on your late-fee cut-off, overpayment detection on. This is what turns "a transfer arrived" into "B-214 paid September".
4. Create links for move-ins and prepaid terms. First month, admin fee, lock, deposit, six- or twelve-month prepay, truck rental. Sent to a tenant who is mid-move and closed the same hour, instead of holding a unit against a promised wire.
5. Put a PIN cashier on the counter — and on the roaming manager's phone. Locks, boxes, tape and walk-up rentals with a fresh QR per sale, under each person's own PIN, with per-cashier analytics across every site you run.
6. Connect your management software. REST API and signed webhooks, so a confirmed payment marks the unit current, stops the dunning sequence and restores the gate code through your own system automatically.
7. Run the payouts from one file. Cleaning crews, patrol, locksmith, haul-away and weekend cover in a single CSV — verifying any changed payee details out of band before you send it. Same rail, opposite direction.

Use cases at a self-storage facility

Five situations that happen in every facility with a mobile tenant base, and what each looks like on this rail.

• The tenant who emigrated and kept the unit. He moved abroad two years ago and left his tools and his family's furniture in a 10×10. His old card died with his old account; his new bank charges more to send the rent than the rent is worth. On a subscription paid in stablecoins, he pays from the balance he already holds, on your billing day, from any country, for as long as he keeps the unit — and your manager stops writing him quarterly emails.
• The card that was reissued, not cancelled. A long-standing tenant's rent fails on the 1st. Under the old rail, that starts the late fee, the call, the overlock and eventually a notice. On a subscription with no card behind it, there is nothing to reissue, so the charge simply does not fail for that reason — the delinquency process is reserved for people who actually stopped paying.
• The move-in arranged from the road. A family in the middle of a relocation needs a unit today, arranged by phone from a highway. You send a payment link for the first month plus the admin fee and the lock; it confirms in seconds; the unit is committed with the money already received. It is the same moment the movers see — the adjacent case we covered in crypto payments for a moving company.
• Twelve months prepaid by someone else. A daughter abroad prepays a year on her late father's unit while the estate is settled, from a different country and a different banking system, in one payment that arrives whole and reconciles to the unit number instead of landing as an unlabelled international transfer.
• Saturday at the counter, and the Friday payout run. Padlocks, boxes and tape sold on a QR generated for that sale under the manager's PIN, with per-cashier analytics per site — no cash tin. Then one CSV on Friday for the cleaning crew, the patrol and the locksmith, settled the same day, with payee details verified out of band beforehand.

Payzum vs card autopay and bank debits for a self-storage facility

Common objections, answered

"Our tenants are ordinary people. They don't hold crypto."

Most of them do not, and this is not for most of them. It is for the slice of your rent roll that is already painful: the tenant who emigrated, the parent paying from abroad for a student's unit, the family settling an estate across two countries, the tenant whose card fails every few months, and the business tenant who would rather pay an invoice than hand over a card. Run it alongside what you already accept. The rest of your tenants will never notice, and you should not ask them to.

"Doesn't this just move the delinquency problem?"

It splits it in two, which is the point. Delinquency in storage is a mix of tenants who cannot or will not pay, and tenants whose instrument failed while they fully intended to. The first group needs your lien process and always will. The second group is a payments problem that has been misfiled as a collections problem for years, and it is the group this fixes — quietly, on the 1st, without an overlock and a notice.

"We already have autopay in our management software. Why add anything?"

Because autopay is only as durable as the credential behind it, and it does nothing at all for the tenant whose banking system will not cooperate across a border. Payzum sits alongside your existing methods and connects back to the same software over REST and signed webhooks, so a confirmed payment marks the unit current in the system you already run. If your rent roll is entirely local and your involuntary failures are rare, you do not need this. If a meaningful share of your tenants are somewhere else, you do.

"What about our accountant?"

Rent collected in USDC is rental revenue, recorded on the day it is received, at the value of that day, against the unit and the period — the same as any other payment. Your lease, your rate schedule, your ledger and your tax obligations are unchanged. What changes is that the receipt reconciles cleanly to a unit reference instead of to a partial transfer with an unreadable description. Confirm treatment in your jurisdiction with your own accountant; we are a payment rail, not your adviser.