What is the best payment processor for a small independent hotel in Europe?

For EU hotels under €10,000/month in card volume, Stripe is often the most practical starting point: transparent published pricing, excellent API integration, and no monthly minimums. For higher-volume properties or those with complex OTA VCC workflows, Adyen's interchange-plus model typically produces lower effective rates. Elavon is worth evaluating for hotels with Cloudbeds or Oracle OPERA integrations already in place. Square suits micro-hotels and B&Bs with primarily card-present transactions and minimal OTA volume.

How much more do hotels pay to process OTA virtual credit cards than direct bookings?

Substantially more. EU interchange caps apply to consumer credit cards (0.3%), but VCCs issued by Booking.com and Expedia are classified as commercial cards, which are uncapped. Average VCC interchange in Europe runs 1.5-1.8%, compared to 0.3% for EU consumer credit cards. Outside the EU, VCC interchange is typically 2.5-3%. A direct booking processed through Stripe costs roughly 1.6-1.9% in EU markets. An OTA VCC transaction with the same processor costs 2.5-3.5% in fees, on top of the 15-18% OTA commission already paid.

What is Adyen's pricing for hotels and how does interchange-plus work?

Adyen uses interchange-plus-plus (IC++) pricing: you pay the actual interchange fee set by Visa or Mastercard, plus scheme fees, plus Adyen's processing markup (starting at approximately 0.6% plus €0.10 per transaction, decreasing with volume). This produces full transparency on cost components. Adyen requires monthly minimum processing fees (typically €100+), making it less suitable for small hotels with low monthly card volume. For properties processing €30,000+ per month, the IC++ model typically results in lower blended rates than flat-rate alternatives.

How can hotels win no-show chargeback disputes?

The winning evidence set for a no-show chargeback includes: the original booking confirmation showing the cancellation/no-show policy in clear language, evidence the guest acknowledged the policy at the time of booking (checkbox, digital signature, or explicit confirmation), proof the room was held and not re-sold, and documentation of any contact attempt. Hotels that use pre-authorization rather than immediate charge at booking typically have fewer no-show disputes, because the authorization flow makes policy acknowledgment a natural part of the booking flow.

Does Stripe work well for hotel payment processing?

Stripe works well for hotel direct bookings through website booking engines. The published EU rate (1.4% + €0.25 for consumer cards) is competitive, the API integration quality is excellent, and on-domain payment capture via Stripe.js avoids the redirect that causes conversion drop. The limitations are the 1.5% international card surcharge (significant for hotels with substantial US or UK guests), no hotel-specific interchange optimization, and limited native automation for OTA VCC workflows. For straightforward direct booking payment without complex OTA reconciliation needs, Stripe is a strong choice.

What is a chargeback and how much does it cost a hotel?

A chargeback is when a guest disputes a charge with their bank, and the bank reverses the payment from the hotel's account pending resolution. The hotel pays a dispute fee (typically €15-100 per case) whether it wins or loses. According to Chargebacks911, the average total cost of a hotel chargeback is €190-200, including the disputed amount, processor fee, and staff time spent on documentation. Hotels with chargeback rates above 1% of transactions risk processor account termination and higher fee tiers.

How do cross-border card fees affect hotel payment processing costs?

EU interchange caps (0.3% for credit cards) apply only to cards issued within the EU. Cards from the US, UK (post-Brexit), or other non-EU countries carry higher interchange rates, typically 1.5-2.1% in the hotel category. Most processors also add a cross-border surcharge (Stripe charges 1.5%; Adyen applies IC++ on cross-border transactions; some add a currency conversion fee of 1% if settlement currency differs). A hotel with 30% international guests can see an effective blended rate 0.5-1% higher than a hotel with the same volume but predominantly EU domestic guests.

Hotel Payment Processor Comparison 2026 (Independent)

A 44-room boutique in Valencia paid 3.4% on every card transaction for three years. A 45-minute analysis of their actual card mix (73% Visa/Mastercard EU, 18% international, 9% Amex) showed they were overpaying roughly €11,800 per year. The processor hadn’t been renegotiated since the hotel opened in 2019. The card mix had shifted substantially as international bookings grew. The rate hadn’t.

