Travel Payment Processing: Reserves, Future Delivery, and the Unflown Ticket Problem

The chargeback ratio is under half a percent. The refund rate is normal, the fraud numbers are clean, and the account has run for two years without an incident. Then a strong booking season arrives, forward bookings double, and the processor raises the rolling reserve and stretches funding by a week. Nothing went wrong. The reserve is not a punishment for past performance. It is collateral against trips that have not happened yet, and a good quarter makes the pile of undelivered promises bigger. This is a guide to how travel actually gets underwritten, why supplier risk becomes your risk at the MID level, and what a payment stack built for future delivery looks like.

You are underwritten on the gap, not the ratio

Most high-risk verticals are priced on dispute behavior. Travel is priced on time.

When a customer pays in March for a trip in October, the acquirer takes on seven months of contingent liability. If the merchant becomes insolvent before October, every open booking converts to a services-not-provided chargeback, and the acquirer pays cardholders back. The merchant is gone by then, so the reserve is the only asset the bank controls.

This is why two travel merchants with identical chargeback ratios get very different terms. A same-week hotel booking engine carries days of exposure, while a tour operator selling escorted trips a year out carries a year of it, at four-figure average tickets, against a book that grows every time marketing succeeds. Underwriters build the model from your average booking window, your average ticket, your refund history, your supplier concentration, and your balance sheet, then size the holdback to the part of the book that is still undelivered.

The practical consequence is that arguing about your chargeback ratio in an underwriting call does not move the reserve much. Producing a forward-booking ledger does. Merchants who instrument that ledger and report it without being chased negotiate reserves down, and merchants who cannot answer "how much have you sold that has not travelled yet" get the default number.

The supplier failure that lands on your account

The second structural fact of this vertical is that fulfillment is usually not yours to control.

An agency or OTA sells inventory owned by airlines, hotels, and tour operators. When one of those suppliers stops operating, cardholders do not dispute against the supplier. They dispute against the name on their statement, which is you. An upstream collapse arrives at your MID as a wave of services-not-provided chargebacks on transactions that were legitimate when they settled, and the loss severity is the full ticket price rather than your margin.

Acquirers know this, which is why supplier concentration is an underwriting question. Selling one carrier's inventory into one region is a single point of failure that your bank is co-signing.

There are three real mitigations, and none of them covers all of it. Diversify suppliers so no single failure can take out a meaningful slice of the forward book. Where the model allows, structure so the airline or hotel is merchant of record for the travel component and you are merchant of record only for your fee, which moves the contingent liability to the party that delivers. And keep cancellation and pass-through terms explicit and click-accepted at checkout, because in a supplier-failure representment your terms are most of the evidence you have.

Three tiers, and what each one costs you

	Aggregator	Domestic dedicated travel MID	Specialist or offshore acquiring
Boards long-window travel	Sometimes, until volume grows	Yes, with financials and accreditation	Yes, specialist appetite
Underwriting focus	None at signup	Booking window, suppliers, balance sheet	Varies, often exposure-capped
Reserve	None, then a 90 to 180 day hold	Rolling, sized to the unflown book	Often higher, sometimes upfront
Response to a volume spike	Automated hold	Reserve resize with notice	Negotiated, relationship-driven
Realistic role	Short-window volume only	Primary processing	Cross-border volume, redundancy

Aggregators are the specific trap in travel, because the failure mode is timed against you. Stripe, PayPal, Square, and Shopify Payments underwrite after volume arrives, and their risk models respond to exactly the signals a healthy travel business generates: seasonal spikes, large average tickets, and a growing forward book. The hold lands during peak season, which is precisely when you owe suppliers deposits, so a cash-flow problem and a processing problem arrive on the same morning. The pattern is the one described in why processors shut down high-risk accounts, with worse timing than most verticals get.

A dedicated MID through an acquirer with real travel appetite trades convenience for predictability. Underwriting is slower and reserves are explicit, but a reserve you negotiated and can forecast is a manageable cost, while a surprise 120-day hold on peak volume is an extinction event.

