7511 Reserved for national use

Introduction

• What it is: This MCC is designated for specific national purposes and is not widely applicable to standard merchant categories.
• Risk level: Medium — Limited business models may increase scrutiny.
• Acceptance difficulty: High — Due to its specialized nature, acceptance might be challenging with some payment processors.
• Typical business models: National vehicle rental agencies; government-related transportation services; specialized leasing companies.
• For merchants: May face higher MDR; potential for reserve requirements; subject to thorough evaluation by PSPs.
• What PSPs expect: Detailed business plan; compliance documentation; clear identification of services offered.

Payment Insights & Benchmarks

Merchants in this MCC should plan for unique challenges when it comes to payment processing, primarily due to specific restrictions and limitations often associated with national use. This may affect acceptance rates and transaction costs.

Payment methods

Cards: acceptance may be limited, leading to lower approval rates and higher declines in certain regions.

• E-wallets: prevalent for convenience, but may have varying acceptance depending on the service provider.
• Bank transfers: commonly used, but processing times can vary significantly.
• Vouchers and prepaid cards: offer privacy and are often utilized for risk mitigation.

Authentication & security

Strong customer authentication (SCA) requirements can complicate the checkout process.

• 3DS is frequently implemented to combat fraud, but may lead to increased cart abandonment.
• Ongoing fraud monitoring is essential, focusing on behavioral analytics and transaction patterns.

Benchmarks (indicative, not guaranteed)

MDR: generally elevated compared to standard e-commerce categories.

• Rolling reserves: may be implemented, potentially impacting cash flow.
• Settlement time: often longer than average, sometimes extending beyond a week.
• Chargeback ratios: can be higher, particularly in regions with loose consumer protection laws.
• Approval rates: typically lower due to restrictive processing policies.

Key metrics to monitor

Authorization rates split by transaction type and payment method.

• Chargeback incidence rates and their reasons for analysis.
• Average transaction volumes and trends to forecast cash flow.
• Decline reasons to refine approval strategies and merchant practices.

Risk & Compliance

Merchants categorized under this MCC face unique challenges and risks, particularly due to the potential for regulatory scrutiny and the ambiguity surrounding permitted transactions. PSPs and acquirers implement robust risk management practices to ensure compliance and mitigate financial crime risks associated with these transactions.

Chargebacks & fraud

Frequent instances of friendly fraud where genuine transactions are disputed, possibly due to confusion regarding service provisions.

• Potential for unauthorized use of payment information, leading to chargebacks from customers who claim non-delivery or misrepresentation.
• Common mitigation tools include transaction alerts, customer verification processes, and chargeback alerts to monitor dispute activity.

AML/KYC expectations

Comprehensive identity verification processes (IDV) are a must, including validation of personal identification documents.

• Mandatory checks against sanctions lists and politically exposed persons (PEP) to ensure that transaction parties are vetted appropriately.
• Manual reviews are often triggered by unusual transaction patterns or high-risk flags, such as frequent changes in payment details or singular high-value transactions.

Operational red flags

Lack of transparency concerning ownership and the nature of business operations can raise concerns for PSPs, especially if ownership is obscured by complex corporate structures.

• Traffic sourcing that appears suspicious, such as leads from non-verified affiliates or unusual geographical patterns, can be indicative of potential fraud risk.
• Absence of clear communication about transaction or service guarantees may signal operational weaknesses, leading to potential disputes with customers.
• Difficulties in accessing customer support or complaint resolution processes may indicate poor operational management, causing alarm for acquirers.

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 payouts
• description of antifraud setup and monitoring tools

Product & marketing

demo access or screenshots of any platforms offered

• marketing plan and traffic source overview
• geographic targeting information
• KYC flow details, including IDV providers and thresholds

Technical integration & security

overview of payment architecture and supported methods

• description of relevant security features and compliance
• PCI DSS compliance status and data storage policy

Operations

customer support coverage and capabilities

• SLA for dispute handling and chargeback response
• operational processes related to customer transactions
• internal procedures for managing operational risks

Regulation & Licensing

