Travel Settlements Example for Online Merchants

A £1,200 holiday booking can look like a successful sale at checkout, yet the money may not be available to the travel business for days or weeks. A practical travel settlements example shows why: authorisation, capture, acquirer settlement, supplier payments, refunds and chargeback exposure all operate on different timelines. For travel merchants, understanding those timelines is central to protecting cash flow while keeping payment acceptance friction low.

What settlement means in travel payments

Settlement is the movement of cleared card funds from the acquiring side of the payment chain to the merchant’s nominated bank account. It is not the same as a customer seeing a payment leave their account, and it is not necessarily the same as the point at which a travel provider receives its share of a booking.

A card payment usually begins with authorisation. The issuer checks the card, available funds and risk signals, then approves or declines the transaction. An approval gives the merchant permission to take payment, but the funds are not yet fully transferred. The merchant must capture the transaction, either immediately or at a later point permitted by the card scheme and acquirer arrangement. Once captured and submitted, the acquirer processes the transaction through clearing and settlement.

For a standard retail purchase, this sequence is relatively short. Travel creates more complexity because fulfilment may happen months after booking. A flight, hotel stay, package holiday or car hire can be cancelled, amended or disputed long after the initial payment. Acquirers therefore assess travel as a sector with elevated delivery and chargeback risk, particularly where there is a long gap between payment and departure.

A travel settlements example from booking to payout

Consider an online travel agent selling a package holiday for £1,200. The traveller pays with a UK-issued Visa card on 1 March, while the departure date is 1 July. The agent uses a payment gateway connected to its acquiring partner and has agreed a two-business-day settlement cycle, subject to its reserve terms.

At checkout, the gateway sends the payment request with the transaction amount, currency, card data and fraud signals. 3D Secure v2 may be applied depending on the risk assessment and regulatory requirements. The customer’s issuer authorises the £1,200 payment. The booking platform confirms the reservation and captures the payment on the same day.

On 3 March, the acquirer settles the transaction. Assume the agreed acquiring and processing cost is 2.8%, or £33.60. Before reserve deductions, the merchant’s net settlement is £1,166.40. If the acquirer holds a 10% rolling reserve against the gross transaction value, a further £120 is withheld temporarily. The merchant receives £1,046.40 into its settlement account or bank account, depending on the agreed setup.

The withheld £120 is not automatically a loss. It is a risk buffer that may be released after an agreed period, provided the booking is fulfilled and no dispute or refund is raised. The precise reserve percentage, release period and scope vary by acquirer. A financially established hotel group with short booking lead times may receive more favourable terms than a newly launched travel intermediary selling long-dated package holidays.

The travel agent now has separate commercial obligations. It may need to pay the airline, hotel, transfer operator and other suppliers according to its contracts with them. Those supplier payouts are not card settlement. Treating them as the same process is a common source of reconciliation errors and cash-flow pressure.

Suppose £700 is owed to the hotel and £250 to the airline shortly after booking. The agent can pay £950 in supplier costs while only £1,046.40 has been received from the acquirer. That leaves £96.40 before overheads, support costs, taxes and future reserve releases. The gross booking value may appear healthy, but the available cash position is much tighter.

What happens if the customer cancels?

If the traveller cancels on 20 March and is entitled to a £900 refund, the merchant must return funds through the original payment method. The acquirer will generally deduct the refund from a future settlement batch. If the merchant has insufficient incoming volume, it may need to fund the refund directly or have the amount debited from its account.

The original processing fee may not always be returned. This depends on the acquiring agreement, card scheme rules and the nature of the fee. The merchant must also reverse or renegotiate supplier payments where possible. If a hotel has already been paid and its cancellation policy permits only a partial recovery, the merchant can face a material loss despite having processed the refund correctly.

What happens if the customer raises a chargeback?

A chargeback is different from a refund because it is initiated through the cardholder’s issuer. The issuer may raise a dispute for reasons including non-receipt of services, cancellation, duplicate processing or fraud. In travel, the evidence needed to defend a dispute can include booking confirmation, acceptance of terms, 3D Secure data, cancellation policy acknowledgement, customer communications, supplier confirmation and proof of travel or check-in.

When a £1,200 chargeback is raised, the acquirer may debit the amount from the merchant’s balance while the case is reviewed. A chargeback fee can also apply. If the merchant successfully represents the transaction with compelling evidence, the funds may be restored. If it loses, the original reserve may help offset the financial impact, but it will not remove the operational cost or the risk to the merchant’s chargeback ratio.

Why timing matters more than the headline settlement cycle

A two-day settlement cycle sounds straightforward, but it does not tell the full story. Travel merchants need to model three timing gaps: the interval between booking and service delivery, the interval between supplier payout and customer travel, and the interval during which refunds or disputes can reduce available funds.

The longer these gaps are, the more working capital the business may need. A merchant that pays suppliers immediately but sells travel six months ahead has a different risk profile from a hotel that captures payment a few days before arrival. Neither model is inherently wrong. The payment setup, reserve structure and supplier contracts need to match the operating model.

Currency adds another layer. A customer may pay in euros while the merchant settles in pounds and pays a hotel in dollars. Foreign exchange conversion can occur at more than one point, creating margin uncertainty. Multi-currency acceptance and settlement can reduce unnecessary conversions, but the right arrangement depends on where customers pay, where suppliers are paid and which currencies the merchant can hold and reconcile efficiently.

Building a settlement model that supports growth

A sound settlement model starts before the merchant account is approved. Acquirers need a clear picture of the business: average booking value, projected volumes, lead time before travel, cancellation policy, supplier relationships, licensing where applicable, historical refunds and chargebacks, and the jurisdictions being served. Clear, accurate underwriting reduces the risk of unexpected funding restrictions later.

At an operational level, finance and payments teams should reconcile each booking against the full payment lifecycle. That means matching the booking reference to authorisation, capture, settlement, refund, chargeback, reserve movement and supplier payment. Automated reporting, webhooks and consistent transaction identifiers make this much easier, especially where several acquirers or payment methods are in use.

Payment orchestration can also be valuable for larger travel businesses. Routing can direct transactions to the most suitable acquirer based on card type, customer location, currency, risk profile or approval performance. The objective is not simply to add providers. It is to improve approval rates, manage concentration risk and maintain reliable acceptance without creating an unmanageable reconciliation burden.

Fraud controls should be calibrated with the same care. Travel bookings are attractive to fraudsters because ticketing and supplier payments can happen quickly, while disputes may arrive later. Excessive decline rules, however, can reject genuine high-value bookings and reduce conversion. A balanced approach combines 3D Secure v2, device and velocity checks, address and card verification where appropriate, manual review for selected transactions, and clear evidence capture throughout the booking journey.

Questions to ask before agreeing settlement terms

Before signing an acquiring agreement, travel merchants should establish the settlement frequency, whether weekends or bank holidays affect funding, the currencies available for settlement, and all fee components. They should also understand the reserve calculation, release schedule, trigger conditions for additional security, and the process for funding refunds when settlement volume is low.

It is equally useful to ask how the acquirer evaluates travel delivery risk. A business selling refundable hotel stays has different exposure from a platform collecting funds for multiple independent suppliers. Transparent policies, strong customer service, clear descriptors and timely refund handling can all reduce disputes, but they do not replace an acquiring structure designed for the sector.

The best travel settlement arrangement is the one that reflects how the merchant actually sells, fulfils and pays suppliers. When payment data, reserve terms and payout timing are visible in one operating view, finance teams can make faster decisions and payment teams can protect conversion without losing control of risk.