Specialist and multi-region acquiring earns its place on cross-border volume. If a large share of your cardholders sit outside the US, domestic-only acquiring pays cross-border interchange and absorbs issuer-country decline patterns that local acquiring does not see. The honest cost is higher pricing, more FX handling, and another compliance relationship.

Accreditation and coding

Travel agencies typically run under MCC 4722, and that code carries assumptions with it. Acquirers want to know whether you hold ARC or IATA accreditation, whether you sell air separately from packages, and whether you are merchant of record for the travel itself or only for a service fee.

Accreditation is not required to process, but it changes the conversation, because an accredited agency has already been financially vetted by a party the bank recognizes. Without it, the burden shifts entirely onto your own financials and booking-window data.

Whatever the answer, describe the business accurately at boarding. Selling long-window packages under a description that implies immediate delivery is the misrepresentation that gets accounts terminated rather than repriced, and misrepresentation at onboarding is the termination reason most likely to produce a MATCH listing that follows the principal for five years.

The disputes are recognition and expectation gaps

Travel's dispute mix is unusual because most of it is not fraud in any ordinary sense.

The largest cluster is cancellation and refund conflict, where the customer cancels under the policy they believe applies and the merchant refunds under the supplier's stricter one. The second is services not provided, after a schedule change, a cancelled flight, or a supplier that stopped operating. The third is trip quality, where the delivered room category or itinerary did not match the listing. The fourth is pure recognition failure: a booking made in February, read on a statement in March, for a trip not yet taken and a brand name the cardholder does not remember.

Descriptors do more work here than in almost any other vertical because of that gap. A descriptor that names the destination or the trip, matched to confirmation and pre-trip emails from the same brand, removes a large share of "I do not recognize this" disputes before they start.

Prevention alerts are the other high-value control. Enrolling in Ethoca and Verifi CDRN and RDR, and wiring them into the booking system rather than only into the finance inbox, means an early dispute on an untraveled itinerary can trigger a cancellation and refund instead of a full-severity chargeback on a four-figure ticket. Measure what that does to your numbers using the chargeback ratio explainer, and keep the chargeback reason code reference beside your representment templates, because the evidence that wins a services-not-provided dispute is not what wins a cancellation-policy dispute.

For representment, the winning file is fulfillment evidence: click-accepted cancellation terms with a timestamp, itinerary delivery confirmation, supplier check-in or boarding data, and any post-trip contact from the customer.

Architecture for delivery-horizon risk

Build the stack around the two facts above.

Split volume across at least two acquiring relationships, and where you can, split by booking window rather than at random. Short-window bookings look like ordinary ecommerce and can carry ordinary terms, while long-window packages are the exposure that drives reserves, so keeping them on separate facilities stops your highest-risk book from pricing all of your volume. The routing mechanics are in the MID load balancing guide.

Store card credentials above the acquirer layer. Tokenization does double duty in travel: it keeps a repeat customer base portable when you change acquirers, and it lets you charge balances, changes, and incidentals months after the original booking without asking for the card again. An agency whose stored credentials live inside one processor cannot move without losing the ability to collect a final balance, which is the trap the token vault explainer exists to prevent.

Then treat the forward-booking ledger as a payments asset rather than a finance report. It is the document that argues your reserve down, and the number your acquirer asks for before every resize.

Practical takeaway

Travel is not hard to bank because travel merchants dispute badly. It is hard to bank because you collect today for something delivered months from now, because your average ticket makes every dispute expensive, because a supplier's failure arrives as your chargebacks, and because growth increases the acquirer's exposure instead of reducing it. The merchant who lasts boards with an acquirer that already runs travel, describes the booking window honestly, negotiates the reserve against forward-booking data, splits short-window and long-window volume across two banks, wires prevention alerts into the booking system, and keeps credentials in a neutral vault so an acquirer change is an inconvenience rather than a rebuild. The merchant who fails runs peak season through an aggregator and finds out in July that the money for supplier deposits is on a 120-day hold. For a walkthrough of what a durable travel and booking payment stack looks like at your volume and booking window, apply for an architecture review.