SStorageFlo.io
See how it worksGet started
Payments

Add payment flexibility without rebuilding your stack

Connect Stripe or Square inside the booking flow. UK operators launch with the gateway they already use, with VAT applied automatically based on your billing details.

View integrations
Renter card
4242 4242 4242 4242
Aria Park05/29
StripeLive
StatusAuthorize
SquareLive
StatusAuthorize
Pay-on-siteFirst-class
StatusReserved
Card data stays outStripe and Square handle the card surface. StorageFlo.io stores processor references and reservation status, never card numbers.
Live gatewaysStripe live. Square live. Other gateways tracked on the public roadmap; we do not present them as live until they ship.
Pay-on-site is first-classOperators capture reservations even before a gateway is connected. The widget keeps working; deposits settle at the facility.
What changes

Stripe, Square, or pay-on-site - all part of the same booking.

Live gateways or a first-class on-site path. Card data stays with the supported processor; reservation status stays with the booking.

01 - Tap to pay

The payment moment is the same instant

When a renter is ready to reserve, the card surface appears in-flow. Stripe or Square handles the contactless tap; StorageFlo.io keeps the reservation, pricing, and confirmation context wrapped around it.
  • Card surface stays with the supported processor.
  • Authorization fires the moment the renter chooses to pay.
  • Failed taps return the renter to the same reservation, not a dead end.
Reservation summary
A-204 - 10x10 climate
Held for 10 min
Renter card
4242 4242 4242 4242
Aria Park05/29
Authorization
Approved - $129.00
02 - Three branches

Stripe, Square, or pay-on-site

Stripe and Square are live today. Other gateways are tracked on the roadmap. Pay-on-site is a first-class branch, not a footnote - operators can capture reservations even before a gateway is connected.
  • Stripe live. Square live. Other gateways tracked on the public roadmap.
  • Pay-on-site captures the reservation and settles the deposit at the facility.
  • Each branch shares the same reservation; only the settle path differs.
One reservation - three valid paths
  • StripeLive
    Card surface stays with Stripe. Operator merchant relationship stays where it is.
    StatusAuthorize
  • SquareLive
    Square handles the card data and merchant relationship. Operator chooses where the funds settle.
    StatusAuthorize
  • Pay-on-siteFirst-class branch
    Reservation captured, deposit settled at the facility. Widget keeps working without a gateway.
    StatusReserved
Other gateways (Authorize.net, Helcim, Moneris, PayPal) appear on the public roadmap, not the live list.
03 - Processor boundary

Card data stays with the processor

Stripe or Square owns the card surface and the merchant relationship. StorageFlo.io stores processor references and reservation status, never raw card numbers. The boundary is visible to the renter and to your finance team.
  • StorageFlo.io stores processor references, not card numbers.
  • Merchant account stays with the processor your team already chose.
  • Refunds and disputes flow through the processor, then sync back to the booking.
Processor boundary
Card data stays with Stripe / Square
Processor (Stripe / Square)
  • Card number
  • CVV
  • Authorization
  • Capture
  • Refund processing
StorageFlo.io
  • Reservation ID
  • Processor reference
  • Status (Held / Captured / Refunded)
  • Last 4 digits (display)
We never store raw card numbers. The merchant account, settlement schedule, and dispute handling stay with the processor your team already chose.
04 - Reservation ledger

Authorize, capture, refund - all on the booking

Every monetary event lives on the same reservation timeline as the booking, the lease, and the move-in message. Operators do not stitch the picture together across tools.
  • Authorize / Capture / Refund states render with `tabular-nums`.
  • Disputes and chargebacks attach back to the reservation.
  • Pay-on-site reservations show as `Held` until settled at the facility.
Reservation ledger - A-204
On the booking
  • Reservation heldHeld129.00
  • Stripe authorizeAuthorized129.00
  • Stripe captureCaptured129.00
  • Day 4 refund (partial)Refunded12.50
Payments questions

Answers operators ask before they switch.

Real questions from real operators. Straight answers, no sales speak, no jargon, no implementation project.

No. Card details stay with the supported processor. StorageFlo.io stores processor references and the resulting payment status; raw card numbers are not held by the booking layer.

Common operator scenarios

The feature set is built around the moments that slow operators down. Less phone tag. Fewer handoffs.

A small RV lot, a growing multi-location operator, and a regional manager do not buy for the same reason. The page needs to show each of them where StorageFlo.io removes friction.

After-hours booking path

“A customer can reserve after hours without waking up the owner.”

For a small owner, the win is not another dashboard. It is a booking path that answers the late-night unit question, collects the reservation, and leaves the manager with a clear record in the morning.
Small owner scenario headshot
Small owner scenarioRV and self-storage lot · Single-location operator
SiteLink operator1 location · owner-operated
Visual unit selection

“The map turns awkward inventory into something customers can understand.”

For a growing team, maps make the facility easier to sell without another phone explanation. Customers see the building, the row, or the space, and managers get fewer mystery holds to clean up later.
Growth manager scenario headshot
Growth manager scenarioMulti-location storage group · Growing operator
Facility maps3+ locations · growth phase
Contract record in one place

“The signed lease is attached to the booking when the dispute shows up.”

For managers and portfolio teams, the value is operational memory. When someone asks what was signed, paid, or sent, the answer should live on the reservation instead of in a folder, inbox, or separate signing tool.
Portfolio team scenario headshot
Portfolio team scenarioRegional storage portfolio · Portfolio team
Contracts and paymentsMultiple locations · manager-led
Build the booking path

Give tenants the flow your team wishes they had.

Bring websites, maps, contracts, payments, communications, and integrations into one booking path that works for small facilities and growing portfolios.

Start your account
Maps and mediaPayments optionalContracts when enabled