Why Travel Merchants Need Extra Scrutiny During MSP Onboarding

The Liability That Arrives Late

Most merchant categories settle the question of fulfillment within days. A retailer ships, a carrier scans, and the window for a non-receipt claim starts to close. Travel works differently. A family books a cruise in January for an August sailing, and the acquiring side funds that transaction long before anyone steps on board.

That gap is where the risk lives. Under Visa reason code 13.1 (Merchandise/Services Not Received), the filing window is generally measured from the date the cardholder expected to receive the service, capped at 540 days from the original transaction processing date. Mastercard handles non-receipt claims under reason code 4853 (Cardholder Dispute), which absorbed the former 4855 code, and it also measures timing against the expected service date.

So on a travel transaction, the clock often starts on the day the trip was supposed to happen.

If the merchant delivers, none of this matters much. If the merchant fails, whether through insolvency, a supplier collapse, or a mass cancellation event, issuers begin filing on behalf of their cardholders and the resulting travel merchant chargebacks flow back to the acquiring side. When the merchant cannot fund them, the MSP and its sponsor bank absorb the loss. A single failed operator with a long booking window could potentially generate months of non-receipt chargebacks against revenue that was settled and spent long ago.

Why Standard Underwriting Models Miss It

Conventional onboarding leans on a familiar set of inputs. Processing history, prior chargeback ratios, MCC, ownership, and financial statements all feed the decision. Those inputs work reasonably well for merchants whose disputes surface close to the sale.

For travel merchant chargebacks, they can mislead. A tour operator’s historical ratio reflects bookings that have already been fulfilled. It says very little about the bookings sitting in the pipeline right now, and those are the transactions that will drive next season’s dispute activity.

A travel merchant can present a low ratio at onboarding precisely because a large share of its volume has not yet reached the point where a dispute is possible. The lag hides the exposure. And MCC alone will not separate a hotel that charges at checkout from an online agency collecting full prepayment a year in advance, even though their risk profiles look nothing alike.

The Dispute Drivers Specific to Travel

Beyond the timing issue, travel combines several dispute drivers that rarely appear together in other verticals. Each one deserves its own line of questioning during onboarding, because each one calls for a different mitigation.

Cancellations, Schedule Changes, and Policy Friction

Flights get rescheduled. Tours get consolidated. Hotels overbook. When a cardholder’s understanding of the cancellation or credit policy differs from the merchant’s, disputes follow, and vouchers or future travel credits are a frequent flashpoint. Ask how policies are presented at checkout and how acceptance is recorded.

Multi-Party Fulfillment Chains

Many travel merchants sell services delivered by someone else. An online agency may package a flight, a hotel, and a transfer from three separate suppliers. If any link breaks, the dispute is filed against the merchant of record. Understanding how liability is allocated in those supplier contracts, and whether the merchant has recourse, tells you a great deal about how a failure would play out.

Descriptor Confusion Across Booking Channels

Travel purchases often pass through metasearch sites, booking engines, and white-label platforms. The name on the statement may not match the brand the cardholder remembers booking with. Unrecognized transactions can turn into disputes quickly, especially when the charge posts months before travel. Map every booking channel to the billing descriptors that will appear on statements.

First-Party Fraud on Consumed Services

Some cardholders take the trip and then claim it never happened, or that it differed materially from what was described. These cases are winnable. But only if the merchant captures the right evidence, such as check-in records, boarding data, itinerary confirmations, and communication logs. Merchants that cannot produce this data on demand will often lose cases they should win.

Event-Driven Volatility

Weather, airspace closures, public health events, and geopolitical disruption can hit a travel portfolio all at once. Exposure in this vertical tends to be correlated. When one travel merchant sees a cancellation spike, others in the same region or segment often see it too, and that concentration effect matters at the portfolio level.

What Deeper Onboarding Diligence Looks Like

We recommend treating travel onboarding as a separate track with its own diligence package. At a minimum, that package should capture the following:

• Booking-to-service window distribution, broken out by product type and channel
• An estimated future delivery exposure figure, calculated from average daily volume multiplied by the average number of days between transaction and service
• Supplier contracts, including liability allocation and the merchant’s recourse if a supplier fails
• Cancellation, refund, and travel credit policies, with screenshots of how they appear at checkout
• A full map of booking channels and the billing descriptors tied to each
• Evidence capture capability for check-in, boarding, and itinerary data
• Applicable seller-of-travel registrations, bonding, or industry accreditations
• Current alert enrollment and the merchant’s ability to respond within alert windows

