Travel Agency Payment Processing in 2026: Merchant Accounts, Reserves and Future-Delivery Risk
If you operate a travel agency, tour business or online booking service, accepting a credit card can be the easiest part of the customer experience—and one of the hardest parts of your financial infrastructure.
The problem is not simply that travel is considered “high risk.”
When a customer pays today for a trip that may not occur for several months, the payment processor and acquiring bank must evaluate what could happen before the service is delivered. A canceled itinerary, supplier failure, delayed refund or business closure can create cardholder claims long after the original transaction was approved.
That is why a travel merchant account is underwritten around the entire booking model: who charges the traveler, what the charge covers, when suppliers are paid, how cancellations are handled, how long fulfillment takes and whether the agency has enough liquidity to absorb refunds.
Quick answer: Travel agencies can obtain merchant accounts, including startups without prior processing history. Approval, pricing, funding speed, reserves and volume limits depend on the agency’s merchant-of-record structure, projected sales, average ticket, booking window, supplier relationships, financial condition, refund obligations, licensing and payment technology. No gateway or sales platform eliminates the need for underwriting.
For an overview of the solutions Align supports in this vertical, visit our travel payment processing page.
Why Do Travel Agencies Receive Additional Underwriting Scrutiny?
In a conventional retail transaction, the customer pays and receives the product immediately. The processor’s exposure usually begins and ends within a short period.
Travel works differently. A customer may pay a deposit in January for a trip in September. During that interval, several events can affect fulfillment:
The traveler cancels or requests a refund.
The airline, hotel, cruise line or tour operator changes the itinerary.
A supplier becomes insolvent or fails to deliver.
The agency and traveler disagree about what was included.
The cardholder does not recognize the billing descriptor.
The transaction was unauthorized.
The agency lacks the cash to process a required refund.
These risks can be amplified by high ticket values, seasonal sales spikes, installment plans, international customers and dependence on third-party suppliers.
Being treated as higher risk does not mean the agency is illegitimate. It means the institution responsible for the merchant account sees more potential financial exposure than it would with an immediately fulfilled sale. Our high-risk payment processing guide explains how that distinction affects underwriting more broadly.
What Is MCC 4722?
Merchant Category Code 4722 generally identifies travel agencies and tour operators. Mastercard’s current materials list MCC 4722 as “Travel Agency & Tour Operators,” and Mastercard defines an MCC as a four-digit code assigned by the acquirer to describe the merchant’s line of business.
That last point matters: the merchant does not unilaterally choose its final MCC.
The acquiring institution reviews the agency’s primary business activity and assigns the classification used in the processing relationship. An agency can explain its business accurately and identify the code it expects, but the final determination belongs to the acquiring side of the payment relationship.
MCC 4722 may fit businesses that arrange or sell travel, tours, transportation, accommodation or packages. It does not mean every travel-related business belongs under the same code. Airlines, cruise lines, lodging businesses, transportation providers and other travel-adjacent businesses may have different classifications.
An inaccurate MCC is not a creative approval strategy. If the account is boarded under a category that does not match the actual business, later monitoring can lead to requests for information, restrictions or termination. The application, website, contracts and transaction activity should all describe the same operating model.
Merchant of Record vs. Agency-Fee Models
One of the first underwriting questions is deceptively simple:
What exactly does your company charge to the traveler’s card?
When the agency collects the full travel cost
If the traveler pays the agency for the combined airfare, hotel, cruise, tour or package, and the traveler sees the agency’s name on the card statement, the agency may be functioning as the merchant of record for the customer transaction.
That creates broader exposure. The agency must explain how suppliers are paid, who is responsible for cancellations and refunds, what happens if a supplier fails and how the agency will return funds after supplier payments have already been made.
The underwriter may request contracts, cash-flow details and evidence that each booking can be traced from the customer payment to the related supplier obligation.
When the agency charges only a separate service fee
Some agencies charge a separately disclosed planning, consultation or booking fee while the airline, hotel, cruise line or other supplier charges the traveler directly for the underlying travel.
In that structure, the agency’s merchant account may be exposed only to its own fee rather than the full trip value. That can materially change the payment risk, but it does not remove underwriting. The fee must be clearly disclosed, supported by an actual service and separated from supplier charges in the customer agreement and payment flow.
Why the distinction must be documented
The website, checkout, invoice, agreement and card statement should make it clear:
Which legal entity is charging the card
What the charge covers
Which company is responsible for delivering each service
Who handles cancellations, changes and refunds
What name will appear on the cardholder’s statement
An agency should not collect funds for undisclosed third parties through an ordinary merchant account. Marketplace, payment-facilitation and split-settlement models require payment infrastructure and underwriting designed for those roles.
Can a Startup Travel Agency Get a Merchant Account?
Yes. The absence of prior processing history is not an automatic decline.
It does mean the underwriter has fewer performance records to evaluate. An established agency can show processing statements, refund history and chargeback ratios. A startup must prove readiness through other evidence.
Underwriters may place more weight on:
The owners’ travel-industry and operating experience
Personal and business credit, when reviewed with proper authorization
Available operating capital
Business and personal bank statements
Supplier or host-agency agreements
Seller-of-travel registration or a documented exemption, where applicable
The website, booking terms and refund policy
The agency’s sales and marketing channels
Projected monthly volume, average ticket and maximum ticket
The time between customer payment and travel fulfillment
The proposed gateway, checkout and fraud controls
A personal guarantee may be requested, particularly when the business has no financial or processing history. Whether it is required depends on the specific underwriting program and applicant.
The most credible startup application does not pretend the business already has performance data. It provides a conservative forecast, explains the assumptions behind it and shows how the agency will manage refunds and supplier obligations while the account establishes a track record.
What Is Future-Delivery Risk in Travel?
Future-delivery exposure is the value of customer payments collected for travel or services that have not yet been fulfilled.
Suppose an agency processes $50,000 this month, but the related trips will occur over the next six months. From a risk perspective, the institution is not evaluating only the $50,000 in sales. It is evaluating how much of that money could still become a refund or dispute before fulfillment.
This is why two travel agencies processing the same monthly volume can receive very different terms.
An agency that collects a small planning fee and sends customers to suppliers for the remaining balance may create less future-delivery exposure than an agency that collects the entire price of long-dated international packages. An established company with strong liquidity, short booking windows and documented supplier payments may be viewed differently from a startup using current bookings to fund earlier obligations.
Underwriters may ask for an unfulfilled-bookings report showing:
Booking date
Payment date and amount
Traveler name or customer identifier
Travel or fulfillment date
Supplier and supplier-payment status
Refundable and nonrefundable components
Current booking status
Remaining amount owed
For a deeper example of why advance payments matter when travel fulfillment is disrupted, read our article on future-delivery payment risk.
Why Supplier and Host-Agency Agreements Matter
A host-agency relationship can strengthen a new agency’s operational story, but it is not a substitute for underwriting the applicant.
The processor may still need to know:
Whether the host or the independent agency contracts with the traveler
Which entity issues the invoice
Which entity charges the card
Which entity pays the supplier
Who controls the booking record
Who is responsible for customer support, cancellations and refunds
Whether the agency has access to booking and fulfillment evidence
Supplier agreements help establish that the business has a legitimate path to deliver what it sells. They can also reveal minimum deposits, cancellation penalties, settlement timing and other obligations that affect cash flow.
If the agency sells custom itineraries through several suppliers, it should be able to reconcile each customer charge to the corresponding booking and supplier records. A generic invoice that says “travel services” is rarely as useful as a file containing the itinerary, traveler acknowledgment, booking reference, supplier confirmation and payment history.
Seller-of-Travel Registration Is a Payment Issue Too
Seller-of-travel requirements are state-specific. Agencies should not assume that forming an LLC in one state resolves every registration or disclosure obligation in the states where they operate or sell.
For example:
Florida states that a seller of travel with a Florida business location, or one that offers travel-related services in Florida, must register unless an exemption applies. Florida separately explains how a business can document an exemption.
California requires sellers of travel to register with the Attorney General’s Office and display the registration number in advertising.
Washington maintains a seller-of-travel licensing program.
Other states may use different rules or may not require a travel-agent license. The analysis can depend on the agency’s location, where customers are located, what is sold and whether an exemption applies.
From an underwriting perspective, the processor may request the registration, bond, trust-account information or exemption letter applicable to the business. A pending application should be identified as pending; it should not be represented as an active registration.
This article is not legal advice. A travel business should obtain qualified counsel or guidance from the relevant state agency about its specific obligations.
Rolling Reserves, Delayed Funding and Monthly Caps
Travel merchant-account terms are designed around exposure. Three of the most common controls are reserves, funding delays and processing limits.
Rolling reserve
A rolling reserve is a percentage of processed funds held for a defined period and then released according to the merchant agreement, provided the funds are not needed for chargebacks, refunds or other obligations.
The reserve percentage, hold period and release method should be documented in writing. Merchants should ask whether releases occur automatically, whether the reserve has a cap and what happens after account closure.
There is no universal “standard travel reserve.” A request for a reserve no higher than 10 percent can be submitted, but the underwriter may approve a different structure or decline the requested limit.
Delayed funding
Instead of—or in addition to—a reserve, the processor may fund transactions after a delay. Funding speed can depend on transaction timing, banking days, processor policies, risk review and account performance.
A request for two-business-day funding is reasonable to discuss. It is not something an ISO, gateway or sales representative should guarantee before the underwriting institution approves the account.
Monthly volume and ticket limits
The merchant application normally identifies expected monthly volume, average ticket and maximum ticket. Those figures become part of the approved risk profile.
Processing far above the disclosed amount can trigger review even when customers are satisfied and chargebacks are low. A high-ticket group booking can create the same issue if it exceeds the approved maximum ticket.
These limits are not targets to work around. They are terms to monitor and amend before the business outgrows them.
Hosted Checkout and 3-D Secure for Travel Payments
A secure travel checkout should do more than collect a card number.
It should connect the transaction to the exact booking and preserve the evidence needed for customer service, fraud review and a possible dispute.
At a minimum, the payment record should be associated with:
The traveler and payer
The itinerary or booking reference
The amount and currency
The deposit or payment schedule
The services included
The travel date
The cancellation and refund terms accepted
The billing descriptor disclosed
Relevant authentication and device data
The customer’s receipt and confirmation
EMV 3-D Secure allows transaction, payment-method and device information to be exchanged so the issuer can authenticate the customer in an ecommerce transaction. In an approved configuration, it can reduce unauthorized-payment exposure and may support a fraud liability shift in eligible circumstances.
It does not eliminate every chargeback. A customer can still dispute a transaction because a service was not provided, a refund was not received or the delivered itinerary differed from the agreement.
The gateway, acquirer and 3DS provider must be configured together. Simply adding a 3DS logo or turning on a generic fraud filter does not establish that authentication data is being submitted correctly.
Why hosted checkout matters
A hosted payment page can reduce the amount of card data handled by the agency’s own systems. For example, Authorize.net Accept Hosted provides a mobile-optimized form hosted by Authorize.net and documents an SAQ A-level integration path.
The precise PCI scope still depends on the complete implementation and whether all applicable eligibility criteria are met. The PCI Security Standards Council explains that SAQ eligibility depends on where payment-page elements originate and on meeting all other criteria.
How to Convert Telephone and Email Quotes Into Secure Checkout Sessions
Custom travel quotes do not require an agent to collect card numbers over the phone or ask a customer to email payment details.
A stronger workflow looks like this:
The agent builds the itinerary and final price inside the approved booking or CRM system.
The system creates an order-specific checkout session for the exact amount.
The customer receives a secure link that expires or is limited to that booking.
The checkout displays the agency name, itinerary summary, price, deposit schedule, cancellation terms and billing descriptor.
The traveler enters the payment details directly into the hosted form and completes any required authentication.
The successful transaction is written back to the booking record, and the customer receives a receipt.
The agency retains the accepted terms, transaction identifiers, communications and fulfillment evidence.
This makes an email or telephone quote the beginning of a documented ecommerce checkout—not permission to key an undisclosed transaction into a virtual terminal.
If the agency genuinely needs mail-order/telephone-order transactions or virtual-terminal access, that channel should be disclosed in the application and approved. MOTO activity has a different risk profile, and 3DS generally applies to customer-driven ecommerce authentication rather than an employee keying the card after a phone call.
WeTravel, Stripe and Authorize.net: What Is Actually Compatible?
The booking platform, gateway and merchant account are different layers. Travel agencies should confirm all three before selecting software.
WeTravel
WeTravel’s current documentation says its payment partners include Stripe and Airwallex. It also documents an option for eligible, verified users to connect a Stripe Standard account so new payments flow into that Stripe account.
WeTravel does not currently document a native Authorize.net connection. Its reporting, API or automation features should not be assumed to reroute checkout transactions through an outside Authorize.net merchant account.
If an agency requires WeTravel’s checkout and payment-plan functions, it should confirm the available processing structure directly with WeTravel before committing. If it requires a separately underwritten merchant account through a different provider, it may need another booking or checkout architecture.
Stripe
Stripe is not automatically unavailable to every travel agency. Its current policy lists “travel reservation services and clubs” as restricted businesses that require additional due diligence. It separately lists certain travel categories—including commercial airlines, cruises and international charter or private airlines—as prohibited.
Approval is specific to the actual business and Stripe service. An account’s ability to begin processing should not be mistaken for a permanent guarantee that every travel model, volume level or future activity is approved.
Authorize.net
Authorize.net is primarily a gateway and payment platform. It does not, by itself, approve a travel agency’s risk.
For a travel agency, an Authorize.net gateway must be connected to a processing and acquiring relationship that has approved the business model, MCC, volume, ticket size, future-delivery exposure and sales channels. The implementation must also support the agency’s booking workflow, authentication requirements and recordkeeping.
Our guide to Authorize.net versus Stripe explains why a gateway and a merchant account should be evaluated separately.
Documents Commonly Needed for Travel Merchant Underwriting
A complete file is easier to evaluate than a promising application followed by weeks of missing documents.
Depending on the business and underwriting program, a travel agency may be asked for:
Articles of organization or incorporation and EIN confirmation
Ownership and beneficial-owner information
Government-issued identification for required owners or guarantors
A voided business check or bank letter
Recent business and, when applicable, personal bank statements
Business financial statements or tax returns when requested
Prior processing statements, if any
Current refund, dispute and chargeback information
A processing forecast with monthly volume, transaction count, average ticket and maximum ticket
A schedule of booking windows and unfulfilled travel
The customer payment flow from quote through fulfillment
Supplier, host-agency and fulfillment agreements
Seller-of-travel registrations, bonds, trust information or exemption documentation where applicable
Sample customer agreements, invoices, itineraries and receipts
Refund, cancellation, privacy and terms-of-service policies
Marketing examples and a description of customer-acquisition channels
Gateway, booking platform, 3DS and fraud-control details
A written explanation of who is merchant of record and who pays each supplier
Sensitive identity, banking and tax documents should be transmitted through the provider’s secure document process—not ordinary email.
How to Scale From $50,000 to $200,000 per Month
A travel agency should disclose its real growth plan at the beginning, even if it requests a conservative initial cap.
For example, an agency expecting to begin near $50,000 per month and reach $200,000 should explain the projected timing, marketing drivers, ticket mix, seasonal factors, supplier capacity and working-capital plan. That allows underwriting to evaluate the destination, not only the first month.
The actual increase is usually earned through account performance and a formal review—not assumed because the original business plan predicted it.
1. Begin with an accurate approved profile
Use realistic volume, average ticket and maximum ticket figures. Do not lower projections solely to fit an application and then process materially more immediately after approval.
2. Keep every booking traceable
Reconcile transactions to booking references, travel dates, supplier payments, refunds and fulfillment records. A processor should be able to understand the outstanding future-delivery exposure without rebuilding it from scattered systems.
3. Maintain refund liquidity
Do not assume tomorrow’s bookings will fund yesterday’s refund obligations. Maintain operating capital and a refund process that can respond when plans change.
4. Control fraud and customer confusion
Use approved 3DS, AVS, CVV, velocity controls and manual review rules. Pair those tools with recognizable billing descriptors, fast confirmations and proactive itinerary communication.
Fraud prevention and dispute management should be reviewed before the volume increase. Our 2026 Visa VAMP guide explains why fraud and dispute signals can affect payment stability even when revenue is growing.
5. Request increases before exceeding the cap
Provide updated processing statements, bank statements, financials, booking reports and chargeback/refund data. Ask the processor what evidence and lead time it requires for a volume or ticket-limit review.
6. Grow in reviewable stages
The underwriter may approve a step-up, maintain existing terms, adjust the reserve or request more operating history. A staged path can be more realistic than an automatic jump from $50,000 to $200,000.
7. Revisit the reserve as the risk changes
A reserve is not necessarily permanent, but release or reduction is not automatic unless the agreement says so. Ask when the account becomes eligible for review and what performance evidence the institution will consider.
The Bottom Line
Travel agency payment processing is not won by finding a gateway that asks no questions.
It is won by building a merchant profile that answers the important questions before money starts moving:
Who is charging the traveler?
What does the charge cover?
When will the service be fulfilled?
Which suppliers are involved?
Who owes the refund if plans change?
How is every transaction tied to a booking?
What capital is available if refunds spike?
How will the agency grow without exceeding its approved profile?
When those answers are clear, a processor can evaluate the real business rather than making assumptions from the word “travel.”
Find Out How a Bank May View Your Travel Agency
Align Ecommerce can review your merchant-of-record structure, projected volume, future-delivery exposure, website, supplier relationships, registration status, gateway requirements and proposed checkout before a formal submission.
We cannot guarantee approval, a specific reserve, a funding schedule or a monthly cap. Those decisions belong to the processor and acquiring institution reviewing the complete file.
Travel Agency Payment Processing
2026 FAQ
Yes. Startups can be reviewed, but they usually need to support the application with operating experience, supplier or host-agency agreements, financial information, registration or exemption documents, clear customer policies, realistic projections and a well-defined payment flow.
MCC 4722 is generally used for travel agencies and tour operators. The merchant can describe its business and expected classification, but the acquiring institution assigns the final MCC based on the primary business activity.
No. Reserve requirements depend on the processor, acquiring bank, financial condition, ticket size, booking window, refund exposure, processing history and other factors. Some accounts may receive a rolling reserve, delayed funding, volume cap, upfront reserve or a combination of controls.
Yes. The requested ceiling can be included in the underwriting discussion, but it cannot be guaranteed before the reviewing institution evaluates the complete file. The merchant does not have to accept an offer that exceeds its stated limit.
Potentially. Funding speed depends on the approved processing relationship, transaction timing, banking days, risk controls and ongoing account performance. It should be confirmed in the written approval and merchant agreement.
No. 3DS helps authenticate customers in ecommerce transactions and can reduce certain unauthorized-payment risks. It does not prevent disputes involving cancellations, services not provided, refund delays or dissatisfaction with the itinerary.
WeTravel’s current public documentation identifies Stripe and Airwallex as payment partners and explains how eligible users can connect a Stripe Standard account. It does not currently document a native Authorize.net connection. Agencies should verify current compatibility directly with WeTravel before selecting their payment stack.
Sometimes. Stripe currently lists travel reservation services and clubs as restricted businesses requiring additional due diligence. It separately prohibits certain travel categories. Eligibility depends on the exact business model, jurisdiction and Stripe service, and approval may be modified or revoked under Stripe’s terms.
Not by itself. Authorize.net is primarily a gateway and payment platform. A travel agency still needs a compatible processing and acquiring relationship that has approved its business model, MCC, volume, ticket size and future-delivery exposure.
The agency can generate an order-specific hosted checkout tied to the traveler, itinerary, amount and accepted terms. The customer enters the card information directly into the secure payment form. If the agency needs MOTO or virtual-terminal transactions, that channel should be disclosed and approved separately.
