October 12, 2026
I grew up working boats in St. Maarten, and I've lost count of the operators who've told me the same story. They finally go to set up card payments on their website, and the processor comes back with a line that stings: you're a "high-risk" merchant. Reserves. Higher fees. A pile of paperwork. It feels personal, like someone decided your business is shady before you've taken a single booking.
It isn't personal. "High-risk" is a label the card networks and payment processors hang on an entire industry, and tour and charter operators sit squarely inside it. The good news is that once you understand why the label gets applied, you can actually do something about it — and most of the fixes are things you already have the tools to do.
Strip away the fintech language and a high-risk merchant account is simple: it's a card-processing account that comes with stricter terms because the processor expects more chargebacks or fraud than it would from an average business. That's the whole idea. A "chargeback" is when a customer disputes a charge with their bank and the money gets pulled back out of your account. When a processor believes a certain type of business will rack up more of those than usual, it hedges — tighter approval, held funds, higher fees.
The important part, especially if you're the kind of owner who takes this stuff to heart: it's a category label, not a verdict on your character or how you run your boat. You can run a spotless operation and still get coded high-risk on day one.
When you apply for processing, you get assigned a Merchant Category Code — a four-digit number that tells the card networks what kind of business you are. Tour and charter operators almost always land in MCC 4722. According to PayCompass, MCC 4722 covers travel agencies and tour operators and specifically includes "charters and excursions" — the businesses selling chartered trips, private tours, and day excursions — as long as you arrange the experience rather than, say, being the airline yourself.
Here's why that code reads as risky. Travel has a structural problem that has nothing to do with you personally: the guest pays now and gets the service later. The travel guide at Jim.com puts it plainly — MCC 4722 is treated as high-risk largely because of the industry's high chargeback likelihood, driven by trip cancellations and the long gap between payment and service delivery. Stack on the rest of how tours actually work and you can see the processor's logic. You depend on third parties to deliver — captains, guides, hotels, the weather. Revenue is seasonal and uneven. Individual transactions can be large. PayCompass lists exactly these — dependency on third-party cruise lines, guides, and hotels, inconsistent seasonal revenue, and high-value transactions — as the operational risks that make processors ask for more underwriting and sometimes a reserve.
One thing worth holding onto: the code alone doesn't seal your fate. As the team at Compaytence puts it, your MCC sets the tone, but your actual business model, geography, financial condition, fulfillment practices, and chargeback history all factor into how a processor treats you. The code opens the conversation; your track record finishes it.
If the "why us?" feeling is strong, the numbers back it up. Travel and hospitality carries the highest average chargeback value of any industry in 2Accept's 2026 data — about $120 per dispute globally, against a $110 average across all US merchants. Once you add the operational and processing costs of fighting one, the total cost of a single travel dispute can run as high as $450, versus around $315 in general e-commerce. Disputes are simply more expensive in our world.
They're also more frequent relative to the line in the sand. A "normal" chargeback rate sits below 1%, with 0.5% to 0.9% considered standard. 2Accept pegs the blended average across all industries at 0.26% of transactions in the third quarter of 2025, up from 0.21% a year earlier — while travel routinely runs close to or above the 0.9% to 1.5% band that draws network scrutiny. So an operator can feel like they're doing fine and still be sitting near the threshold that trips alarms.
The quiet culprit is "friendly fraud" — when a cardholder disputes a charge they actually made. PayCompass estimates it drives roughly 70% to 75% of all chargebacks. Think about how a tour booking works: a guest pays in March for a July catamaran trip. By the time the statement shows up, the charge is four months old, the trip name looks unfamiliar, and it's easier to call the bank than to call you. That's a friendly-fraud chargeback waiting to happen, and it's baked into the shape of our business.
"High-risk" only turns into real money when you cross the card networks' monitoring thresholds, so it's worth knowing the actual numbers you're managing toward — not a vague "be careful."
On the Visa side, the program to know is VAMP, the Visa Acquirer Monitoring Program. The Merchant Risk Council reports that VAMP replaced Visa's older dispute- and fraud-monitoring programs in 2025, and it now rolls fraud reports and chargebacks into a single ratio measured against your card-not-present transactions. The threshold tightened on April 1, 2026: the "excessive" line dropped from 2.2% to 1.5%. Monitoring kicks in once you hit 1,500 combined disputes and fraud reports in a month, and once you're enrolled, flagged transactions carry a fee of roughly $8 each.
Mastercard runs its own version, the Excessive Chargeback Program. Chargeflow lays out the tiers: you become an "Excessive Chargeback Merchant" at 100 to 299 chargebacks in a month combined with a 1.5% to 2.99% ratio, and a "High Excessive" merchant at 300-plus chargebacks and a 3% or higher ratio. You have to cross both the count and the ratio to be flagged — and you have to stay under both for three straight months to climb back out.
The fines are the part that stings, and they escalate the longer you're stuck. PayKings outlines the Mastercard schedule: nothing in month one, then $1,000 a month in months two and three, $5,000 a month in months four through six, $25,000 a month in months seven through eleven, and up to $100,000 a month by month nineteen and beyond — roughly double those figures in the "High Excessive" tier. Your acquiring bank gets billed and passes it straight to you. The takeaway isn't to panic; it's that these are concrete lines, and everything in the fix-it section below is about keeping comfortable distance from them.
Most operators never see a fine, because most never hit those thresholds. What you're far more likely to live with are the account terms that come with the high-risk label.
The big one is a rolling reserve — a slice of your sales the processor holds back temporarily as a cushion against future chargebacks. SecureGlobalPay describes the typical shape: 5% to 15% of each transaction held for 90 to 180 days, then released on a rolling schedule. The key word is held, not charged. A reserve is your money in a holding pen, not a fee you've lost.
Alongside that, expect a higher MDR — the "merchant discount rate," which is just the percentage the processor keeps from each sale — than a standard online store would pay. PayAtlas notes that under MCC 4722 you should also plan for settlement cycles that can stretch up to about 10 days (the gap between a card being charged and the money landing in your account) and more detailed underwriting up front: a real business plan and proof you know the industry. None of this is a ban. They're terms, and terms can be negotiated down as you prove yourself.
When operators hit this wall, the instinct is to go shopping for a processor that advertises itself as "high-risk friendly" and will approve you fast. I get it. But approval isn't the same as a fix. Switching processors doesn't change your MCC, and it doesn't erase your chargeback history — it just resets the underwriting clock with a new company, usually at worse rates and a bigger reserve while they get comfortable with you. You've paid more to stand in the same spot.
There's a version of this that genuinely worries me, and it's common in my corner of the world. Here in the Caribbean, most of the big processors — Stripe, PayPal — don't connect to local banks. So I'll see a sizeable tour company take card payments on the island, route the money to a bank account they've opened in the US, Canada, or Europe, and then wire it back home. I'll be honest: I don't understand how that's clean, accounting-wise or tax-wise, and it adds exactly the kind of cross-border complexity that makes an underwriter nervous rather than reassured. It's a workaround dressed up as a solution.
It's the reason we built our own processor, JB Pay, so a Caribbean operator can sign up, share some basic company details, sign an agreement, take cards right on their own website, and have the money pay out to their local bank, on their island. If you want the detail, I've written separately about how Caribbean operators handle card processing and payouts. The broader point holds everywhere, though: chasing an easy approval treats the symptom. Lowering your actual risk treats the cause.
The label is earned over time, and it comes off over time. Here's what actually moves the needle — all of it doable from the operator's seat, none of it requiring you to become a payments expert.
A deposit does two quiet, powerful things. First, it shrinks the dollar amount exposed on any single booking — if a dispute does land, it's a fight over the deposit, not the whole trip. Second, it shortens the window in which a guest can plausibly forget the charge. Remember that friendly fraud thrives on the long gap between payment and service; collecting a smaller deposit now and the balance closer to the trip keeps the charge fresh and recognizable. If you're not sure how to structure it, I've walked through setting up deposits and automated balance-due reminders step by step.
When a dispute is filed, the bank wants proof the customer knew what they were buying. The beautiful thing is that a decent booking system is already generating that proof as a byproduct of taking the booking: a timestamped record of when the guest booked, an itemized receipt, an automated confirmation email with your cancellation terms right there in it. That's precisely the documentation card networks ask for. Routine admin, it turns out, is also your defense file. I've pulled the whole approach together into a chargeback-proof playbook for your bookings if you want the full checklist.
This one is a genuine gift for operators with repeat guests, and most of us have more of them than we think. Visa Compelling Evidence 3.0, live since April 2023, lets you kill a friendly-fraud dispute before it ever becomes a chargeback. Checkout.com explains the mechanics: if the same cardholder has two earlier, undisputed transactions with you — dated between 120 and 365 days before the disputed one — and those transactions match at least two of four data points (things like the customer's account ID, IP address, shipping address, or device fingerprint, with at least one being IP or device), Visa shifts liability to the card issuer and blocks the dispute. The part that matters for your risk status: a dispute stopped this way never counts toward your VAMP or Mastercard ratio. For returning snorkelers, repeat charter clients, and multi-booking families, that history is a shield — if your system is capturing it.
Come back to that rolling reserve. SecureGlobalPay is clear that it's a refundable buffer, not a punishment — and, this is the part operators miss, a sustained history of low chargebacks and stable processing volume is exactly what gets a reserve reduced or removed. So the 90-to-180-day hold isn't forever. Once you've put together a few clean months, ask. Bring your own numbers. Processors reward a trend they can see, and the trend is something you control one booking at a time.
Print this, stick it by the register, and work it:
High-risk isn't a brand burned into your business. It's a starting position — and for tour and charter operators, it's one you can steadily, provably work your way out of. The operators who get there don't do it by finding a friendlier processor. They do it by giving every processor less to worry about.
