Computer Software Stores.
Retail of packaged and downloadable software.
- MCC
- 5734
- Category
- Miscellaneous Stores
- Cardflo support
- Yes
What MCC 5734 covers
Merchant Category Code 5734 is the ISO 18245 identifier used by the card networks for computer software stores. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
Retail of packaged and downloadable software. Choosing the right MCC is critical: an incorrect code can lead to higher interchange, surcharges, or, in regulated categories, declined transactions and account holds.
MCC 5734 covers merchants primarily engaged in selling computer software, including packaged software, downloadable licenses, and increasingly, subscription-based models for perpetual licenses or software-as-a-service (SaaS). Purchases range from individual applications to enterprise-level solutions, with ticket sizes varying dramatically.
Frequency can be one-off or recurring for subscription services.
Chargebacks are often driven by 'non-receipt' for downloadable content (where the download link fails or is not sent), 'not as described' due to compatibility issues or unmet feature expectations, and 'fraud' for high-value software licenses.
For subscription models, 'cancellation not processed' is a common dispute reason. Scheme programmes like Visa's Compelling Evidence 3.0 rules and Mastercard's Digital Goods programme aim to address disputes specific to digital content.
Cardflo's robust subscription management tools and retry logic can significantly reduce involuntary churn and 'cancellation not processed' chargebacks, particularly relevant for recurring software payments. Its KYB onboarding ensures compliance for a wide range of software vendors, including those offering niche or high-risk applications.
Software retailers must configure acceptance for immediate digital delivery and subscription models, prioritising strong front-end fraud tools like 3DS2 for high-value single purchases. Due to the high CNP nature, a moderate reserve may be expected, particularly for emerging merchants.
Ensure your payment gateway supports flexible recurring billing for subscriptions and robust tokenisation. Given the intangible nature, focus on clear terms of service, refund policies for digital goods, and irrefutable proof of digital delivery or access to mitigate 'not received' disputes and subsequent recovery efforts.
Acquirer and acquirer assessment stance.
Low to medium-risk standard board, depending on the software type and business model. High-value single purchases or frequent recurring billing can escalate risk.
Clear terms of service, refund policies, and download delivery confirmations are critical.
Dispute and chargeback profile.
The most prevalent chargeback reason codes are "13.2 / 4855 (merchandise was not received)" for download issues, and "13.1 / 4853 (services not as described)" due to unmet expectations or compatibility. For subscription services, often "13.3 / 4837 (cancellation of recurring transaction)" occurs.
For 'not received', provide download links, IP logs, timestamps of access, and confirmation emails sent. For 'not as described', present detailed product specifications, system requirements, licensing agreements, and customer support interactions.
For 'cancellation', show evidence of confirmed charges, clear cancellation policies, and proof of prior notifications.
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 5734
- Placement with acquirers that actively board MCC 5734 businesses in your region.
- MCC review during onboarding to confirm the right code for your products.
- Reclassification support if scheme rules or product mix change post-launch.
- Multi-acquirer routing to keep approvals stable for broad merchant categories.
- Dispute support tuned to the mixed-product chargeback profile this MCC sees.
- Dedicated onboarding manager rather than a generic ticket queue.
Payment methods typically enabled.
Onboarding checklist.
What acquirers typically ask to see when boarding MCC 5734. 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 trading pattern.
- Product catalogue extract confirming the MCC covers the goods actually sold.
- Refund, exchange and cancellation policy shown at point of sale and on the website.
- PCI DSS SAQ appropriate to the environment (A, A-EP or D as relevant).
- 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 merchants selling downloadable software best defend against 'merchandise not received' chargebacks?
For downloadable software, physical proof of delivery is impossible. Merchants must gather compelling evidence: IP address of download, download timestamps, customer login records confirming access, email confirmation of download link delivery, and any communication logs regarding successful installation or use.
Some schemes, like Visa under Compelling Evidence 3.0, allow proof of digital delivery and continued usage as a strong defence against these claims, particularly for transactions under certain thresholds.
What specific challenges do subscription-based software models (SaaS) face regarding chargebacks for 'cancellation not processed'?
For SaaS, 'cancellation not processed' (Visa Reason Code 13.3) is frequent. Merchants need a clear, easily accessible cancellation process.
Evidence to dispute these involves demonstrating the customer did not cancel via the proper channels, continued usage post-alleged cancellation, or that the cancellation request was received after the billing cycle cut-off. Ensuring customers receive email confirmations of their subscription and cancellation is critical.
Cardflo's recurring billing tools offer dunning management and clear customer communication to minimise these disputes.
Are there specific scheme rules for trials that convert to paid software subscriptions?
Yes, schemes have specific rules for trial-to-paid conversions. Merchants must clearly disclose the trial duration, the amount charged after the trial, and the billing frequency during sign-up.
Usually, a notification email must be sent to the cardholder a few days before the trial converts, reminding them of the upcoming charge and how to cancel.
Failure to adhere to these rules can result in automatic chargeback liability for 'recurring transaction' disputes (Mastercard Reason Code 4849) or similar categories.
What specific evidence is most effective for demonstrating digital software delivery and usage to dispute 'merchandise not received' claims?
To combat 'merchandise not received' claims for digital software, the most effective evidence includes IP address logs showing successful download or access from the cardholder's location, timestamps of download initiation and completion, and any unique license keys or activation codes issued and subsequently used.
Proof of email delivery containing download links or access instructions, alongside records of account creation and login activity within the software platform, also serve as compelling evidence.
This data helps establish that the digital product was made available and, in most cases, accessed by the cardholder.
How can software merchants manage recurring billing for subscriptions to reduce 'cancellation not processed' chargebacks and maintain compliance?
To effectively manage recurring subscriptions and minimise 'cancellation not processed' chargebacks, merchants should implement a clear and easily accessible cancellation process, ideally through the customer's account portal or via direct contact methods.
Provide clear terms of service during sign-up, detailing billing cycles, amounts, and cancellation policies. Send pre-billing notifications before each renewal, particularly for annual subscriptions.
Maintain comprehensive records of subscription start dates, billing events, and any communication regarding cancellations or account changes. Promptly process all cancellation requests and provide confirmation to the customer to ensure compliance with PSD2 and scheme rules.
Other MCCs in Miscellaneous Stores
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.