Direct Merchant Payments for Tours: Whose Account Does the Money Land In?
A $3,000 private charter should not sit in someone else’s account while a booking platform decides when to release it. Here is how direct merchant payments work, what percentage fees really cost, and the questions that expose a platform holding your revenue.
Fuel is due Friday. Payroll is due Friday. The deposit on Saturday’s private charter cleared eleven days ago and is still sitting somewhere that is not your bank.
That is the whole argument for direct merchant payments for tours, and it has nothing to do with software preferences. It is about where the money physically goes when a guest hits Book Now, and who gets to decide when you touch it.
For charter captains, party boat operators, dive shops, and tour companies, payment processing is not a checkout feature. It is cash flow, customer service, dispute handling, and how much control you keep over revenue your crew already worked for. Get the structure wrong and every weather cancellation turns into a finance problem on top of an operations problem.
First question: whose merchant account is it?
What Direct Merchant Payments for Tours Actually Means
With direct merchant payments, your business holds its own merchant account or processor relationship. A guest books online, the card is processed for your company, and the funds deposit to your bank on your processor’s schedule. The booking system still handles the reservation, availability, confirmations, passenger details, and reporting. It just never becomes the party collecting and holding your revenue.
The alternative is a marketplace-style or platform-controlled model. There, the software provider processes the guest’s card under its own merchant account, nets out its fees, and remits the rest to you later. Some operators are fine with that, especially if they want one company handling everything. But it puts a layer between a completed booking and money in your account, and that layer has its own interests.
Direct to you
- Step 1Guest pays your business
- Step 2Your processor settles to your bank
- Step 3You refund from your own account
- Step 4Statements, disputes, and 1099-K are all in your name
Through the platform
- Step 1Guest pays the software company
- Step 2Platform holds the funds, nets its fee
- Step 3Platform decides the payout date
- Step 4Refunds and disputes route through their queue
Direct processing gives you a cleaner financial structure: deposits, processor statements, refunds, and chargebacks all tied to your business, in your name, on your terms. Your booking platform should support that without asking you to hand over the transaction. That is exactly how billing and payments are built here.
Why Cash Flow Matters More on the Water
A restaurant runs the same menu every week. Charter and tour businesses do not get that kind of predictability. Weather cancels a trip. A captain moves a departure time. A private group books five months out while a walk-up party boat fills seats the morning of.
That reality is why access to your own revenue matters so much. You may need to refund a guest today, cover a dock bill, buy bait, pay a deckhand in cash, or move twenty passengers to a new date. When the money is delayed or gated by a third party, a routine operational change becomes a financial headache.
Nobody has ever had a good Saturday that started with “I have to email support to refund my own customer.”
Be honest about what direct processing does not do. It does not eliminate processor payout schedules, underwriting, rolling reserve requirements, or card network rules. No legitimate provider can promise that, and anyone who does is selling something. What it removes is the extra question: whether a booking platform is sitting on your money, skimming its fee off the top before you see it, or adding one more approval step on the morning you need action fast.
For a high-ticket private charter, a scuba trip, or a sunset cruise, that gap is not small. A handful of bookings can be thousands of dollars. You should be able to say out loud who processes your transactions, when deposits land, and what happens when a guest disputes a charge. That clarity is the foundation of real revenue and cost control.
Weather Cancellations Are a Payments Problem Too
Weather is part of the business. Guests understand that when it is explained clearly. What they do not accept is silence, or an answer that starts with “we have to wait to hear back.” Your payment setup should help you in that hour, not slow you down.
With a direct merchant relationship, your team issues refunds from the payment account connected to your business. Transaction history, reservation details, cancellation notes, and customer messages all sit alongside the decision. That gives you a straight path whether the trip gets canceled, rescheduled, partially refunded, or converted to a future credit.
The word doing the work above is your. Your exact options still depend on your processor, your booking system, and the terms you set for deposits and cancellations. A nonrefundable deposit is reasonable for an offshore trip with a crew reserved for the day. Flexible rebooking may suit a whale watching operation dealing with wind. Software should let you apply your policy consistently, not force every business through one refund workflow.
Clear policies still do the heavy lifting. Put the cancellation window, weather policy, no-show terms, and rescheduling options where guests see them before they pay. Then let automated customer communication deliver the news in one pass:
Keep Your Booking Revenue Separate From Software Fees
Percentage-based booking fees get expensive quietly. A platform taking a cut of every reservation earns more whenever you sell a premium charter, add passengers, or raise prices to cover rising fuel and insurance. You did the work; the fee went up anyway.
That model is easy to overlook because the money never hits your account in the first place. It deserves the same scrutiny you give fuel, marina fees, insurance, and card processing. So run it on one real trip: a $2,500 private charter for six.
| Model | One charter $2,500, 6 passengers | 80 charters a season |
|---|---|---|
| Platform commission at 6% of the booking | $150 | $12,000 |
| GoFish.Rocks, flat $1.50 per passenger | $9 | $720 |
| You keep the difference | $141 | $11,280 |
Software fees only; card processing is separate on every platform, so it cancels out of the comparison. Published rates as of July 2026: Peek Pro up to 8% and FareHarbor up to 6% per Bokun’s pricing guides, Origin at 5%, and Rezdy at 3% plus a monthly plan. Your own number is on your last statement.
Same booking page. Same confirmation email. Same server load. $150 or $9. Raise your charter to $3,500 and the percentage fee climbs to $210, while the flat fee stays at $9, because six people still booked six seats.
A software company should not get a raise every time you do.
Direct merchant payments make that cost picture legible. You pay your card processor for card processing, and you pay your booking software its stated price. Two separate decisions you can evaluate honestly, instead of one bundled arrangement you have to reverse-engineer. That is the entire point of transparent pricing, and it is why our fee structure is a flat $1.50 per passenger per trip instead of a percentage of everything you sell.
Chargebacks Still Require Good Operations
Being the direct merchant means chargebacks are yours to answer. That is not a downside to bury in a footnote. It is the trade-off for controlling your own payment relationship, and it is a fair one, because the operators who lose disputes usually lose them on documentation, not on merit.
A strong chargeback response starts long before the dispute arrives. When a guest claims they never authorized a charge, or that the trip never ran, what you can produce in the next few days decides it.
Keep this
- Booking confirmation with timestamp and IP
- Signed waiver and passenger manifest
- Payment receipt and the descriptor the guest saw
- Proof they accepted the cancellation policy
- Trip communications and any reschedule offers
- Evidence the trip actually sailed
Not this
- “I’m pretty sure we texted them”
- A paper manifest that lives in the wheelhouse
- Three inboxes and a deckhand’s personal phone
- A policy that exists but was never shown at checkout
- A refund you promised verbally and never issued
For no-show disputes, accurate manifests and documented reminders carry the day. For weather disputes, keep the cancellation notice, the reschedule offer, and the guest’s response. For service complaints, a quick phone call and a practical fix often prevents the dispute entirely, which is cheaper than winning one.
Your booking system should make those records easy to pull. If staff have to reconstruct one reservation from text messages, a paper notebook, a separate calendar, and two inboxes, the business is exposed. Payments, manifests, message history, and reservation changes belong in one operational view.
Questions to Ask Before Choosing a Payment Setup
Do not accept “integrated payments” as an answer. It is a phrase, not a structure. Ask what it means in plain English, and get it in writing before you sign anything.
Ask Before You Sign
Seven questions. Any fuzzy answer is itself the answer.
- Whose merchant account processes the card? Mine, or yours?
- Who controls payout timing, and what is the actual settlement schedule in writing?
- Can I keep or choose my own processor, or am I locked into yours?
- How do refunds work? Can my staff issue one at 6 AM without asking anyone’s permission?
- Are software fees separate from processing fees, and do you take a percentage of bookings?
- What happens if I leave? Can I export customers, booking history, and financial reporting? Contract length, cancellation fee?
- Who answers the phone Saturday at 6 AM when a guest says they were charged twice?
That second-to-last one is the quiet tell. How a company answers “can I leave?” before you join tells you what they will be like if you ever try. If the answer involves a long contract and a data export you have to request in writing, you have learned something. Worth reading up on fair credit card processing before you sign on that side too.
Support is the other practical issue. When a guest says they were charged twice at 7:00 AM on a busy Saturday, you need a person who understands charter bookings, not a ticket queue that replies Tuesday. Payment tools are only useful when your team can get help during real operating hours, which is why live US-based support is not a bonus feature on the water. It is the feature.
What This Looks Like on GoFish.Rocks
Since you are reading this on our site, here is our cards-on-the-table version.
Payments go straight to your own merchant account. We never hold your revenue, never net our fee out of your deposits, and never decide when you get paid, because it was never in our hands to begin with. Pricing is a flat $1.50 per passenger per trip, no subscription, no percentage, no setup fee, and $0 when weather kills the trip. Migration is hands-on and free, and if you ever want out, your data leaves with you.
We built it so we are on your side of the rail: we only make money when you make money, and we never touch the money in between.
The Right Setup Is the One You Can Explain
A good payment structure should be simple enough to explain to your bookkeeper, your deckhands, and a customer standing on the dock. Guests pay your business. Your processor deposits to your business. Your booking software keeps the reservation organized. Your policies decide how cancellations and refunds work.
If explaining it takes a diagram and a phrase like “well, technically they collect it first,” that is not a payment structure. That is an arrangement you inherited from a sales demo.
Clarity buys you room to focus on the work that actually builds the business: running safe trips, filling seats, taking care of guests, and protecting the margin on every departure. When the money trail is direct, the business stays in your hands.
Direct Merchant Payments FAQ
What are direct merchant payments for tours?
Direct merchant payments mean your tour or charter business holds its own merchant account, so guest payments are processed for your company and deposited to your bank on your processor’s schedule. The booking software manages reservations, manifests, and communication, but never collects or holds the money.
How is that different from a booking platform that processes payments?
In a platform-controlled model, the software company processes the card under its own merchant account, nets out its fees, and remits the balance to you later on a schedule it sets. With direct merchant payments, there is no middle step: the funds settle to your account, and refunds, statements, and disputes are all in your business’s name.
Do direct merchant payments mean I get paid instantly?
No, and be skeptical of anyone who says otherwise. Your processor’s payout schedule, underwriting, and any rolling reserve still apply. What direct processing removes is a booking platform deciding when to release your money on top of that.
Who handles chargebacks with direct merchant payments?
You do, as the merchant of record. That is the trade-off for controlling your own payment relationship, and it is manageable with organized records: booking confirmations, signed waivers, manifests, payment receipts, proof the cancellation policy was accepted, and trip communications. Most disputes are lost on missing documentation rather than on the facts.
Are booking software fees the same as credit card processing fees?
They should not be. Card processing is what your processor charges to run the transaction. Software fees are what the booking platform charges for the software. When they are bundled into one percentage, it is hard to tell what you are paying for either. A flat per-passenger software fee keeps the two separate and comparable.
Your money, your account
Payments settle directly to your merchant account, never ours. Flat $1.50 per passenger, no percentage, no contract, and $0 in fees when weather cancels the trip.
See How It Works →




