5734 Computer software stores

Introduction

• What it is: This MCC covers businesses primarily selling computer software and related products.
• Risk level: Medium — It can have varying fraud risks associated with digital products.
• Acceptance difficulty: Medium — Some PSPs may require additional verification for online sales.
• Typical business models: software retail stores; online software distributors; subscription-based software services; game development studios.
• For merchants: Expect moderate MDR; potential for reserves on high-value transactions; may require detailed product listings.
• What PSPs expect: Clear business structure; robust refund policy; transparency in software licensing agreements.

Payment Insights & Benchmarks

Merchants in this MCC should anticipate varied payment experiences influenced by transaction types, customer behaviors, and potential security challenges. Understanding these nuances can help in optimizing acceptance and minimizing costs.

Payment methods

Cards: the primary payment method, but may face scrutiny due to higher fraud risk, resulting in lower approval rates.

• E-wallets: increasingly popular for quick transactions and ease of use, particularly for digital products.
• Bank transfers: often underutilized but effective for larger purchases; require robust reconciliation processes.
• Subscription payments: necessitate seamless recurring billing; chargebacks can be challenging if not managed well.

Authentication & security

Strong customer authentication (SCA) and 3DS protocols are commonly used to enhance security for online transactions.

• While these measures help reduce unauthorized charges, they can also lead to increased friction in the checkout process.
• Merchants should monitor patterns of fraud and be aware that digital goods can experience higher levels of chargebacks.

Benchmarks (indicative, not guaranteed)

MDR: typically higher than standard e-commerce, reflecting the added complexity of digital goods.

• Rolling reserves: may be implemented by acquirers, often at significant percentages to mitigate risk.
• Settlement times: generally longer, often exceeding 5 to 7 days due to the nature of digital goods.
• Chargeback ratios: can be higher than average due to disputes often arising from digital transactions.
• Card approval rates: usually lower, necessitating a focus on optimizing transaction flows.

Key metrics to monitor

Purchase conversion rates segmented by payment method.

• Chargeback rates specifically tied to customer service inquiries versus fraud.
• Recurring payment failures and success rates.
• Customer feedback regarding payment experiences, particularly on friction points.

Risk & Compliance

Merchants under the Computer Software Stores MCC are subject to significant scrutiny due to the potential for high rates of chargebacks and fraud. PSPs and acquirers typically implement stringent measures, expecting merchants to proactively mitigate risks associated with digital products and ensure compliance with AML/KYC requirements.

Chargebacks & fraud

Common types of fraud include friendly fraud, where customers dispute legitimate charges, and use of stolen credit card information for software purchases.

• Chargeback spikes can occur after promotional periods or discount offers, as customers may attempt to exploit these situations.
• Mitigation tools such as device fingerprinting, behavioral analytics, and transaction monitoring can help identify suspicious activity before it escalates.

AML/KYC expectations

Strong identity verification processes are required, including government-issued ID checks and validation against sanctions lists.

• Merchants must conduct source-of-funds checks for high-value transactions or irregular purchasing behavior.
• Manual review triggers may include frequent refunds, high-volume purchases of digital goods, or discrepancies in user registration information.

Operational red flags

Lack of transparency regarding ownership, especially in white-label setups, can lead to heightened scrutiny from PSPs.

• Unclear business practices, such as insufficient refund policies or absence of clear product descriptions, raise concerns about legitimacy.
• Traffic generated from unverified channels or countries with high fraud rates can alarm acquirers and lead to further investigations.
• Failure to implement adequate customer support could result in unresolved disputes, prompting higher chargeback rates.

Onboarding Checklist

Merchants operating under the Computer Software Stores MCC must be thorough in preparing their onboarding package. A well-organized submission maximizes the likelihood of approval from payment service providers (PSPs) or acquirers and expedites the review process.

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

Product & marketing

demo access or screenshots of the live platform

• overview of marketing strategies and traffic sources
• geographic targeting information
• KYC flow details, including methods for identity verification

Technical integration & security

payment architecture overview including supported payment methods

• description of SCA/3DS flows and tokenization methods
• PCI DSS compliance status and data storage policies

Operations

customer support setup (availability and languages)

• service level agreements (SLA) for dispute resolution
• policies regarding refunds, exchanges, and software licensing
• internal procedures for chargeback handling and customer feedback

Regulation & Licensing

