Loading blog content, please wait...
By ActivityPay
Authorization Holds Are Weirder for Tour Operators Than Anyone Explains A guest books a kayak tour three weeks out. The authorization goes through. Everyth...
A guest books a kayak tour three weeks out. The authorization goes through. Everything looks fine. Then the day before their trip, they try to add two more people to their booking, and their card declines—even though they have plenty of available credit.
What happened? The original authorization hold is still sitting there, tying up funds that technically haven't been captured yet. And now there's not enough room for the second charge.
This scenario plays out constantly in experience-based businesses, and it catches operators off guard because authorization holds weren't designed with advance bookings in mind.
Most retail transactions happen in a single moment. Customer swipes, merchant captures, funds move. The authorization and capture are essentially simultaneous.
Experience businesses don't work that way. A guest might book a sunset sailing trip six weeks before the actual departure. That's six weeks where the authorization is just... sitting there.
Here's what most operators don't realize: authorization holds have expiration windows. Depending on the card network and card type, that window might be 7 days, 10 days, or 30 days. After that, the authorization drops off—but the booking is still on your calendar.
When you finally try to capture the funds on departure day, you're essentially running a new transaction. If the card has expired, the account is closed, or the available credit has changed, that capture fails. You've got a guest on your dock and no payment.
Restaurants don't worry about this. Neither do most retail stores. Their authorization-to-capture window is measured in minutes, not weeks.
But tours, activities, and attractions operate on fundamentally different timelines:
Long booking windows. Many guests book premium experiences months in advance. A private charter, a multi-day adventure, a holiday whale watching trip—these often get booked 60 to 90 days out.
Deposit structures. Operators commonly collect a deposit at booking with the balance due closer to the trip. Each of those is a separate authorization event with its own expiration timeline.
Add-ons and upgrades. Guests frequently modify bookings—adding people, upgrading packages, purchasing extras. Each change can trigger new authorization complexity.
Weather and cancellation patterns. Unlike a hotel room that exists regardless of weather, outdoor experiences get rescheduled or canceled based on conditions. That creates rebooking scenarios where the original authorization is long gone.
The payment infrastructure most businesses rely on was built for immediate transactions. Experience businesses are trying to run advance reservations through systems designed for coffee shops.
When an authorization hold drops off before capture, a few things can happen:
The capture still works. If the cardholder's available credit hasn't changed and the account is in good standing, many processors will complete the capture anyway. This is called a "forced capture" or capturing without a valid authorization. It often works, but it carries higher risk—and higher liability if the cardholder disputes it later.
The capture fails. The funds aren't there anymore. Maybe the guest maxed out their card in the weeks since booking. Maybe the card was reported lost and replaced. You now need to contact the guest, collect new payment information, and hope they're responsive before their trip.
The capture succeeds but gets disputed. This is the sneaky one. The charge goes through, but because the original authorization expired, the cardholder might not recognize the charge weeks later. They call their bank, claim they didn't authorize it, and you're fighting a chargeback with weaker documentation.
None of these outcomes are catastrophic on their own. But when you're processing hundreds of bookings with varying lead times, these edge cases add up.
Operators running mostly same-day or next-day bookings rarely encounter authorization expiration issues. The window between booking and fulfillment is short enough that holds stay valid.
But operators with longer lead times—destination tours, seasonal experiences, premium multi-day trips—face this constantly. The higher the average booking value and the longer the typical lead time, the more authorization timing matters.
This is one reason why many experienced operators structure payments differently based on lead time:
That final balance collection isn't just about cash flow management. It's about ensuring you have a valid, recent authorization before the guest shows up.
Speaking of deposits—this is where things get particularly awkward for tour operators.
Many operators collect 25% or 50% at booking, then collect the remainder closer to the trip. Seems straightforward. But each of those is a separate authorization event.
The deposit authorization gets captured right away. No problem there. But the balance due authorization—collected weeks later—is the one guests sometimes miss. Their payment reminder email goes to spam. They're traveling and not checking email. They thought the deposit was the full amount.
Now you're chasing payment from guests who might already be en route to your location. Or you're declining to provide the experience they've been planning for months because their balance payment failed.
This isn't a payment processing problem. It's a workflow design problem. The payment infrastructure is doing exactly what it's supposed to do. The challenge is building booking flows that account for how authorization holds actually work.
Operators who handle this well tend to do a few things consistently:
They automate balance reminders aggressively—starting earlier than feels necessary, with multiple touchpoints across email and SMS.
They collect balance payments far enough in advance (often 7-14 days before the trip) that there's time to resolve issues before the guest arrives.
They capture funds promptly rather than letting authorizations age. If you're collecting full payment at booking, capture it immediately rather than waiting.
They train staff to recognize authorization-related declines versus other payment failures. The troubleshooting is different.
The goal isn't to fight the authorization system. It's to design booking flows that work with how card networks actually function—even when that's different from how operators assume they work.