This is more common than hotel operators realize. Payment processing looks like a fixed cost. It isn’t. The fee you pay today reflects a negotiation (or its absence) that happened at a specific moment, priced against a volume and card mix that probably no longer matches your actual business.

For independent hotels in the 20-80 room range, the five processors that come up most often in evaluations are Stripe, Adyen, Worldpay (FIS), Elavon, and Square. Each has a genuinely different structure. This guide compares them with specific numbers so you can evaluate your current arrangement against real alternatives. For the broader context of how payment decisions fit into your direct booking economics, the guide to hotel direct booking strategies and OTA fee reduction covers channel mix and why processor choice affects your net revenue per booking.

What You Actually Pay When a Guest Books with a Card

The fee on your monthly statement is a composite. Breaking it apart matters because the components are negotiable at different layers.

Interchange fee. Set by Visa or Mastercard. Goes to the card-issuing bank. Not negotiable with your processor. For EU consumer credit cards, capped at 0.3% under EU regulation. For non-EU cards and commercial/corporate cards, interchange is higher and uncapped. According to Visa’s published interchange schedule, hotel-category transactions for card-present bookings can qualify for preferential rates when proper lodging data is transmitted (check-in/check-out dates, folio details).

Scheme fee. Charged by the card network itself (Visa, Mastercard). Small (typically 0.05-0.15%) but unavoidable.

Processor markup. This is the part you negotiate. Either a flat percentage added to interchange (interchange-plus pricing) or a blended rate that bundles all three components together (flat-rate pricing).

Monthly fees. Some processors charge a monthly platform or account fee regardless of volume.

Per-transaction fee. A fixed amount per authorization (typically €0.05-€0.30).

Cross-border surcharge. Applied when the card is issued outside your account’s country. Stripe adds 1.5% for international cards. Adyen applies interchange-plus on cross-border transactions. This single line can significantly inflate effective rates for hotels with substantial international guest mixes.

Chargeback fee. Per dispute, not per outcome. Whether you win or lose the chargeback, you typically pay €15-100 per case.

According to Sertifi’s hotel payment processing guide, hotels typically see total processing costs of 2.0-3.5% when all fees are included. The spread between best and worst outcomes within that range is large enough to matter.

The Five Processors Small Hotels Should Compare

Stripe

Stripe publishes its pricing clearly: EU-issued consumer cards cost 1.4% + €0.25 per transaction. Non-EU or commercial cards add 1.5% on top, making an international transaction 2.9% + €0.25. Currency conversion adds another 1%.

For a hotel with a predominantly European domestic guest mix, Stripe’s effective blended rate is typically 1.6-1.9%. For a property in Barcelona with 35% US and UK guests, the blended effective rate climbs closer to 2.4-2.7%.

Stripe’s integration quality is excellent. It connects cleanly with most modern booking engines and PMS platforms via API. The payment experience is fully on-domain with Stripe’s JavaScript library, avoiding the redirect that kills conversion. Stripe also handles 3D Secure authentication automatically, which matters for European transactions since PSD2 compliance requires it.

The main limitation for hotels is that Stripe treats hospitality like any other e-commerce vertical. There’s no lodging-specific data transmission that could qualify transactions for lower interchange tiers. This isn’t unique to Stripe, but processors with hospitality-specific configurations (Elavon, Worldpay) can sometimes achieve lower effective interchange on hotel transactions.

Adyen

Adyen uses interchange-plus-plus (IC++) pricing: you pay actual interchange, plus scheme fees, plus Adyen’s processing markup. The markup starts at approximately 0.60% per transaction plus €0.10, though this decreases with volume. Monthly minimum fees apply (typically €100+ per month in processing fees, which at low volume can make Adyen expensive).

The average total blended rate for European consumer card transactions through Adyen sits around 1.5-2.0%, with the precise figure depending entirely on your card mix. Higher international volume pushes this up.

Where Adyen is strong: it handles VCC transactions from OTAs without special configuration, supports a wide range of local payment methods (iDEAL, SEPA, Bancontact), and has native integrations with enterprise PMS platforms including Oracle OPERA, Mews, and Stayntouch. For a hotel processing meaningful volume (above €30,000/month in card payments), Adyen’s interchange-plus structure typically produces better outcomes than flat-rate pricing.

