Your merchant-account application for the adult platform just came back declined, and the reason cited is generic: "high-risk content category." Meanwhile a sibling company running a mainstream subscription box under the same ownership sailed through underwriting in days. The difference is not your business quality; it is the Merchant Category Code and the registration layer that sits specifically on top of adult content.
An adult merchant account is not a slightly more expensive version of a standard merchant account. Card networks require a distinct registration step before your first transaction, price reserves in a wider and more front-loaded range than most high-risk categories, and expect documentation, performer consent, age verification, that no other vertical has to produce.
This guide covers the mechanics specifically: which MCC applies, what the mandatory registration involves, what reserves actually look like across the new-merchant curve, what documentation acquirers require before approval, and how a handful of 2025-2026 state-level rules now tie age verification directly to payment flows. For the broader bank-account-versus-merchant-account question, see BankMyCapital's adult merchant account vs business bank account guide; this piece goes one layer deeper, into merchant-account mechanics alone.
Direct Answer
An adult merchant account is a card-acquiring relationship for adult content or services, typically classified under MCC 5967 (Direct Marketing – Inbound Telemarketing) or MCC 7273 (Dating/Escort Services), and requires mandatory Specialty Merchant Registration under card-network adult-content rules before the first transaction. Expect reserves of 10 to 15% for new merchants, falling to 5 to 10% with a clean history.
Which MCC Applies to an Adult Merchant Account: 5967 or 7273?
MCC 5967 (Direct Marketing – Inbound Telemarketing) is the code most commonly used for adult content platforms: cam sites, subscription content, adult e-commerce. MCC 7273 (Dating/Escort Services) applies to adult businesses that sit closer to companionship or dating-adjacent services rather than content delivery.
The distinction matters because Visa and Mastercard underwrite the two codes slightly differently, and misclassifying your business, deliberately or by an underwriter's shortcut, creates a mismatch that a card-scheme audit can flag later, independent of how well you actually run the business.
What to Consider:
- Confirm which MCC your acquirer files under in writing, not just verbally at onboarding; get it in the merchant agreement.
- Match the MCC to your actual revenue model — a hybrid platform selling both subscription content and companionship-adjacent bookings may need separate entities rather than forcing one code to cover both.
- Expect an MCC change to require a fresh underwriting review, not a simple account update, if your business model shifts after approval.
Example
A subscription cam platform onboarded under MCC 5967 later added a paid video-call booking feature closer to a dating/escort model. The acquirer required a full re-underwriting under a blended risk file rather than treating it as a minor product update, adding six weeks to a planned feature launch.
Final Takeaway: Get your MCC classification confirmed in writing at onboarding, and revisit it any time your revenue model changes meaningfully.
Complete Specialty Merchant Registration Before Your First Transaction
Card networks require adult-content merchants to complete a Specialty Merchant Registration, a mandatory compliance filing confirming your business meets adult-content-specific rules, before the acquirer can process a single live transaction. Skipping or delaying this is one of the most common reasons an otherwise-approved account sits idle for weeks.
The registration typically requires confirming your age-verification process, your content-ownership and consent documentation, and your billing-descriptor practices, all before go-live, not after.
What to Consider:
- Start the registration in parallel with underwriting, not after approval, since it commonly adds its own multi-week timeline.
- Assign one internal owner for the registration paperwork; scattered ownership across compliance and product teams is the most common cause of delay.
- Keep a copy of your approved registration on file indefinitely; a lapsed or unclear registration status is a common trigger for a later acquirer review.
Example
An operator with a fully approved merchant account still could not process live transactions for three weeks because Specialty Merchant Registration had not been separately completed. The acquirer's compliance team, not the underwriting team, held that gate.
Final Takeaway: Treat Specialty Merchant Registration as a parallel workstream to underwriting, not a formality that follows approval automatically.
Understand the Real Reserve Tiers: 5-10%, 10-15%, and 15-20%
Reserves for adult merchant accounts sit on a wider curve than most high-risk categories. A new merchant with no processing history typically sees 10 to 15% withheld, held for 90 to 180 days. A merchant with a thin file, a new entity, or a recent MCC change, can see 15 to 20%. An operator with 12 or more months of clean chargeback data can often negotiate down to 5 to 10%.
| Merchant Profile | Typical Reserve | Typical Hold Period | Negotiation Path |
|---|---|---|---|
| New merchant, standard risk | 10-15% | 90-180 days | Renegotiate after 6-12 months clean history |
| Thin-file / recently changed MCC | 15-20% | 90-180 days | Build volume and dispute history before renegotiating |
| Established, clean chargeback history | 5-10% | 90-180 days, sometimes shorter | Maintain ratio below the acquirer's internal threshold |
What to Consider:
- Model your cash flow against the 15-20% band initially, even if your quote is lower, since a thin file is the default state of any new account.
- Ask what specific chargeback ratio unlocks a reserve reduction, and get that threshold in writing rather than treating it as a vague "good history" promise.
- Track reserve trend, not just level — a reserve that rises after a clean quarter is a signal worth escalating immediately.
Example
An operator new to card processing budgeted around a quoted 12% reserve, then discovered the acquirer's actual first-90-day rate was 18% pending a full chargeback-history review, a gap that required renegotiating a supplier payment schedule mid-quarter.
Final Takeaway: Plan around the higher end of the reserve range in your first year; treat any reduction as an outcome to earn, not a starting assumption.
Assemble the Documentation Acquirers Actually Require
Adult merchant-account underwriting requires two categories of documentation most other verticals never need to produce: written performer or model consent covering depiction, distribution and download rights, and a documented age-verification process, now including specific handling for AI-generated or synthetic content under 2025-2026 guidance.
Acquirers increasingly ask not just whether age verification exists, but how it is implemented and evidenced, since several jurisdictions now tie age-verification standards directly to payment eligibility. This documentation sits alongside, not instead of, the broader AML recordkeeping standards set internationally by the FATF, which most acquirers reference in their own compliance frameworks.
What to Consider:
- Keep signed consent records on file per performer, covering exactly what content and distribution rights were granted, not a generic release form.
- Document your age-verification method explicitly, including how it handles AI-generated or synthetic depictions, a distinction underwriters increasingly ask about directly.
- Refresh documentation on a schedule, not only when an acquirer asks; stale consent or verification records are a common review trigger.
Example
A platform's merchant-account renewal review flagged that its age-verification documentation had not been updated to address AI-generated content, a category the acquirer's own compliance checklist had added the prior year. Providing an updated written policy closed the review within a week.
Final Takeaway: Build a documentation refresh cycle into your compliance calendar rather than waiting for an acquirer's request to reveal a gap.
Track State-Level Rules Tying Age Verification to Payment Flows
A growing number of US states now write age-verification mandates directly into statute in a way that touches the payment flow itself, not just content-display rules. This is a meaningfully different compliance shape than a general content-labeling requirement: it makes your payment and access flow part of the legal compliance surface, not just the moderation surface.
For an adult merchant account, this means your checkout and access-gating sequence is not purely a product decision; it is something your acquirer's compliance review increasingly checks directly.
What to Consider:
- Map which states' rules actually apply to your user base, rather than assuming a single national policy covers every jurisdiction you serve.
- Build age verification into the access flow itself, not as a separate disclaimer page a user can skip past.
- Keep a jurisdiction-by-jurisdiction compliance log, since this area is still actively evolving and an acquirer review may ask when your policy was last checked against current state rules.
Example
An operator serving several US states discovered during an acquirer review that its access flow satisfied only a subset of applicable state age-verification requirements. Closing the gap required a checkout-flow change, not a policy memo, before the account renewal cleared.
Final Takeaway: Treat state age-verification-payment rules as a live compliance surface to monitor, not a one-time launch checklist.
Avoid the MATCH List: The Terminal Consequence in This Vertical
The MATCH list (Mastercard's Member Alert to Control High-Risk Merchants, also referred to as the TMF) is the industry's most commonly cited terminal consequence for adult merchant-account violations: a severe or repeated card-scheme rule breach can place your business's principals on this list, making a new merchant account meaningfully harder to obtain across acquirers industry-wide.
Reality Check
No provider, consultant or fee can remove a MATCH listing on request. Removal, when it happens at all, runs through the acquirer that placed you there and the underlying dispute that caused it, not through a paid service claiming special access. The only reliable strategy is not landing on the list in the first place: clean documentation, a monitored chargeback ratio, and a registration status kept current.
What to Consider:
- Treat every acquirer termination as a potential MATCH event, not a routine account closure, and ask directly whether the termination reason is being reported.
- Respond to a rising chargeback ratio before it triggers termination, since a proactively managed decline is a fundamentally different file than a scheme-driven termination.
- Keep your Specialty Merchant Registration and consent documentation current at all times, since a lapsed registration is itself a common trigger for the kind of termination that leads to listing.
Example
A platform that let its age-verification documentation lapse during a leadership transition was terminated by its acquirer for a compliance breach unrelated to chargebacks. The termination reason reported to the network complicated two subsequent merchant-account applications elsewhere.
Final Takeaway: MATCH-list avoidance is a documentation and monitoring discipline, not a recovery plan to build after the fact.
Adult Merchant Account: MCC 5967 vs MCC 7273 at a Glance
| Factor | MCC 5967 (Direct Marketing) | MCC 7273 (Dating/Escort Services) |
|---|---|---|
| Typical use case | Subscription content, cam platforms, adult e-commerce | Companionship or dating-adjacent booking services |
| Reserve treatment | Standard adult-vertical range, 10-15% new merchant | Similar range, often reviewed alongside recurring-billing pattern |
| Registration requirement | Specialty Merchant Registration required | Specialty Merchant Registration required |
| Common underwriting focus | Age verification, content consent | Identity verification, service-legitimacy documentation |
Conclusion: Compliance as a Standing Discipline, Not a One-Time Filing
An adult merchant account is governed by rules no other high-risk vertical fully shares: a mandatory registration step before your first transaction, reserve tiers that start wide and narrow only with a proven track record, and documentation, performer consent and age verification, that acquirers expect to see maintained continuously, not produced once at onboarding.
The businesses that keep their accounts stable treat compliance as a standing operational discipline: correct MCC classification, current registration, documented consent, and a chargeback ratio watched weekly rather than reviewed after a warning arrives.
None of this guarantees approval or protects against every scheme-level policy shift, but it is the difference between a merchant account that survives a difficult quarter and one that does not.
How BankMyCapital Helps
BankMyCapital is not a card acquirer, and does not review or hold content or client funds. On the merchant-account side, BMC assesses an adult operator's MCC classification, registration status and documentation readiness, then makes introductions to acquirers already active in the adult vertical, rather than filing cold applications likely to be declined on category alone. See BankMyCapital's payment processing service for how this connects to the wider banking and processing picture.