MCC 7372 vs 5967: The Right Merchant Category Code for Adult AI Platforms

MCC 7372 is the code for computer programming, data processing, and integrated systems design services. This code is for software companies. An AI model behind your product does not turn your business into a software company. What you sell decides the code, not what you built it with.

An adult AI platform that generates or sells sexual content should be coded MCC 5967, not MCC 7372. MCC 5967 is the code that Visa uses to classify adult content merchants, and it falls under Tier 1 of the Visa Integrity Risk Program (VIRP). When 5967 doesn't fit, and 7372 isn't accurate either, non-explicit AI companion apps often fall under MCC 7273.

Trying to classify an adult AI business as software to avoid VIRP is a bad strategy. It is the exact kind of misclassification that gets merchant accounts shut down. 

This article covers when each code is appropriate, who assigns the MCC, whether a merchant can be reclassified after approval, and what happens when an adult AI platform is coded incorrectly.

MCC 7372 vs 5967 vs 7273 at a Glance

These three MCCs cover very different business models:

• MCC 7372 is for software services. It covers custom software development, SaaS, APIs, systems integration, and data processing. But card networks classify businesses by what customers pay for, not by the technology behind it. Calling it “tech” doesn't change the classification.

• MCC 5967 is the relevant code for explicit adult content under Visa's VIRP framework. Its generic MCC label, “Direct Marketing – Inbound Teleservices,” is misleading and dates back to older commerce models. Visa's VIRP documentation identifies 5967 for Adult Content Merchants, which can include AI-generated adult material. 

• MCC 7273 covers dating and escort services. It can fit non-explicit AI companion, dating, or matchmaking products. Adult users or intimate conversations alone don't make a product 5967. The line is drawn by the content and how you monetize it. 

Use the table below to identify the closest fit.

One more detail to remember: an acquirer registered for 5967 is not automatically cleared for 7273. If you run a companion or matchmaking product, start with a processor that already handles the dating merchant account category properly.

Who Assigns the MCC?

The acquirer assigns the MCC. You don't choose it yourself. During underwriting, the acquirer reviews what you sell and how the business operates, then assigns the code that fits.

Calling yourself an “AI software company” won't make MCC 7372 correct. Underwriters can review your website, checkout flow, paywalled content, and marketing to determine what customers are actually buying.

Your best move is to disclose the business accurately from day one. The acquirer either approves the right category or tells you they can't support it. Both are better than getting terminated months later because your MCC doesn't match your business.

Working with someone who handles adult AI accounts regularly saves a lot of pain. A specialist can present and register the business correctly. Finding out that you used the wrong code during a compliance review is an unnecessarily expensive way to learn. 

If you have never confirmed which code your account carries, high-risk payment consulting is the fastest way to find out where you stand.

What Happens If an Adult AI Platform Is Miscoded as 7372?

Miscoding can turn into a serious compliance problem, even if the account processed without issues for months. 

Visa's AI tools detect merchants who fraudulently conceal the true nature of their businesses to avoid our compliance requirements, and terminations for noncompliance rose 5x between 2020 and 2024.

Once Visa or the acquirer spots a mismatch, the business can face:

• Compliance action and assessments passed from the acquirer to the merchant

• Higher reserves or increased declines while the account is reviewed

• Account termination if the activity isn't eligible under the current setup

• A MATCH listing in some cases, making future processing much harder

How severe the response is depends on how the mismatch happened and how it was discovered. An honest coding error found early is one thing. Representing an adult business as software to avoid Tier 1 requirements is another.

A merchant can run for months with no obvious issues before a monitoring alert, chargeback pattern, or portfolio review exposes the mismatch. “But we were approved as software” won't carry much weight at that point. Underwriting reflects what the acquirer approved. Monitoring looks at what you're doing now.

If you suspect your MCC doesn't match your current business, fix the discrepancy before compliance does it for you.

Can Visa or an Acquirer Reclassify an Adult AI Merchant?

Yes. An MCC isn't permanent. If your actual business no longer matches what was underwritten, the acquirer can review and reclassify the account. Initial approval under MCC 7372 doesn't give you a lifetime exemption.

Product and pricing changes can trigger that review. For example:

• An AI companion adds explicit image generation.

• A free chat product starts charging for NSFW content.

• A software platform adds an adult-content subscription.

None of these changes requires bad intent. They simply create a gap between what the acquirer approved and what the business now sells.

That's different from deliberately using 7372 to avoid Tier 1 requirements. Correcting a genuine mismatch is standard underwriting practice. 

The safest approach is to accurately disclose the business, use the appropriate MCC, and notify your acquirer when the product or monetization model changes.

Mastercard Runs Its Own Adult Content Rules

Visa compliance does not automatically cover Mastercard. Mastercard has its own adult-content standards, registration requirements, and review process. It does not use Visa's VIRP tier structure.

If you accept Mastercard on an adult AI platform, treat it as a second compliance track with its own paperwork. Our breakdown of Mastercard's adult content rules covers the specifics this article leaves out on purpose.

That also means don't carry Visa's fees, tiers, or integrity assessments into Mastercard. Those are Visa-specific. Mastercard sets its own rules and charges.

What Adult AI Operators Should Do

If you run an adult AI platform, the safest approach is to ensure your paperwork matches your business from day one:

1. Describe the product honestly: Explain what the platform generates, what customers pay for, and how access works. Underwriters will eventually see the same things.

2. Be clear about explicit content: If you generate or sell explicit sexual material, you're looking at 5967. A non-explicit companion or dating product is a different category, typically 7273.

3. Don't hide behind the “software company” label: AI is the technology. What matters is the product customers are buying.

4. Confirm your actual MCC: Ask your acquirer for the code assigned to your account and get the answer in writing. 

5. Verify the right Tier 1 registration: If your category requires registration, confirm that your acquirer is registered for your specific MCC. A neighboring category doesn't count.

6. Review Mastercard separately: Visa registration doesn't cover Mastercard. Different network, different rules.

7. Flag product changes before launch: Adding explicit generation, introducing paid NSFW content, or changing your monetization model can alter the risk profile. Tell your processor first and update the account if needed.

Our high-risk payment consulting covers upfront classification and registration, and risk management for high-risk merchants keeps the account clean once it goes live.

Final Thoughts

You don't get to choose the code that makes underwriting easier. The MCC should reflect what customers are buying, and that remains true after the account goes live.

Fixing a bad classification later is far more painful than getting it right at signup. You can end up dealing with reviews, reserves, account closure, and the awkward task of explaining your business to a new acquirer. Better to get the paperwork right the first time.

If you are ready to get onboarded, MobiusPay will handle NSFW AI payment processing, coded correctly from day one. Request a Personalized Analysis.