Adyen is not ideal for very small properties. The monthly minimums and setup complexity favor properties that can absorb the initial configuration investment.

Worldpay (FIS)

Worldpay (owned by FIS) is the enterprise-oriented option. Pricing is not publicly listed; you request a quote. The structure is interchange-plus, with markups negotiated based on volume, business type, and contract length.

The standard contract is three years. Early termination fees run €295-495. Worldpay has a substantial number of documented complaints about fee transparency: rates quoted during sales discussions that don’t match what appears on statements, and monthly fees that weren’t explicitly disclosed. Hotel Tech Report’s Worldpay reviews reflect this pattern.

For hotels, Worldpay’s advantage is breadth of PMS integration and the ability to support lodging-specific data fields that qualify transactions for lower interchange categories. For a 60-room property already using a PMS with native Worldpay integration, the specialization may justify the complexity. For a 25-room property evaluating processors for the first time, the contract terms and transparency issues make Worldpay a harder starting point.

If you engage Worldpay, get every fee in writing before signing: monthly platform fee, batch settlement fee, compliance fee, chargeback fee, and early termination fee. The published rate is rarely the total rate.

Elavon

Elavon is a US Bank subsidiary and one of the top eight payment acquirers in Europe. It has a dedicated hospitality division with hotel-specific configurations, including support for authorization-and-capture workflows, lodging data transmission for interchange qualification, and direct PMS integrations.

Pricing is bespoke: you don’t find public rates. For EU hotels, effective total rates typically run 1.6-2.2% depending on card mix and volume. Elavon’s bank backing (US Bank) means stronger financial stability than some fintech processors, and its hospitality unit understands hotel-specific workflows including VCC processing from OTAs.

Elavon operates in 30+ countries. For hotels with European operations and meaningful cross-border card volume, Elavon’s regional acquirer relationships can reduce scheme fees on local transactions that a US-based processor would treat as international.

The integration story is solid: Elavon works with Cloudbeds, Oracle OPERA, and proprietary hotel systems through its Converge platform. If your PMS has a native Elavon integration, the setup is substantially simpler than connecting a generic processor via API.

Square

Square offers the simplest structure: flat rate, no monthly minimums, no contract lock-in. In Europe, Square charges 1.75% for chip-and-PIN and contactless transactions (card present). Online or card-not-present transactions run 2.5%. Processing above £200,000 annually qualifies for custom pricing discussions.

Square does not add explicit cross-border surcharges on its published European rates, though the flat rate already prices in an average. For micro-hotels, guesthouses, and short-term rental operators processing under €5,000 monthly in card payments, Square’s simplicity is genuinely valuable. There are no contracts, no setup fees, and the hardware is inexpensive.

For hotels above that volume threshold, Square’s flat rates become expensive compared to interchange-plus alternatives. A hotel processing €20,000/month would pay €350/month at Square’s 1.75% card-present rate. A comparable Adyen setup at 1.5% effective rate costs €300. The difference is €600/year. At higher volume, the gap widens.

Square’s PMS integrations are limited compared to specialist processors. It works well as a standalone solution or with basic booking tools, but doesn’t support the lodging-specific data fields that can reduce interchange on hotel transactions.

Processor Comparison Table

Processor	EU card rate	Intl surcharge	Chargeback fee	Monthly minimum	Hospitality PMS integrations
Stripe	1.4% + €0.25	+1.5%	~€15	None	Via API; most booking engines
Adyen	~0.6% + €0.10 markup (IC++)	IC++ on cross-border	~€20-35	~€100 processing fees	Oracle OPERA, Mews, Stayntouch
Worldpay	Negotiated (IC+)	Negotiated	~€25-50	Varies by contract	Broad; PMS-specific integrations
Elavon	Bespoke (IC+)	Regional acquirer	~€20-40	Bespoke	Cloudbeds, Oracle OPERA, Converge
Square	1.75% (card present)	Blended in flat rate	~€15-25	None	Limited; basic booking tools

How Do OTA Virtual Cards Change Your Actual Fee Reality?

