3812 Hyatt place

Introduction

• What it is: This MCC code covers lodging services provided by hotels and motels, specifically those branded as Hyatt Place.
• Risk level: Medium — Typically associated with higher transaction volumes and potential cancellations.
• Acceptance difficulty: Medium — Some networks may require additional checks due to the nature of the business.
• Typical business models: Hotels; motels; extended stay lodging; boutique hotels; hospitality chains.
• For merchants: Moderate MDR rates; potential for reserve requirements; clear cancellation policies may be necessary.
• What PSPs expect: Business registration; proof of legitimacy via hotel classification; detailed description of services offered.

Payment Insights & Benchmarks

Merchants in this MCC should prepare for diverse payment dynamics influenced by customer preferences and the hospitality industry's unique challenges. Understanding these payment insights will help businesses manage costs and improve transaction experiences.

Payment methods

Cards: widely accepted, though international cards may experience varying approval rates.

• E-wallets: increasingly popular for customer convenience, particularly for loyalty program integration.
• Mobile payments: often favored for quick check-ins and checkout processes.
• Corporate accounts: prevalent in business travel, which may entail additional authentication.

Authentication & security

Strong customer authentication (SCA) protocols may be required, especially for international transactions.

• 3DS may see varied implementation, impacting user experience and conversion rates.
• Fraud detection systems must account for unique transaction patterns typical in the hospitality sector.

Benchmarks (indicative, not guaranteed)

MDR: typically higher than standard e-commerce, reflecting industry risk.

• Rolling reserves: may be required, commonly in the range of 5-10%.
• Settlement delays: frequently longer due to manual reconciliation processes (7+ days).
• Chargeback ratios: often higher than e-commerce averages due to booking cancellations.
• Approval rates: generally lower for international cards compared to domestic.

Key metrics to monitor

Authorization rates segmented by payment method and origin.

• Chargeback ratios categorized by type (e.g., fraud, customer service).
• Customer payment preferences and trends over time.
• Average transaction values to identify high-risk periods.

Risk & Compliance

Merchants under the MCC 3812 (HYATT PLACE) face unique risks that can impact their financial integrity and reputation. Due to the nature of hospitality and travel transactions, both payment service providers (PSPs) and acquirers implement rigorous scrutiny, compelling merchants to proactively manage potential chargebacks, fraud, and compliance with AML/KYC requirements.

Chargebacks & fraud

Commonly encounter friendly fraud (e.g., guests disputing legitimate charges) and reservation manipulation (fraudulent bookings using stolen credit cards).

• Increased risk of chargebacks during high-demand periods, such as holidays or special events, as guests may escalate disputes due to dissatisfaction.
• Mitigation tools include transaction monitoring systems, fraud detection algorithms, and customer identification verification methods.

AML/KYC expectations

Robust identity verification processes must be in place, including thorough checks for identity documents and customer background.

• Mandatory sanctions checks and ongoing monitoring for high-risk transactions, particularly with international guests.
• Manual review is triggered by unusual booking patterns, such as multiple reservations from the same IP address or unusually high-value transactions.

Operational red flags

Lack of transparency regarding ownership of booking platforms or unclear operator details, which can raise suspicion among PSPs.

• Inconsistencies in guest information, such as varying names or email addresses for bookings, suggesting potential fraud.
• Absence of clear cancellation or refund policies, leading to poor customer experiences that can result in chargebacks.
• High volumes of last-minute cancellations or no-shows, which can indicate potential fraudulent activity.

Onboarding Checklist

Merchants under this MCC should prepare a complete onboarding package before approaching PSPs or acquirers. A well-structured submission improves approval chances and shortens review times.

Legal & corporate documents

company registration and incorporation documents

• disclosure of beneficial owners (UBO) and corporate structure
• valid licenses for the relevant business activities
• policies: Terms of Service, Privacy, AML/KYC, Refund Policy

Financials & risk management

recent financial statements and cashflow forecasts

• liquidity or reserve model for managing customer transactions
• description of antifraud setup and monitoring tools

Product & marketing

demo access or screenshots of the live platform

• marketing plan and traffic source overview, including partners or affiliates
• geographic targeting information
• KYC flow details, including identity verification providers and thresholds

Technical integration & security

payment architecture overview with supported methods and providers

• description of SCA/3DS flows, including any retry logic and tokenization methods
• PCI DSS compliance status and data storage policies

Operations

customer support setup, including languages spoken and availability

• SLA for dispute handling and chargeback response
• deposit, transaction, and payout limits; any self-exclusion options

Regulation & Licensing

Licensing and certification are critical for merchants in this MCC, as PSPs and acquirers will require proof of compliance before onboarding. Recognition of licenses depends heavily on the merchant’s jurisdiction and the markets they target.

