Hotels, Motels & Resorts.
Lodging, hotels, motels and resorts (not in 3500–3999).
- MCC
- 7011
- Category
- Business Services
- Cardflo support
- Yes
What MCC 7011 covers
Merchant Category Code 7011 is the ISO 18245 identifier used by the card networks for hotels, motels & resorts. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
Lodging, hotels, motels and resorts (not in 3500–3999). Choosing the right MCC is critical: an incorrect code can lead to higher interchange, surcharges, or, in regulated categories, declined transactions and account holds.
Merchants in MCC 7011 include hotels, motels, resorts, and other lodging establishments. Transactions typically have moderate to high ticket sizes, corresponding to room nights, and can include ancillary services like dining or spa treatments.
Frequency varies, with some customers making infrequent, high-value bookings while business travellers may have higher frequency.
Chargebacks are frequently related to 'services not rendered' (e. g. , guest no-show charged anyway), 'cancelled recurring transaction' for subscription-like memberships, or 'credit not processed' for legitimate refunds. Fraud is also a concern, particularly for online bookings made with stolen card details.
Schemes often have specific rules for the travel industry, focusing on no-shows and cancellations.
Visa and Mastercard both have specific parameters for travel-related chargebacks. Cardflo's chargeback defence tools, combined with robust fraud screening calibrated for common hotelian patterns, can help manage disputes effectively.
Our support for tokenisation and EMV 3D Secure can reduce fraud-related chargebacks while maintaining a good customer experience.
Hoteliers should optimise payment acceptance for both pre-paid and post-stay charges, leveraging card-on-file tokenisation for seamless ancillary billing. Implement robust 3DS2 for CNP bookings to reduce fraud liability shifts.
Given advance booking patterns, ensure your payment gateway supports delayed capture and incremental authorisations for incidentals. For no-shows, clearly display cancellation policies at booking and point-of-sale terminals.
Consider a multi-acquiring setup to diversify risk and optimise processing costs across different booking channels, particularly for international guests where FX fees can be significant. Maintain a vigilant approach to chargeback monitoring, especially for 'service not rendered' claims.
Acquirer and acquirer assessment stance.
Medium-risk standard board, potentially low-risk for established chains with good processing history. Some acquirers may require a transactional reserve for new or smaller merchants given the seasonal nature and potential for advance bookings.
Expect 0-5% reserve held for up to 180 days, especially if advance bookings represent a significant portion of revenue.
Dispute and chargeback profile.
The primary cause for disputes here is 13.1 / 4853 (services not as described) or 13.4 / 4808 (realise debit/credit). This arises when guests dispute room conditions, unapproved charges, or valid refunds aren't processed.
For 'services not described', retain detailed records of bookings, room allocation, and any guest complaints or resolutions. For 'no-show' charges (often under 13.4), supply booking confirmations, cancellation policies, and proof of attempts to contact the guest.
Evidence of check-in/out and incidental charge sign-offs are critical for disputing unrecognised transactions (10.4 / 4837).
See also: chargeback management · payment response codes · Compelling Evidence 3.0.
Book a scoping call to see how Cardflo would set you up.
How Cardflo handles MCC 7011
- Placement with acquirers that actively board MCC 7011 businesses in your region.
- B2B card-not-present processing with Level 2 and Level 3 data support.
- Virtual-card, AP-automation and procurement-card acceptance.
- Invoice-linked payment flows and pay by link options for receivables teams.
- Settlement and reconciliation that maps cleanly to ERP and accounting systems.
- Dedicated onboarding manager experienced with B2B and corporate merchants.
Payment methods typically enabled.
Onboarding checklist.
What acquirers typically ask to see when boarding MCC 7011. Cardflo collects this once and reuses it across every acquirer we route you through.
- Business registration and beneficial-owner documentation (KYB, UBO).
- Six months of processing statements or bank statements demonstrating B2B volume.
- Standard master services agreement or engagement letter template.
- Level 2 / Level 3 data capability evidence for commercial-card processing.
- Refund, cancellation and dispute-handling policy for recurring or retainer billing.
- Chargeback ratio and dispute history covering the last six months, including any Visa or Mastercard monitoring-programme status.
See also: Know Your Customer (KYC) · high-risk merchant · smart routing.
Talk to an acquiring specialist about your MID setup.
Common questions
How can hotels in MCC 7011 best manage 'no-show' chargebacks?
No-show chargebacks (often filed as 'services not rendered') can be mitigated by clearly communicating cancellation policies at the time of booking and again in confirmation emails. Hotels should also secure an authorisation for the full stay or at least the first night's rate upon booking.
If a guest is charged for a no-show, comprehensive documentation of the booking, the cancellation policy accepted by the cardholder, and attempts to contact the guest serves as strong compelling evidence for representment. Ensuring a guest check-in/out system that records details accurately is also vital.
Are there specific Visa or Mastercard rules regarding pre-authorisations for hotel bookings?
Yes, both Visa and Mastercard have specific rules. For hotels, it's common practice to perform an authorisation hold (pre-authorisation) for the estimated cost of the stay plus an incidental amount.
This hold must be released promptly if the guest does not stay or pays by another method. Improperly managed authorisations, particularly if they convert to a sale after a guest paid another way, can lead to 'credit not processed' or 'transaction not recognised' chargebacks.
Visa mandates that final authorisation matching be completed within 7 days of checkout for chip or online transactions, and 31 days for magnetic stripe or manual imprint.
What role does 3D Secure play in reducing fraud for online hotel bookings?
3D Secure (3DS) is crucial for online hotel bookings. Implementing 3DS shifts liability for fraud-related chargebacks from the merchant to the card issuer, provided the transaction was successfully authenticated.
This is particularly valuable for high-value bookings which are often targets for fraudsters. Cardflo's payment orchestration can ensure 3DS is optimally deployed, including strategic exemptions where appropriate to balance security and customer convenience, reducing friction for legitimate customers while protecting against fraud.
How can hotels best protect themselves from chargebacks related to 'no-shows' where the guest claims they cancelled?
To defend against 'no-show' chargebacks, hotels must have clear, accessible cancellation policies displayed prominently during the booking process, in confirmation emails, and at reception.
When processing a no-show fee, retain detailed records including the original booking confirmation, evidence of the cancellation policy presented to the customer, and a timestamped record of the guest's failure to arrive or cancel within the stipulated period.
If possible, record any customer communication regarding the booking. For pre-paid bookings, ensure the charge is captured on the expected check-in date, not earlier, to align with service delivery and reduce 'service not rendered' claims.
What payment processing strategies can reduce fraud for online hotel bookings made with stolen card details?
For CNP online hotel bookings, implement strong fraud scrutiny. Mandate 3DS2 for all online transactions, especially for higher value bookings, to shift liability for fraud to the issuer.
Utilise advanced fraud detection tools that analyse IP addresses, device fingerprints, and booking patterns (e. g. , multiple bookings from a single IP to different names).
For last-minute bookings or those originating from high-risk countries, consider requiring the guest to present the physical card used for booking and a matching photo ID at check-in.
Tokenise card details securely for future payments, rather than storing raw card data, to enhance PCI DSS compliance and reduce data breach risk.
Other MCCs in Business Services
Related industries.
Related features.
Related guides.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.