Understanding Payment Processing Fees for Experience Operators

Most experience businesses know payment fees matter. If you are taking bookings online, selling memberships, running courses, issuing refunds or taking payments on-site, the cost of processing payments has a direct impact on your margin.

But the number you are quoted by a payment provider is rarely the full story.

A rate might sound simple at first. “Interchange plus 0.3%”, “low-cost payment processing”, “transparent pricing”, or “save on every transaction”. On paper, it all looks fairly straightforward. A customer pays, a small percentage is taken, and the rest lands in your account.

In reality, payment processing is usually more complicated than that. There are multiple parties involved in every card transaction, and several different types of fees can sit behind the headline rate. Some are obvious. Others only become clear when you start looking through statements, payout reports and chargeback notices.

For activity centres, attractions, sailing schools, watersports operators, tour companies and family entertainment venues, this matters more than it might for a standard ecommerce business. Payments are not just a checkout step. They are tied into bookings, deposits, memberships, waivers, refunds, gift cards, balance payments, customer communication and accounting.

That means the real cost of payment processing is not just the percentage charged on each transaction. It is the total cost of taking the payment, managing it, reconciling it, and dealing with everything that happens afterwards.

The headline rate is only part of the picture

A lot of payment pricing is built around headline numbers. These are useful, but they can also be misleading if you do not know what is included.

For example, interchange plus pricing is often presented as the more transparent option. In theory, it can be. You pay the underlying interchange fee, plus a markup from the processor. That sounds simple.

The question is what else sits around it.

A typical payment may include:

• interchange fees

• scheme fees

• processor markup

• gateway fees

• 3D Secure or authentication fees

• cross-border fees

• currency conversion fees

• chargeback fees

• refund-related costs

• terminal or hardware costs

• monthly account or reporting fees

None of these fees are necessarily unreasonable. Payments infrastructure is complex, and there is a real cost to moving money securely. The issue is that operators are often shown one clean number, when the real cost is made up of several moving parts.

So when a provider says “we only charge 0.3%”, the important question is: 0.3% on top of what?

If that 0.3% is only the processor markup, then the total cost could be much higher once interchange, scheme fees and other charges are added. The quoted rate may be technically accurate, but still not very useful for understanding what the business will actually pay.

Why experience businesses feel this more than most

Experience businesses are operationally messy by nature. That is not a criticism; it is just the reality of the sector.

A customer journey might start with an online booking, then involve a deposit, a waiver, a balance payment, a date change, an add-on, a gift card, a weather-related cancellation or a partial refund. For a family booking, there may be multiple participants. For a course, there may be staged payments. For a membership, there may be recurring billing, access control and eligibility rules.

That makes payments part of the operation, not just part of finance.

If your payment system is disconnected from the rest of the business, every edge case creates admin. Staff need to check whether someone has paid. Customers need to be chased for balances. Refunds need to be matched to bookings. Bank transfers need to be manually reconciled. Reports need to be exported and cleaned up before they make sense.

This is where the hidden cost appears. It does not always show up on a payment statement, but it shows up in staff time, customer confusion and messy reporting.

A lower card rate can look attractive, but if it creates extra work elsewhere, it may not be cheaper at all.

The problem with comparing payment providers on rate alone

It is tempting to compare payment providers in a simple way.

Provider A charges 1.5%. Provider B appears to charge 1.2%. Provider B looks cheaper.

Sometimes that is true. But not always.

If the cheaper provider creates more manual work, the saving can disappear quickly. A small reduction in transaction fees can be wiped out by a few extra hours of admin each week.

For example, saving 0.3% on £500,000 of card payments is £1,500 a year. That is worth having. But if the setup creates five extra hours of admin per week, you are looking at 260 hours a year. Even at a conservative cost per hour, the “saving” is no longer much of a saving.

And that is before considering the customer experience. If payments are clunky, balances are missed, refunds are slow or staff cannot quickly see what has happened, the business pays for that in other ways.

The cheapest setup is not always the one with the lowest advertised percentage. It is the one that gives you the best total outcome: lower admin, cleaner reporting, fewer errors and a better customer journey.

Bank transfers are not always free

One common response to card fees is to push customers towards bank transfers. On the surface, this feels sensible. There is no visible card fee, the money arrives in the bank account, and the business avoids paying a processor.

But bank transfers still have a cost. It is just less visible.