OTA virtual credit cards (VCCs) are single-use cards issued by Booking.com, Expedia, or other OTAs to pay hotels after a guest stay. The hotel charges the VCC rather than receiving a bank transfer. This model exists because it gives OTAs control over payment timing and fraud liability.

The problem: VCC transactions are categorized as commercial card payments, not consumer card payments. EU interchange caps apply to consumer cards (0.3% for credit). Corporate and commercial cards are uncapped. According to Katanox’s analysis of VCC payment methods, interchange fees on VCC transactions average 1.5-1.8% in Europe, compared to 0.3% for consumer credit cards. Outside the EU, VCC interchange rates are typically 2.5-3%.

The implication for a hotel with 40% OTA share (common for independent properties): roughly 40% of your card volume is being processed at commercial-card interchange rates, not consumer rates. If your processor is quoting you a blended effective rate without separating VCC transactions, you’re not seeing the real cost distribution.

The processor comparison for VCC matters: Adyen and Elavon have VCC-specific workflows that streamline charging and reconciliation. Stripe treats VCCs like any commercial card (functional but not specialized). Square can process VCCs but lacks the automation for high-volume OTA reconciliation.

For hotels where OTA VCC volume is substantial, the net payment economics of a direct booking versus an OTA booking aren’t just about OTA commission. A direct booking on a Stripe integration costs you roughly 1.6% in processing. An OTA booking through Booking.com costs you the OTA commission (typically 15-18%) plus 2.5-3% in VCC processing fees. The total OTA cost for a €200 room night is €35-42 in combined fees. The processing economics strongly favor direct bookings, which is a useful way to frame the processor decision alongside your booking engine evaluation for direct reservations.

Chargebacks for Hotels: The Quietly Expensive Category

The naive approach to chargebacks is treating them as the processor’s problem. This fails when an authorized-but-later-disputed no-show charge at €280 costs you €305 with the chargeback fee on top, and you’ve also lost the room revenue because the room sat empty. The working pattern is pre-authorization at booking confirmation, capture at checkout, with no-show terms stated explicitly in the booking confirmation email and guest signature captured if possible.

According to Chargebacks911’s hotel chargeback guide, the average total cost of a hotel chargeback runs €190-200 when you include the disputed amount, the processor’s dispute fee (typically €15-100), and internal staff time spent gathering documentation. A disputed no-show at €200 becomes a €320-420 total cost when you factor in the processing fee and lost-room cost.

No-show chargebacks specifically are winnable. The winning evidence set is: (1) booking confirmation with cancellation policy stated explicitly, (2) no-show terms acknowledged by the guest at booking (checkbox or signature), (3) record showing the room was held and not re-sold, (4) failed contact attempt documentation if applicable.

Hotels that use pre-authorization rather than immediate charge see fewer chargebacks on no-show disputes. A held authorization signals clear intent without triggering the “I was charged for something I didn’t receive” dispute framing. Pre-authorization holds typically release within 7 days if not captured; some processors and card networks extend this with hotel-category authorization codes. This connects to experience from Guestivo customer data: automated pre-arrival payment authorization reduced no-show rates from approximately 7% to 3% at a mid-market property, which also reduced the volume of chargeback disputes to process.

Processor choice affects chargeback resolution. Adyen and Elavon have dedicated chargeback management tools and pre-built response workflows. Stripe provides dispute management through the dashboard but without hospitality-specific templates. Worldpay’s chargeback process has been criticized for response times. Square’s dispute process is functional but designed for retail, not hotel-specific no-show or authorization disputes.

Cross-Border Cards: Why a Barcelona Hotel with US Guests Pays More

A Barcelona hotel that processes 30% US Mastercard transactions is paying full interchange on those cards, because EU interchange caps apply only to cards issued within the EU. US consumer credit cards carry interchange of roughly 1.5-2% (varies by card tier). A standard Visa Signature or World Mastercard from the US has interchange around 2.1% in the hotel category.

Additionally, if your processor account is in EUR and the US guest’s card is billed in USD, a currency conversion fee applies on top (typically 1%). On a €250 transaction from a US card: €250 x (2.1% interchange + 0.1% scheme + 0.6% processor markup + 1% conversion) = approximately €9.50 in processing fees, or 3.8% effective rate.