Operator licenses

Hotel and lodging licenses (varies by region) — typically required for operation; recognition varies based on state or national regulations.

• Health and safety permits — often mandated to ensure compliance with local standards; crucial for maintaining operational licenses.
• Fire safety inspection certifications — necessary for guest safety and often required by local authorities; their acceptance may be jurisdiction-specific.
• Business licenses — standard requirement for all commercial operations; relevance and enforcement depend on local laws.

Geo-restrictions

Specific cities may have heightened regulations or restrictions on hotel operations, impacting merchant onboarding by PSPs.

• Some jurisdictions may impose limits on room capacity or operational hours, which could affect service offerings.
• Regions with stringent zoning laws might restrict new lodging establishments or require special permits.

Certifications & audits

PCI DSS compliance is essential when handling payment card data to ensure secure transactions.

• Regular health and safety audits to comply with local regulations and ensure guest safety.
• Environmental sustainability certifications may be requested by some consumers or platforms.
• Annual reviews for compliance with local hospitality regulations and fire safety standards.

Official Definitions & Network Comparisons

This section shows how major card networks define this MCC and highlights practical differences that affect merchant onboarding.

Explanation:

While each network defines this MCC in a related manner, differences in terminology such as "members' clubs" versus "fraternal organizations" can affect how businesses are categorized. Some networks may require unique licenses or additional documentation for certain types of memberships. Common denial reasons include failure to provide valid documentation, risks associated with specific geographic locations, and a lack of clarity regarding membership services offered.

Alternative MCC Codes

Merchants often confuse this MCC with other categories. The table below shows which codes are related, why they are confused, and what risks misclassification brings.

Rule of thumb for merchants:

If your business primarily involves providing overnight accommodations, make sure to use MCC 3812. Misclassifying as another code can lead to compliance issues or payment processing difficulties, especially if your offerings do not align with the selected MCC.

Best Practices for Merchants

Merchants operating under the MCC 3812 should prioritize payment processing efficiency and risk management to maintain positive relationships with payment service providers (PSPs) and ensure smooth transactions. The following best practices are essential for optimizing operations and minimizing disputes.

Classification & transparency

always use the correct MCC for all transactions to avoid potential account issues

• clearly present licensing information, operational policies, and any geographic restrictions on your website
• ensure that all billing descriptors are transparent and easy for customers to understand

Fraud & chargeback reduction

implement 3DS or step-up authentication for transactions flagged with high-risk indicators (e.g., large amounts, unusual locations)

• provide clear and concise billing descriptors, immediate transaction confirmations, and responsive customer support to resolve issues proactively
• maintain detailed event logs to substantiate transactions during dispute representments

Payment acceptance optimization

support a variety of payment methods (cards, wallets, mobile payments) to enhance customer convenience and reduce reliance on a single payment option

• optimize routing of transactions based on geographic location, bank networks, or specific payment providers, and conduct A/B testing to identify the best performing setups
• consider setting up separate merchant IDs (MIDs) for different product categories or regions to better manage compliance and risks

Operational discipline

track key performance indicators (KPIs) such as transaction approval rates, decline codes, chargeback ratios, and customer lifetime value (LTV)

• regularly conduct compliance audits and update internal procedures to align with industry standards and best practices
• establish a dedicated team or individual responsible for managing disputes, emphasizing timely responses and resolution strategies

Payouts & liquidity

maintain adequate liquidity buffers to manage rolling reserves and potential extended settlement periods

• implement automated anti-money laundering (AML) checks for withdrawals, particularly when transactions exceed threshold limits
• monitor payout trends and be vigilant for unusual withdrawal patterns that may indicate risks or fraud

Business Scope & Examples

This MCC covers businesses involved in the operation of hotels and lodging facilities. Merchants classified under this category typically provide services where customers make payments for overnight stays and related accommodations. The scope is broad and focuses on businesses that offer temporary lodging, whether through traditional hotels or alternative accommodations.

Models

full-service hotels (luxury and mid-range)

• motels and budget accommodations
• extended stay hotels with kitchen facilities
• bed and breakfast establishments
• vacation rentals (e.g., Airbnb)

Borderline cases

Hostels — budget accommodations often targeting younger travelers; may sometimes fall under this MCC depending on the services offered.

• Vacation package services — companies that bundle lodging with travel arrangements; may not fit if the focus isn't on direct accommodation sales.
• Short-term rental platforms — platforms that facilitate peer-to-peer rental of homes; should clarify whether they focus on overnight lodging.

Signals for correct classification

primary service involves overnight stays for guests

• charges are generally based on a per-night fee structure
• ancillary services (e.g., room service, cleaning) cater specifically to lodging clients