Computer Programming, Data Processing & Systems Design.
Custom software, IT consulting and SaaS development.
- MCC
- 7372
- Category
- Business Services
- Cardflo support
- Yes
What MCC 7372 covers
Merchant Category Code 7372 is the ISO 18245 identifier used by the card networks for computer programming, data processing & systems design. Acquirers, issuers and regulators use this code to set interchange, scheme fees, fraud rules and reporting categories for every transaction your business processes.
Custom software, IT consulting and SaaS development. Choosing the right MCC is critical: an incorrect code can lead to higher interchange, surcharges, or, in regulated categories, declined transactions and account holds.
This MCC is for merchants providing computer programming, data processing, and systems design services. This includes custom software development, IT consulting, and Software-as-a-Service (SaaS) development.
Typical transaction sizes vary widely, from smaller monthly subscription fees for SaaS products to large project-based invoices for custom development, sometimes reaching five or six figures. Frequency is often recurring for SaaS or managed services, or milestone-based for projects.
Chargebacks are generally low, often related to service dissatisfaction, project delays, or disputes over deliverables not meeting expectations. Friendly fraud, where a cardholder claims non-receipt or non-provision of service, can occur but is not dominant.
Scheme rules on 'digital goods' or 'services not rendered' are relevant.
Cardflo's ability to support recurring billing models and offer robust B2B payment solutions, including account-to-account transfers for larger invoices, significantly benefits merchants in this MCC, ensuring higher approval rates and lower processing costs for substantial transactions.
Businesses within computer programming and systems design should optimise their payment stack for diverse transaction types, from recurring SaaS subscriptions to significant project-based milestone payments. Prioritise a multi-acquirer gateway with robust fraud screening, given the CNP nature of most transactions.
For larger projects, consider implementing a phased payment structure aligned with deliverables, clearly defined in contractual agreements. Emphasise strong client communication and documentation throughout the project lifecycle to mitigate 'Non-Receipt of Services' disputes, ensuring your payment acceptance strategy supports both speed and accountability.
Acquirer and acquirer assessment stance.
Low-risk standard board. These are generally stable businesses with clear service agreements.
Standard underwriting applies, and reserves are rarely required unless specific risks are identified during due diligence.
Dispute and chargeback profile.
The most common chargeback reason codes in this sector are 13.1 / 4853 (services not as described) and 13.3 / 4855 (non-receipt of services).
These typically arise when a client claims software did not meet specifications, project deliverables were incomplete, or a service was not rendered as expected.
To dispute these, provide original contracts, project proposals, detailed statements of work, change orders, logs of communication, and evidence of delivered code or completed tasks. For SaaS, supply usage logs, access records, and terms of service to prove service provision and acceptance.
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 7372
- Placement with acquirers that actively board MCC 7372 businesses in your region.
- B2B card-not-present processing with Level 2 and Level 3 data support.
- Virtual-card, AP-automation and procurement-card acceptance.
- Invoice-linked payment flows and pay by link options for receivables teams.
- Settlement and reconciliation that maps cleanly to ERP and accounting systems.
- Dedicated onboarding manager experienced with B2B and corporate merchants.
Payment methods typically enabled.
Onboarding checklist.
What acquirers typically ask to see when boarding MCC 7372. 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 B2B volume.
- Standard master services agreement or engagement letter template.
- Level 2 / Level 3 data capability evidence for commercial-card processing.
- Refund, cancellation and dispute-handling policy for recurring or retainer billing.
- Six months of processing statements or bank statements demonstrating trading pattern.
See also: Know Your Customer (KYC) · high-risk merchant · smart routing.
Talk to an acquiring specialist about your MID setup.
Common questions
How can 3D Secure exemptions be managed for recurring SaaS subscriptions under MCC 7372?
For recurring SaaS subscriptions, merchants can often benefit from 3D Secure (3DS) exemptions under transaction risk analysis (TRA) rules.
If the initial transaction is authenticated with 3DS and subsequent payments are consistent in value and frequency, the acquirer may be able to flag these for 'merchant-initiated transaction' (MIT) exemptions, minimising friction.
Cardflo's robust acquiring network can help configure this for optimal balance between security and conversion.
What payment methods are common for large B2B software development projects?
For substantial B2B software development projects under MCC 7372, traditional card payments are often supplemented by or replaced with bank transfers, such as SEPA Credit Transfer or Faster Payments. These methods are preferred for their lower fees on high-value transactions and reduced chargeback risk.
Cardflo supports a wide range of B2B payment solutions, including direct bank transfers, to reduce costs and administrative burden.
Are there specific chargeback thresholds for 'services not rendered' in this MCC?
While there isn't a specific scheme-mandated chargeback threshold unique to 'services not rendered' under MCC 7372, general dispute thresholds apply.
Merchants exceeding 0.9% chargeback-to-transaction ratio (Mastercard) or 0.9% dispute-to-sales ratio (Visa) may enter monitoring programmes like Visa's Dispute Monitoring Program (VDMP) or Mastercard's Excessive Chargeback Program (ECP). Clear contracts and proof of service delivery are crucial for dispute resolution.
We sell SaaS. How can we manage chargebacks where a customer claims they cancelled their subscription but were still charged?
For SaaS subscriptions, it's crucial to have clear, accessible cancellation policies and an efficient process for handling cancellation requests. Ensure your customer portal clearly shows subscription status and provides a visible cancellation option.
Implement an automated system that sends a confirmation email upon cancellation, stating the final billing date. If a chargeback occurs, provide the initial subscription agreement, evidence of service usage up to the cancellation date, cancellation request logs, and the cancellation confirmation email.
This documentation proves the customer received service and acknowledges the agreed billing and cancellation terms.
Our business develops custom software. What payment acceptance strategies prevent disputes over project deliverables or scope creep?
For custom software development, adopt a milestone-based payment structure that aligns invoices with specific, agreed-upon deliverables or project stages. Each payment should be clearly linked to a pre-defined achievement.
Implement formal client sign-off procedures for each completed milestone, acknowledging satisfaction or raising concerns before the next phase begins. Your contracts must explicitly detail the project scope, deliverables, timelines, and a formal change management process for any scope adjustments.
This robust documentation and phase-gate approach significantly reduces the likelihood of 'services not as described' disputes and provides strong evidence if one arises.
Other MCCs in Business Services
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.