7379 Computer maintenance, repair and services

Introduction

• What it is: This MCC covers businesses focused on computer maintenance, repair, and related services that aren't classified elsewhere.
• Risk level: Medium — There may be variable performance among service providers.
• Acceptance difficulty: Medium — Some payment processors may require additional documentation due to service variability.
• Typical business models: IT support firms; computer repair shops; hardware maintenance services; technical consulting services.
• For merchants: Expect moderate transaction fees; potential reserve requirements; may face longer approval processes.
• What PSPs expect: Proof of business registration; clear service offerings on the website; a history of successful service delivery.

Payment Insights & Benchmarks

Merchants operating in the computer maintenance, repair, and services category should anticipate unique payment experiences that may differ from standard e-commerce. Factors like method preferences and higher fraud prevention measures can influence transaction success and costs.

Payment methods

Cards: generally accepted, but approval may vary based on the type of service and customer profile.

• E-wallets: a popular option among tech-savvy customers, offering ease of use for both one-time and recurring payments.
• Bank transfers: used frequently for larger transactions, but can lead to longer settlement times.
• Invoicing: common for service contracts, providing customers flexibility, yet prone to delayed payments.

Authentication & security

Strong authentication measures (like 3DS and SCA) are often required to prevent fraud, especially for online services.

• These measures can positively impact chargeback rates but may also lead to customer frustration if not implemented carefully.
• Continuous monitoring of fraud patterns is essential, as the risk profile can change rapidly in service-based transactions.

Benchmarks (indicative, not guaranteed)

MDR: likely to be higher compared to standard e-commerce due to service-based nature.

• Rolling reserves: may be required, particularly for merchants with higher service-level risks.
• Settlement times: typically longer, often exceeding 5 days compared to faster product sales.
• Chargeback ratios: potentially elevated due to the nature of disputes in service-related offerings.
• Approval rates: usually lower for card payments compared to other sectors, with higher acceptance for alternative payment methods.

Key metrics to monitor

Conversion rates segmented by payment method to assess performance effectiveness.

• Chargeback ratios and dispute reasons specific to service quality versus unauthorized claims.
• Average payment processing time to manage cash flow predictably.
• Customer retention rates linked to payment satisfaction and ease of use.
• Rate of fraudulent transactions to adjust security measures as needed.

Risk & Compliance

Merchants in the MCC for Computer Maintenance, Repair and Services face unique challenges relating to fraud and chargeback management, making compliance with best practices crucial. PSPs and acquirers implement stringent measures to mitigate risks associated with this sector, and merchants must be proactive in addressing potential issues.

Chargebacks & fraud

Frequent occurrences of chargebacks resulting from customer dissatisfaction or misunderstanding of services rendered, contributing to "I didn’t authorize this transaction" claims.

• Some cases of friendly fraud and use of stolen credit cards for purchasing repair services or parts.
• A common mitigation tool is implementing refund policies with clear communication and obtaining detailed service agreements that outline scope and pricing.
• Monitoring for signs of multi-accounting and ensuring robust verification processes can help curb abuse.

AML/KYC expectations

Strong customer identity verification is expected, including verification of identity documents and address provided by clients to mitigate risk.

• Sanctions and Politically Exposed Persons (PEP) checks should be performed regularly to ensure compliance.
• Source-of-funds verification may be triggered for high-value transactions, unusual payment methods, or repeated purchases that deviate from typical patterns.
• Manual review triggers may include first-time customers making large purchases or accounts originating from high-risk jurisdictions.

Operational red flags

Lack of transparency regarding business ownership and operations can raise concerns; clear disclosure of who operates the service is critical.

• High volumes of chargebacks may signal issues with service quality or client satisfaction, leading to scrutiny from payment processors.
• Deals or promotions that sound too good to be true can signal potential fraud or scams, raising a caution flag for PSPs.
• Absence of clear communication regarding service expectations, refund policies, or lack of customer support responsiveness may alarm acquirers and lead to compliance issues.

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 the live platform

• marketing plan and traffic source overview (affiliates, SEO, PPC)
• geographic targeting information
• KYC flow details, including IDV providers and thresholds

Technical integration & security

payment architecture overview with supported methods/providers

• description of SCA/3DS flows, retry logic, and tokenization
• PCI DSS compliance status and data storage policy