Someone has to check the bank account. Someone has to match the payment to the right booking. Someone has to update the customer record. Someone has to chase anyone who forgets to pay. Someone has to deal with incorrect references, partial payments and timing issues.

For a small number of large bookings, that might be manageable. For a busy operator with lots of customers, it quickly becomes painful.

The issue is not that bank transfers are always bad. They have their place. The issue is assuming they are free because there is no obvious transaction fee. In practice, the cost is often moved from the payment provider to the admin team.

And admin time is still a cost.

Refunds, credits and cancellations change the equation

Refunds are another area where the headline payment rate does not tell the full story.

Experience businesses often deal with cancellations, date changes and weather-related disruption. Customers may need a full refund, a partial refund, a credit, or a transfer to another session. In some cases, the business may want to retain part of the payment while refunding the rest.

The quality of the payment workflow matters here.

A good system should make it clear what was paid, what was refunded, what remains outstanding and how the booking has changed. A poor setup leaves staff trying to piece it together manually.

Refunds also have cost implications. Some providers do not return the original processing fees. Some charge additional fees. Chargebacks can create further costs, even when the operator has done nothing wrong.

Again, this is not always obvious from the quoted rate. But it has a real impact on how easy the business is to run.

Reporting is where the pain usually shows up

Most operators do not feel the pain of payment complexity at the moment of payment. They feel it later, when they are trying to understand the numbers.

At the end of a day, week or month, a business needs to know:

• how much money was taken

• which bookings were paid online

• which payments were taken in person

• what was refunded

• what remains outstanding

• which payments relate to which payouts

• what fees were charged

• what should be recognised as revenue

• what needs to be reconciled in Xero or the accounts

If payments are separated from bookings, this becomes harder than it should be. You end up with one report from the payment processor, another from the booking system, card terminal data somewhere else, and bank transfers sitting in the bank account with inconsistent references.

That is when teams start relying on spreadsheets and manual workarounds. It might work for a while, but it does not scale well.

The more locations, activities, staff and customers you have, the more important it becomes that payments and operations sit together.

What operators should actually ask

When comparing payment options, the card fee still matters. Of course it does. But it should not be the only question.

A better set of questions would be:

• What is the total blended cost we are likely to pay?

• Does the quoted rate include interchange, scheme fees and processor markup?

• Are there extra fees for 3D Secure, chargebacks, refunds or cross-border cards?

• Are card terminal or hardware costs included?

• Can customers pay deposits and balances automatically?

• Can staff see payment status directly against the booking?

• Can refunds, credits and transfers be managed cleanly?

• Can online and in-person payments be reported together?

• Can payouts be reconciled against bookings?

• Does it connect properly with our accounting workflow?

• How much admin will this create or remove?

That final question is the one I think gets overlooked most often.

Payment processing is not just a finance decision. For experience businesses, it is an operational decision.

Payments should be part of the operating system

At Sailia, we see payments as one part of a much bigger system.

A payment should not sit off to the side of the business. It should connect to the booking, the customer, the activity, the instructor, the membership, the waiver, the refund, the gift card, the payout and the accounts.

That is where the value comes from.

Most providers can take a payment. The harder and more important question is what happens after the payment has been taken.

Does the booking update automatically? Does the customer receive the right confirmation? Can staff instantly see what has been paid? Are balance reminders sent without manual chasing? Are refunds linked to the original transaction? Can finance see a clean breakdown? Can managers understand performance across multiple activities or locations?

When payments are connected properly, the whole business runs more cleanly. When they are disconnected, the cost shows up everywhere else.

The real cost is the total cost

The point is not that one pricing model is always better than another. Interchange plus pricing can be good. Flat-rate pricing can be good. Bank transfers can be useful. Card payments can be expensive in some cases and extremely efficient in others.

The point is that operators need to look beyond the headline number.

The real cost of payment processing includes the visible fees and the hidden operational cost around them. It includes the time spent chasing balances, reconciling payouts, handling refunds, fixing errors and explaining payment issues to customers.

For experience businesses, that matters because the payment is rarely the end of the journey. It is part of a much wider workflow involving people, capacity, staff, equipment, weather, memberships, gift cards, refunds and repeat customers.

So yes, look closely at the card fee. But also look at the system around it.

A payment setup that saves a fraction of a percent but creates hours of admin is not cheap. It is just hiding the cost somewhere else.

The best payment setup is the one that helps the business run properly: clear for customers, simple for staff, reliable for finance and connected to the rest of the operation.