How We Approach Collect Rent Online at Flux

How we think about collect rent online

When a property manager asks us how to collect rent online, we do not start with a feature list. We start with two facts that decide almost everything: rent recurs, and rent is usually a large, predictable amount. Hold those two facts in mind and the right choices tend to make themselves.

This is how we approach the problem at Flux, written as principles you can apply rather than a sales pitch. There is no named client here and no invented result, just the reasoning we use when someone wants to move rent collection off paper.

Start with the payment method the tenant will actually use

A rent portal that only accepts cards does two unhelpful things at once. It pushes your fee costs up on every payment, and it annoys the many tenants who would rather pay straight from a bank account. So we lead with ACH bank transfer for rent, because the method should fit the amount, and a monthly four-figure payment is exactly where avoiding card network costs matters most.

We keep cards available, because some tenants want them and some situations call for them, like a catch-up payment where speed and convenience win. The point is not to ban cards; it is to make the cheaper rail the default and the card the exception, rather than the other way around.

What does it cost to collect rent online?

Cost is the first question almost every manager asks, and the honest answer is that it depends on the mix of methods your tenants use. On Flux the flat rate is 2.9% plus 30 cents per transaction, with volume-based pricing available as a portfolio grows. There are no monthly fees, no minimums, and no contracts, so a manager with a handful of units is not paying to keep the option open through a vacancy.

Where local surcharging rules allow, the fee can be passed to the tenant at checkout. We mention that option because managers ask for it, and we always add the same caveat: check your state rules and your lease terms first, because surcharging is not permitted everywhere.

Timing: when the money actually lands

We set expectations on timing early, because a tenant paying on the first does not put cash in your account on the first. ACH settles in one to three business days and cards in one to two. If any part of the portfolio prefers stablecoins, those funds arrive at the merchant wallet instantly, but that is the rare case.

We would rather a manager know the real windows than promise same-day availability and then field frustrated calls when the money is still in transit. Planning distributions and vendor payments around the actual settlement window, not the payment date, is what keeps the operating account honest.

Keeping tenant card data out of your systems

Property managers already hold a great deal of sensitive information, and we do not want tenant card numbers added to that pile. Our approach captures card data inside origin-isolated iframes on payments.fluxpayments.com, so it never touches the manager's servers or domain.

Flux is SAQ-D Level 2 PCI DSS certified, and the practical upshot is simple: the less tenant card data lives on your systems, the smaller your risk and the less you have to defend. You collect the rent and keep the record; you do not inherit the card numbers.

Recurring rent without re-entry

Rent repeats, so the payment plumbing should repeat too, without a person re-entering anything. Our approach uses tokenization, so a tenant's payment method can be stored securely and charged on schedule without asking for the details again each month. It uses webhooks, so your own system learns the moment a payment succeeds or fails and can act on it.

For managers on QuickBooks, the integration syncs each rent payment to the books, so the ledger largely keeps itself and the month-end close becomes a review rather than a data-entry marathon. That combination, recurring charges plus real-time notifications plus automatic bookkeeping, is what turns rent collection from a monthly chase into a background process.