Operations

customer support coverage (languages, 24/7 if available)

• SLA for dispute handling and chargeback response
• deposit, bet, and payout limits; self-exclusion mechanisms
• internal process for chargeback investigation and documentation

Regulation & Licensing

Licensing and certification are important for merchants in this MCC, as they ensure compliance with local regulations and industry standards. The recognition of licenses depends on the merchant’s jurisdiction and the specific markets they intend to serve.

Operator licenses

Business licenses — typically required at the local level for operating a repair or maintenance service.

• Specialty certifications (e.g., Apple Certified Service Provider) — may be recognized by specific manufacturers and enhance business credibility.
• Data protection certifications (such as GDPR compliance) — important when handling sensitive customer information.
• State-level installer licenses — required in some regions for certain types of computer work (e.g., installations that involve hardware modifications).

Geo-restrictions

Some countries may require specific business registration that aligns with local laws for technology services.

• Certain regions may have restrictions on the types of services offered, especially concerning data security and consumer protection standards.
• International operations may be limited by local regulatory frameworks that vary widely between jurisdictions.

Certifications & audits

PCI DSS compliance is needed if the merchant processes card payments for services rendered.

• ISO 9001 certification can demonstrate quality management practices, which is beneficial for customer trust.
• Regular audits for data protection regulations, particularly if handling personal or financial data of consumers.
• Compliance with local consumer protection laws may also require periodic assessments and recommendations.

Official Definitions & Network Comparisons

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

Explanation:

The terminology used by the networks varies, with nuances in defining what constitutes "repair" and "maintenance." Each network has its own set of requirements for documentation and monitoring, affecting how services are classified and how merchants are assessed. Common reasons for onboarding issues may include insufficient service detail, excessive chargebacks, and geographic limitations.

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:

When classifying under an MCC, ensure that the primary service provided aligns closely with the definition. Mixing unrelated services can lead to misclassification issues and potential penalties. Always select the most specific MCC that reflects the main service of your business.

Best Practices for Merchants

Merchants operating under the MCC 7379 must prioritize risk management and payment operations to facilitate seamless transactions and maintain compliance. Implementing the following best practices will enhance acceptance rates and minimize exposure to disputes.

Classification & transparency

always use the correct MCC; attempts to bypass classification often lead to account closure

• clearly display service offerings, licensing, and other relevant policies on the website
• maintain transparent business models and use clear billing descriptors to avoid confusion

Fraud & chargeback reduction

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

• ensure clear billing descriptors and provide instant confirmations (via SMS/email) to reduce misunderstandings
• log all service events and transactions meticulously to build a solid case for dispute representments

Payment acceptance optimization

support multiple payment methods (cards, wallets, etc.) to cater to diverse customer preferences

• analyze transaction patterns to route payments effectively by geography or customer segment, ensuring optimal performance
• use separate MIDs to differentiate services or locations, simplifying compliance with various payment schemes

Operational discipline

regularly track KPIs such as authorization rates, chargeback ratios, and response times to identify areas for improvement

• conduct routine compliance audits to ensure all processes are up-to-date and align with industry standards
• appoint a dedicated team or individual to handle disputes, ensuring timely and efficient response and resolution

Payouts & liquidity

maintain adequate liquidity buffers to accommodate rolling reserves and ensure stability during extended settlements

• implement automated AML and compliance checks for withdrawals, particularly for larger amounts
• continuously monitor payout processing time and flag any irregular withdrawal patterns for further investigation

Business Scope & Examples

This MCC encompasses businesses that provide services related to computer maintenance and repair, including software services, troubleshooting, and technical support. Merchants falling under this category typically engage in direct service delivery to maintain or enhance the functionality of computer systems and related technology.

Models

Computer repair shops

• IT consulting services
• Data recovery services
• On-site technical support providers
• Remote IT support services
• Software installation and configuration services

Borderline cases

Electronics recycling — businesses that recycle electronic components may handle computers but are primarily focused on disposal, not repair or servicing.

• Retail electronics — stores selling computers and peripherals might provide limited support but do not primarily offer repair or maintenance services.

Signals for correct classification

services directly involve repairing or maintaining existing computer systems

• business models operate primarily on a service fee rather than product sales
• customer engagement typically includes troubleshooting and technical support activities