Licensing and certification are essential for merchants in the "Reserved for national use" MCC, as they may engage in activities that require strict adherence to regulatory standards. Recognition of licenses by PSPs varies based on the merchant's jurisdiction and target markets, underscoring the importance of compliance.

Operator licenses

This MCC does not typically apply to general commercial activities, but relevant licenses may pertain to specific industries that interact with national regulations, such as transportation or logistics.

• National transportation authorities or governmental departments may require approvals for services using this MCC.
• In some regions, specific state or regional licenses might be necessary if the entities provide services impacting commerce or transportation.

Geo-restrictions

Many countries have specific regulations regarding internal commerce that can prohibit transactions depending on the type of activity associated with the MCC.

• Certain jurisdictions may have restrictions on foreign entities operating in the national territory, impacting cross-border acceptance.
• National transportation regulations can lead to varying requirements for state or regional operators.

Certifications & audits

Compliance with local regulations typically includes audits by governmental or regulatory bodies.

• Safety and operational standards may require periodic inspections or certifications from national transport authorities.
• Some regions may enforce additional standards related to operational safety or environmental assessments relevant to this MCC.

Official Definitions & Network Comparisons

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

Explanation:

All networks classify this MCC as "reserved for national use," highlighting a lack of universal application. This means certain MCCs may not be available for standard merchant processing, and their exact implementations can vary by region or network. Merchant onboarding can be affected by the lack of clarity on permissible activities, and common denial reasons may stem from ambiguous usage of this MCC or localization requirements.

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:

Ensure that your type of service aligns directly with the MCC classification. Misclassifying your business can lead to payment processing issues and even account termination, so always choose the most descriptive code for your operations.

Best Practices for Merchants

Merchants operating under this MCC must be vigilant about compliance and operational efficiency to minimize risks and ensure smooth payment processing. The following best practices are designed to enhance transparency, reduce fraudulent activities, and optimize payment acceptance strategies.

Classification & transparency

always use the correct MCC; misclassification can lead to payment disruptions and account issues

• ensure that your website clearly explains your services, including any geographic or operational limitations
• provide transparent information regarding business practices, including refund and dispute policies

Fraud & chargeback reduction

implement 3DS or step-up authentication for transactions that exhibit high-risk characteristics

• utilize clear and recognizable billing descriptors to avoid confusion and reduce chargeback rates
• maintain detailed logs of transaction events to support your case in the event of a dispute

Payment acceptance optimization

diversify your payment methods to include cards, digital wallets, and alternative payment solutions

• assess and route transactions based on geographic trends and payment provider performance for better conversion rates
• consider setting up separate merchant IDs (MIDs) for different product lines or regions to tailor your approach

Operational discipline

establish key performance indicators (KPIs) to monitor auth rates, chargeback levels, and transaction trends

• conduct regular compliance audits to ensure adherence to policies and identify areas for improvement
• designate a specific team or individual responsible for handling disputes and customer queries with defined response times

Payouts & liquidity

create a financial buffer to accommodate rolling reserves and unexpected settlements

• implement automated checks for anti-money laundering (AML) to ensure compliance during withdrawal processes
• track the speed and volume of payouts diligently to identify any unusual activity or potential fraud risks

Business Scope & Examples

This MCC is reserved for national use and does not typically cover specific types of businesses. In practice, this means it is generally not applicable for directly categorizing merchant models within the standard payment processing framework. As such, merchants should avoid using this MCC for transactional purposes.

Models

This code is not associated with any standard business models that fall within typical merchant classifications.

Borderline cases

General Rental Services — Businesses involved in the rental of various goods (e.g., vehicles, equipment) may consider other MCCs that more accurately represent their services, as this code does not apply.

• Private or Government Services — Certain government-owned or operated services may be classified elsewhere and should not utilize this specific MCC for transactions.

Signals for correct classification

Consider whether your business fits more appropriately under a distinct MCC that clearly represents your business model.

• Consult payment network guidance to identify suitable MCC alternatives relevant to your services.
• Avoid using this MCC for standard transactional purposes; seek clarification on applicable codes.