MCC Codes
Cardflo supports this MCC
MCC 5817

Digital Goods, Applications (Excluding Games).

Software application downloads and digital apps.

MCC
5817
Category
Miscellaneous Stores
Cardflo support
Yes
Apply now

What MCC 5817 covers

Merchant Category Code 5817 is the ISO 18245 identifier used by the card networks for digital goods, applications (excluding games). Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.

Software application downloads and digital apps. 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 5817 covers digital goods merchants selling applications and software (excluding games). This includes productivity software, utility apps, operating systems, and professional tools, often sold via licenses, subscriptions, or one-time downloads.

Ticket sizes can vary significantly from low-cost utility apps to high-value software suites. Frequency depends on the product model, with subscriptions being highly recurring.

Chargebacks typically arise from 'non-receipt of goods' (e. g. , licensing key issues, download failure), 'unauthorised transactions', or 'service not as described' (e. g. , software bugs, lack of advertised features).

Given the recurring nature of many software sales, 'cancellations not processed' are also frequent dispute reasons. These merchants should be mindful of scheme rules concerning subscription billing.

Cardflo's comprehensive subscription management features, including dunning management, intelligent retry logic, and seamless integration with account self-service portals, helps reduce involuntary churn and 'cancellation not processed' chargebacks.

Merchants selling digital applications should configure their acceptance to support both one-time purchases and subscription models, leveraging payment tokenisation for recurring billing and ensuring compliance with scheme guidelines for subscription management.

Implement 3DS2 strategically, especially for initial subscription payments or higher-value software licenses, balancing security with conversion. Maintain clear communication around subscription terms, including renewal dates and cancellation procedures, to mitigate disputes.

Given the varying ticket sizes, a multi-acquirer setup can optimise routing for cost and success rates. Rolling reserves, typically 2.5-5% for 90-180 days, may apply if dispute rates become elevated.

Acquirer and acquirer assessment stance.

Medium-risk standard board, leaning towards low for established SaaS providers with low chargeback rates. Risk factors increase for merchants with aggressive sales models, free trials ending in paid subscriptions, or complex licensing.

A 2.5-5% rolling reserve for 90-180 days might be applied if dispute rates rise above acceptable thresholds, particularly for subscription-based services.

Dispute and chargeback profile.

Common dispute reasons for digital applications include 13.1 / 4853 (merchandise/services not as described) often relating to software bugs or misrepresented features, and 13.3 / 4831 (cancellation of recurring transaction) when subscription cancellations are not processed.

For 'not as described' claims, present detailed product descriptions, release notes, and customer support logs demonstrating functionality as advertised.

To counter 'cancellation not processed', provide clear evidence of the cancellation policy being accessible to the cardholder, the date of cancellation request, and confirmation of services discontinued from that date.

See also: chargeback management · payment response codes · Compelling Evidence 3.0.

Payments built for Digital Goods, Applications (Excluding Games).

Book a scoping call to see how Cardflo would set you up.

Apply now

How Cardflo handles MCC 5817

  • Placement with acquirers that actively board MCC 5817 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.

Visa Credit / Debit
Mastercard Credit / Debit
Apple Pay
Google Pay
AMEX
Open Banking

Onboarding checklist.

What acquirers typically ask to see when boarding MCC 5817. 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.

Route MCC 5817 traffic with confidence.

Talk to an acquiring specialist about your MID setup.

Apply now

Common questions

What are the specific scheme rules for recurring billing in MCC 5817?

Both Visa and Mastercard have strict rules for recurring billing, requiring merchants to clearly disclose subscription terms, provide easy cancellation methods, and send notifications before renewal for annual or high-value subscriptions.

Failure to comply can lead to 'cancellation not processed' chargebacks, which are difficult for merchants to win if evidence of clear disclosure and cancellation options is lacking.

How can MCC 5817 merchants minimise 'non-receipt of goods' chargebacks given digital delivery?

Merchants should implement robust delivery mechanisms, such as immediate email delivery of licence keys/download links, and ensure these are also accessible within a customer's account portal. Logging download attempts, IP addresses, and successful activations provides strong evidence for chargeback disputes.

Proactive customer support for activation issues is also crucial.

Is 'free trial conversion' a chargeback risk for digital applications?

Yes, 'free trial conversion' can be a significant chargeback risk. Merchants must explicitly inform customers about the automatic conversion to a paid subscription after the trial period ends, including the billing date and amount.

Clear opt-out instructions should be provided. Claims of 'unauthorised transaction' or 'service not as described' often arise when these disclosures are insufficient, leading to chargebacks that can be difficult to defend.

What detailed operational steps should I take to minimise chargebacks related to 'service not as described' for my software applications?

To reduce 'service not as described' chargebacks, ensure all marketing materials and product descriptions precisely reflect your software's current features and capabilities. Avoid overstating performance or ease of use.

Provide readily accessible, detailed specifications, system requirements, and user guides. Implement a transparent bug reporting system and publicly share release notes for updates, demonstrating continuous improvement.

Crucially, offer responsive customer support that can troubleshoot issues or offer appropriate resolutions, including refunds where necessary. Proactive communication about known issues or service interruptions can also prevent dissatisfaction escalating to a dispute.

Given that many applications are subscription-based, what are the key compliance requirements regarding recurring payments to avoid disputes?

For subscription-based applications, strict adherence to scheme rules for recurring payments is critical. This includes obtaining explicit cardholder consent for recurring billing, providing clear terms and conditions at the point of sale, and sending timely notifications before each recurring charge.

Merchants must offer an easy, transparent cancellation process and honour all cancellation requests promptly, ensuring no further charges are made. Maintain records of all consent, notifications, and cancellation requests.

Implementing account updater services can help manage expired or reissued cards, reducing involuntary churn, but these must be accompanied by robust communication and clear opt-out options.

Apply with Cardflo

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.

Apply now
Apply now