The future delivery exposure figure deserves special attention. It gives your risk team a rough sense of how much settled volume could come back if the merchant stopped delivering tomorrow. It will never be precise. Still, it reframes the conversation around the liability the portfolio is carrying today, rather than ratios the merchant has already posted.

Sizing Reserves and Limits to Future Delivery Exposure

Once exposure is quantified, it can drive account structure. Rolling reserves, delayed settlement, and volume caps are familiar levers. For travel, the difference is calibration. A reserve sized to historical chargeback losses will usually be undersized for a merchant whose risk sits in the future.

Some MSPs tie reserve levels directly to the booking window, so a merchant collecting payment nine months ahead carries a different requirement than one collecting thirty days out. Others stage volume limits, raising caps only after a full travel season demonstrates fulfillment performance. Either approach could potentially reduce the chance that a single failure becomes a portfolio event.

The network context makes this more pressing. Under VAMP, Visa evaluates acquirer portfolios against an Above Standard threshold of 0.5% and an Excessive threshold of 0.7%, while the merchant Excessive threshold has been 1.5% in North America, the EU, and Asia Pacific since April 2026, with volume minimums applying. Mastercard’s Excessive Chargeback Program classifies a merchant as an Excessive Chargeback Merchant (ECM) at 100 chargebacks and 150 basis points in a calendar month, and as a High Excessive Chargeback Merchant (HECM) at 300 chargebacks and 300 basis points. A cluster of travel merchants hit by the same disruption could potentially shift a portfolio’s position against these thresholds within a single reporting cycle.

Building Dispute Infrastructure Into the Account

Reserves protect the MSP after something goes wrong. Dispute infrastructure reduces how often something goes wrong in the first place. For travel accounts, we see a strong case for making that infrastructure part of the onboarding package itself.

At the inquiry stage, DEFLECT integrates Verifi Order Insight and Ethoca Consumer Clarity to deliver itinerary details, booking references, and merchant branding to issuer call centers and banking apps. When a cardholder doesn’t recognize a charge from a booking platform, that context can settle the question before a dispute is ever filed.

At the dispute stage, RESOLVE consolidates Ethoca Alerts, Verifi CDRN, and Visa RDR into one interface, so cancellation-driven disputes can be refunded before they become chargebacks. For a travel merchant facing a wave of schedule changes, the ability to act within alert windows at scale often separates a contained event from a ratio problem.

And for travel merchant chargebacks tied to consumed services, RECOVER automates representment using the check-in, boarding, and confirmation data captured during onboarding, helping merchants recover revenue they would otherwise write off.

There is a commercial angle here as well. Travel merchants know their vertical is scrutinized. An MSP that pairs deeper diligence with ready-made dispute solutions gives those merchants a reason to sign, and a reason to stay.

Monitoring After Go-Live

Onboarding diligence sets the baseline. Ongoing review keeps it current. Travel merchant chargebacks rarely announce themselves early, so the most useful indicators tend to be leading ones: alert volume relative to bookings, refund requests, the share of alerts that convert into chargebacks, shifts in the average booking window, and news about the merchant’s key suppliers. A sudden lengthening of the booking window, for example, could potentially signal a merchant pulling cash forward. Quarterly reassessment of future delivery exposure keeps reserves aligned with what the account is carrying now.

Strengthen Your Travel Onboarding Track

If your portfolio includes travel merchants, or you are weighing whether to take them on, onboarding is where the most leverage sits. We can help your team build a diligence framework around future delivery exposure, configure alert coverage through RESOLVE before the first booking settles, and set up evidence capture so travel merchant chargebacks tied to consumed services can be contested through RECOVER. Reach out to our team to discuss how these solutions can be packaged into your travel onboarding process.

Why ChargebackHelp?

ChargebackHelp gives MSPs a single, card-agnostic platform for managing chargeback risk across an entire merchant portfolio. Our solutions connect directly to programs from Visa, Mastercard, Verifi, and Ethoca, automating work at the inquiry, dispute, and chargeback stages so your risk team can focus on oversight instead of case handling. That automation also becomes part of what you sell. Merchants gain prevention and revenue recovery from day one, and your portfolio gains a structural buffer against the threshold pressure that network programs continue to apply. Contact us to see how it fits your book of business.