Licensing and certification are essential for merchants in the Computer Software Stores MCC, as they confirm compliance with industry standards and legal requirements. Recognition of these licenses is contingent upon the merchant's jurisdiction and the specific markets they serve.

Operator licenses

Software Publisher License — often required for distributing proprietary software; recognition varies by region.

• Export Control Licenses — necessary for software that involves encryption or sensitive technology, depending on country regulations.
• Business Licenses — general operating permits that may be required at the local, state, or national level.
• Copyright Registration — while not a license, it is crucial for protecting intellectual property and may be required for certain types of software.
• Some jurisdictions may also require specific licenses for software applications that involve financial transactions or personal data.

Geo-restrictions

Certain countries have restrictions on software that may deal with personal data or encryption technology, potentially blocking transactions.

• Export restrictions exist for software containing sensitive technology, especially to countries with trade sanctions.
• Some jurisdictions require a local presence or office for operation, affecting online sales to specific regions.

Certifications & audits

PCI DSS compliance for software that handles payment card information.

• ISO 27001 for information security management, ensuring best practices in data protection.
• Regular software security assessments and vulnerability audits to comply with industry standards.
• GDPR compliance audits if dealing with personal data of EU citizens.

Official Definitions & Network Comparisons

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

Explanation:

Although the definitions may seem straightforward, differences in terms such as "retail" and specifics about physical vs. digital goods can impact classification. Each network has unique compliance requirements and may impose different onboarding processes based on their definitions. Common issues include misclassification of hardware or service-oriented businesses as software-only stores, leading to onboarding delays.

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 primary business activity aligns closely with MCC 5734. If the bulk of your sales are not related to software or involve other types of products or services, it's crucial to choose a more accurate MCC to avoid compliance issues. Misclassifying your business can lead to account closures and potential financial penalties.

Best Practices for Merchants

Merchants operating under the MCC 5734 for Computer Software Stores need to be diligent in managing their payment systems, risk factors, and operational processes. By adhering to the best practices outlined below, merchants can enhance their payment acceptance capabilities while minimizing disputes and maintaining solid relationships with payment service providers (PSPs).

Classification & transparency

always use the correct MCC; improper classification can lead to compliance issues and account restrictions

• ensure your website clearly displays return and refund policies, as well as software licensing information
• provide clear and accurate billing descriptors for transactions to enhance customer recognition

Fraud & chargeback reduction

implement 3DS or step-up authentication for high-risk transactions (e.g., new customers or large purchases)

• offer instant confirmations via SMS/email and maintain accessible customer support for transaction inquiries
• log details of software sales and customer interactions to create a robust defense for chargeback representments

Payment acceptance optimization

support various payment methods (credit/debit cards, digital wallets, alternative payment options) to meet customer preferences

• analyze payment routing by geography and adjust settings based on real-time performance insights
• consider using separate merchant IDs (MIDs) for different software offerings to tailor risks and compliance management

Operational discipline

monitor key performance indicators (KPIs) like authorization rates, chargeback ratios, and average order value (AOV)

• conduct regular compliance audits and update internal payment policies to comply with evolving industry standards
• establish a dedicated dispute resolution team to handle chargeback incidents promptly and within service level agreements (SLAs)

Payouts & liquidity

set aside liquidity buffers to manage rolling reserves and cover potential chargeback liabilities

• automate anti-money laundering (AML) checks for all withdrawal requests, particularly those above specified thresholds
• keep a close watch on withdrawal patterns to detect unusual or suspicious activities promptly

Business Scope & Examples

This MCC covers businesses primarily involved in the retail sale of computer software. Merchants classified under this category typically sell licensed software products directly to consumers or provide digital downloads, catering to both individuals and businesses. The scope includes both physical storefronts and online platforms.

Models

brick-and-mortar software retail stores

• online software download platforms
• subscription-based software services (SaaS)
• software license resellers and distributors
• educational software providers

Borderline cases

Digital game distribution — while often software-related, merchants focusing solely on video games may fall under a different MCC related to entertainment.

• Hardware retailers — businesses that primarily sell computer hardware with incidental software offerings may not qualify.
• Mobile app developers — while they create software, development-focused businesses that sell apps only on mobile platforms could differ in classification.

Signals for correct classification

primary revenue comes from the sale of licensed software products

• offers a wide range of software titles, including major brands and applications
• supports both one-time purchases and subscription models for software access