A traveler pays for a trip through your agency. The airline changes the flight, the traveler declines the alternative, and your team receives a refund request. Before anyone promises a date, staff need to know who processed the airfare, what the airline has confirmed and which part of the booking is affected.
Travel agency payment processing is partly a responsibility problem. One itinerary may contain airfare, lodging, transfers and an agency service fee, with different suppliers and payment arrangements. A single “refunded” checkbox cannot explain that transaction.
Scope and date: Checked September 21, 2026. The federal rules discussed here concern covered air transportation to, from or within the United States. They are not a universal refund rule for hotels, cruises, tours or every travel package. This is operational education; counsel should assess your contracts, jurisdictions and business model.
Start with the merchant of record for the airfare
DOT explains that a ticket agent serving as merchant of record has airfare refund responsibilities when a covered flight is cancelled or significantly changed and the applicable conditions are met. The merchant of record is the entity responsible for processing the consumer's payment, reflected in the financial charge statement. See DOT's passenger refund guidance.
Do not infer that role from whose logo appears on the itinerary. An agency can arrange a booking while the airline processes the airfare. In another arrangement, the agency processes the customer payment and then pays suppliers. Record the actual arrangement for each transaction.
Make that distinction visible to support staff before a disruption. Useful fields include the supplier, booking reference, original transaction reference, amount, payment method and merchant of record. Where a package combines services, maintain a component breakdown your finance team can reconcile.
Ticket-agent refunds are not identical to airline automatic refunds
The current ticket-agent provision, 14 CFR 399.80(l), requires qualifying refunds upon request when the agent is merchant of record. For credit-card purchases, its prompt-refund definition is seven business days after the agent receives the carrier information specified in 14 CFR 260.6(d). For cash, check, debit-card and other purchases, it is twenty calendar days after the refund becomes due. Refunds generally go to the original payment form unless the consumer agrees to another cash-equivalent form. See the current ticket-agent rule.
That wording matters. An agency should not copy an airline's automatic-refund timeline into its procedure without mapping the different triggers. Conversely, waiting for a traveler to chase several departments is a poor way to manage an actual request.
The airline must supply eligibility information without delay after receiving a consumer refund request through the agent, and promptly transfer consumer funds when the agent owes the refund but does not hold those funds. See 14 CFR 260.6(d)-(e). Build an escalation path for missing information and funding.
Separate flight cancellation from an unused ancillary service
An airfare refund after a cancelled trip is different from a claim for an optional service that was not provided on a trip the passenger took. DOT identifies the airline as responsible for qualifying refunds of unprovided ancillary services and significantly delayed or lost checked bags, even when a ticket agent was merchant of record for that fee. See DOT's distinction between ticket and ancillary-fee refunds.
For your operating procedure, use separate issue categories. “Flight cancelled; traveler declines alternative” should route differently from “paid Wi-Fi unavailable” or “checked bag delayed.” Preserve the traveler’s description, airline notice and relevant receipt so the responsible party can assess the request.
Also distinguish refunds from fee-disclosure rules. DOT's July 2026 action restored earlier ancillary-fee disclosure provisions following the vacatur of a separate 2024 rule. That action should not be described as eliminating the current airfare refund duties. See the July 2, 2026 final rule.
Build one refund case with several accountable steps
Treat each refund as a case linked to the original booking and payment. Record the request time, reason, supplier response, traveler decision, applicable deadline and assigned owner. Keep “eligibility confirmed,” “refund submitted” and “refund completed” separate.
For example, a refund instruction accepted by your payment portal does not necessarily mean the traveler already sees the funds. Give staff language that describes the confirmed stage. Reconcile the refund reference to the original charge and maintain any supplier receivable separately.
When a package includes a hotel, use the relevant hotel contract and applicable rules for that component. Do not automatically apply the airfare result to the entire package. Explain the component status clearly so the customer does not receive conflicting messages from different team members.
Plan cash flow around future travel
Future departures create a useful management question: how much customer money relates to services that have not yet occurred? Maintain a view by departure month, supplier and refund exposure.
Discuss reserves, settlement timing and refund-funding arrangements with the provider before peak season. Ask how a large cancellation event would affect available processing funds and how refunds are initiated if normal settlements are insufficient. Those are provider-specific terms; a travel merchant account does not come with one universal reserve formula.
Use actual booking data to model a disruption scenario. Distinguish amounts held by the agency from amounts already paid to suppliers. Identify who can authorize a refund and who monitors supplier recovery. This is a planning exercise, not a substitute for legal or accounting advice.
A travel payment review checklist
- Map the merchant of record for each airfare transaction.
- Separate airfare, ancillary fees, agency fees and other travel components.
- Store the original payment and supplier references together.
- Record the traveler's request and decision about alternatives.
- Map the correct rule, eligibility trigger and deadline.
- Escalate missing airline information and supplier funds.
- Reconcile refunds independently from supplier recoveries.
- Review provider terms against your future-departure exposure.
- Have counsel assess state seller-of-travel obligations where applicable.
Questions agency owners ask
Must every travel purchase be automatically refunded?
No. The DOT provisions discussed here address defined air-travel situations, with different airline and ticket-agent responsibilities. Other travel services require their own assessment.
Can we keep an agency service fee?
The ticket-agent rule permits retention of certain disclosed per-passenger service fees for qualifying services beyond merely processing payment for a flight the traveler found. Have counsel review the service, disclosure and fee against 399.80(l); do not assume all fees are retainable.
Does a processor decide whether a traveler is owed a refund?
Processing functionality and legal refund entitlement are different issues. Your team needs a documented assessment and an executable payment workflow.
Make the refund path part of your merchant review
Bring sample bookings, supplier arrangements and a recent anonymized refund timeline to the conversation. Stratamize can help map reporting and payment handoffs for travel merchant accounts, with eligibility subject to provider review. Book with Joseph to discuss where the booking, supplier and payment records need to connect.