You compare booking software on features, price, and how the calendar looks. Fair enough. But the part of the system that touches every dollar your park earns — payment processing — usually gets a single line on the pricing page, and most owners sign up without asking how it works.
That's a mistake. Two parks can run the same software, charge the same rates, and have very different months, purely because of how the money moves. Here's what actually happens between a guest typing in a card number and cash landing in your bank account — and where the model can quietly work against you.
The path a payment takes
When a guest books a site online, the money doesn't go straight from their card to your checking account. It passes through a payment processor, and — depending on the software you use — sometimes through the software company itself before it reaches you.
That middle step is where the important differences live. Three questions tell you almost everything:
- Who holds the money between the booking and the payout?
- How long do they hold it?
- What does each transaction cost, and who pays it — you or the guest?
Who actually holds your money
There are two basic models in campground software.
In the first, the platform collects guest payments into its account and remits your share later — weekly, twice a month, or when your balance crosses a threshold. Your money sits with the platform in the meantime. During peak season, that can mean thousands of dollars of your July revenue living in someone else's account while your own bills come due.
In the second model, payments settle into a payment account that belongs to you — the software connects to it but never holds your funds. This is how Bunkpost works: payments run on Stripe Connect, the account is yours, and payouts hit your bank daily. If you ever left, the payment account and its history would still be yours.
Neither model is fraudulent or exotic. But the first one gives the platform float and leverage; the second gives you both. Ask which one you're signing up for before you sign.
What processing actually costs
Card processing is not free, and no honest vendor will tell you it is. The standard published online card rate in the US is around 2.9% plus 30 cents per transaction. For a park doing, say, $150,000 a year in card volume, that's roughly $4,500 — a real cost, in the same category as insurance or electricity.
What matters is whether you're paying only that, or that plus a markup. Some platforms add their own percentage on top of the processor's rate. Others advertise "free software" and recover the cost through per-booking guest fees — which is really a tax on your guests wearing your park's name. We've written before about why those booking fees exist and who actually pays them, and about what campground software really costs once you count everything. The short version: the money comes from somewhere. A flat subscription plus straight processing costs is easier to reason about than a model where the vendor earns more every time your rates go up.
Bunkpost charges a flat monthly price and adds no guest fees and no percentage of your bookings. You pay standard Stripe processing on cards, and that's the whole payments story.
Payout timing matters more in a seasonal business
A restaurant that gets paid out weekly instead of daily is mildly annoyed. A campground is a different animal: many parks earn most of their revenue in a four- or five-month window, and that same window is when expenses peak — seasonal staff, propane, repairs, the septic guy.
Daily payouts mean Saturday's check-ins are in your account early the following week, every week, all season. A twice-monthly remittance means you're effectively lending the platform your busy-season revenue for up to two weeks at a time, then managing lumpy deposits against smooth expenses. Neither changes your annual total. One of them changes how often you check your balance nervously in July.
Chargebacks: the trade-off nobody puts in the brochure
Here's the honest downside of taking cards online: guests can dispute charges. A chargeback happens when a cardholder tells their bank a charge was fraudulent or unfair, and the bank claws it back while the dispute is reviewed. It exists to protect consumers, and mostly it does — but it can also be misused by a guest who ignored your cancellation policy and wants their money back anyway.
You cannot eliminate chargebacks. You can make them rare and winnable:
- Publish a clear cancellation policy and make guests agree to it at booking. A policy the guest saw and accepted is your best evidence in a dispute. If yours is vague, start with writing a cancellation policy guests actually accept.
- Use a recognizable statement descriptor. A surprising number of disputes are just guests not recognizing the charge on their statement.
- Confirm everything in writing. Booking confirmations, receipts, and refund records are the paper trail that wins disputes.
- Refund fast when a refund is owed. A refund costs you the processing fee. A chargeback costs the fee, a dispute fee, and your time.
Any software that promises you'll "never deal with chargebacks" is either holding your money so it can absorb them (see the float problem above) or pricing that risk into what you pay. There's no free lunch here — just clearer and murkier versions of the same trade.
Questions to ask any booking software vendor
Before you commit to a platform — including ours — get plain answers to these:
- Whose name is on the account where guest payments settle?
- How often do payouts reach my bank, and is there a fee to get them faster?
- What is the total per-transaction cost — processor rate plus any platform markup?
- Are there per-booking fees charged to my guests?
- If I cancel my subscription, what happens to my payment history and upcoming payouts?
A good vendor answers all five in a sentence each. If the answers require a diagram, that's an answer too. Ours are short: your Stripe account, daily, standard Stripe rates with no markup, never, and you keep everything — the features page and FAQ cover the details.
The takeaway
Booking software isn't just a calendar — it's the pipe your revenue flows through. Judge the pipe: who holds the money, how fast it reaches you, and what each dollar costs on the way. A park that gets those three answers right keeps more of its own money and sleeps better in peak season.
If you want to see what the direct model looks like in practice, how it works takes about two minutes to read, and the first 30 days are free — long enough to watch a real payout hit your own bank account before you pay us anything.