The negotiable element here is the processor markup and, for higher-volume properties, the currency conversion arrangement. Some processors offer net settlement in multiple currencies, which can reduce currency conversion costs if you have meaningful multi-currency volume. Elavon’s regional acquirer relationships in Europe can sometimes achieve lower effective cross-border rates than US-based processors. Adyen’s IC++ model makes the cross-border cost fully visible by breaking it into components.

For hotels with a high international guest mix, asking processors to break down your card-mix cost estimate is valuable before signing. A quote built on your actual last-three-months card mix (which your current processor can provide) is more useful than a headline rate.

PMS and Booking Engine Integration: What Actually Matters

Payment integration quality is not uniform across processors. The key variables:

Authorization and capture vs immediate charge. Hotels need pre-authorization (hold) at booking and capture at checkout. Not every booking engine supports this correctly with every processor. Confirm the flow before committing.

Redirect vs on-domain payment. A redirect to a third-party payment page causes conversion drop. Hotelchamp research found two-thirds of US travelers become apprehensive when redirected to an unfamiliar portal. Stripe’s JS library, Adyen’s Drop-in, and Elavon’s Converge all support on-domain card capture.

Tokenization for repeat guests. Storing a card token for returning guests (for deposits, upgrades, incidental charges) requires PCI-compliant tokenization. Stripe, Adyen, and Elavon all support this. Square does in basic form. The token must persist across stays, which requires PMS-level storage, not just processor-level.

OTA VCC automation. Manually charging VCCs is time-consuming at scale. Adyen, Elavon, and some Worldpay configurations support automated VCC charging triggered by check-out events in the PMS. Stripe requires custom development for this workflow.

For properties using Cloudbeds, Little Hotelier, or Mews, check native processor integrations first. Native integrations handle lodging data fields automatically, which matters for interchange qualification. Third-party API connections often don’t transmit the full lodging dataset, costing you interchange optimization.

A Practical Switch Evaluation for a 40-Room Property

Switching payment processors is not trivial. Tokenized card data held by your current processor may not be transferable. PMS integrations need reconfiguration. Staff need retraining on new settlement reports. A structured three-phase approach reduces the risk.

Phase	Timeline	Key Actions	Expected Outcome
Audit current costs	Weeks 1-2	Pull last 3 months of statements. Calculate effective rate by card type (domestic consumer, intl consumer, commercial/VCC). Identify your card mix percentage. Compare to processor benchmarks.	Precise current cost baseline; identify if you’re paying above market
Shortlist 2 processors	Weeks 3-5	Request interchange-plus quotes from 2 candidates. Ask for cost estimates built on your actual card mix (not a generic rate). Confirm PMS integration depth. Check tokenization portability.	2 specific alternatives with apples-to-apples cost projections
90-day pilot	Weeks 6-20	Run new processor on one channel (e.g., direct bookings only). Compare effective rates against baseline. Monitor chargeback resolution speed. Track VCC processing time if applicable. Evaluate at 90 days before full switch.	Evidence-based decision on whether to complete the switch

The audit phase is the most valuable regardless of outcome. Many hotels discover they’re on a plan that made sense at low volume and was never renegotiated as the business grew. Even without switching, the audit often reveals the ability to renegotiate with the current processor.

For context on technology stack evaluation more broadly, the boutique hotel technology guide for 2025 covers how payment processing fits alongside PMS, booking engine, and channel manager in the full independent hotel technology budget.

FAQ

The Practical Takeaway

Most small hotels haven’t renegotiated their payment processor since they opened. The first thing to do is read last month’s statement line by line, not read a comparison article.

That said: the five-processor comparison above gives you the framework to evaluate whether you’re being fairly priced. If your current effective rate is above 2.5% and your guest mix is predominantly EU domestic, something in your pricing structure doesn’t match your actual card mix. If you’re processing OTA VCCs at the same rate as direct consumer card bookings, you’re not seeing the real cost breakdown.

Payment processing is not a fixed overhead. It’s a negotiated cost with meaningful room to optimize, usually without switching processors at all.