Free architecture review on call one
paymentswithpaul_

August 5, 2026 · 8 min read

Adult Payment Processing: Registration, Content Rules, and the Descriptor Problem

Why adult is the card-brand-designated high-risk vertical: Visa and Mastercard registration, content compliance records, embarrassment-driven disputes, and the MID structure that lasts.

The email arrives from the acquirer, not the processor, and it is polite. The portfolio is being reviewed, the category no longer fits the bank's risk appetite, and the merchant has thirty days. Nothing in the account was wrong. Dispute ratios were inside program limits, the content library had documented consent records, and the last underwriting review passed without a single condition. The bank simply decided it did not want adult on its books anymore, and that decision was made several levels above anyone who has ever seen the merchant's numbers. Adult is the vertical where a clean operator still gets shown the door, because the pressure comes from reputation and program obligations rather than performance. This is a guide to what the card brands actually require, what the disputes really look like, and how to build a stack that treats a bank exit as a routing event instead of an extinction event.

Designated, not merely tolerated

Most high-risk categories are risky by inference. An underwriter looks at supplements or dropshipping, predicts the dispute pattern, and prices it. Adult is different, because the card brands name the category directly and impose obligations on the acquiring bank before a single transaction clears.

Visa treats adult content as high-integrity-risk under the Visa Integrity Risk Program, which replaced the older Global Brand Protection Program in 2023. Mastercard runs a parallel registration regime for the category. The practical effect is the same under both: your acquirer cannot quietly board you. It has to register you with the brand, pay per-merchant annual program fees, and carry documented monitoring duties for as long as you process.

That single requirement explains most of what merchants experience as unfairness. The pool of acquirers is small because most banks decline the administrative burden rather than price it. Approval is slower and more document-heavy, because the bank is attaching its own name to your file at the network. And pricing carries the registration fees plus the category's tail risk, so effective rates in the 4 to 8 percent range with a rolling reserve, commonly 5 to 10 percent held for six months, are normal for the vertical rather than evidence you were quoted badly.

Underneath the formal programs sits an informal filter that is harder to argue with. Sponsor banks derisk categories for reputational reasons that appear in no rulebook, which is why fully compliant adult merchants, including sellers of physical products with no content component at all, get declined by underwriters who never look past the MCC.

The content rules that end accounts fastest

If you operate a platform where anyone other than you uploads content, the compliance surface changes completely.

Mastercard's 2021 requirements for banks servicing adult content merchants moved the standard from "do not host illegal material" to "prove, per person, per piece of content, before publication." The expectations are documented age and identity verification for every performer depicted, documented consent for the specific content and its distribution, review of content before it goes live, and a complaint process with a defined takedown and appeal path. Visa's posture on content-sharing platforms tracks the same direction.

Two things follow that operators consistently underestimate.

The first is that this is an evidence problem, not a policy problem. Publishing a policy page costs an afternoon. Producing, on request, the verification record for a specific uploader and a specific clip from eighteen months ago is an infrastructure commitment, and it is the thing an acquirer will actually ask for when a complaint reaches the brand. Platforms that cannot produce it do not get a remediation window, they get removed from processing.

The second is that United States federal record-keeping law under 18 U.S.C. 2257 already imposes producer obligations, and payments compliance now sits on top of it rather than replacing it. Meanwhile the age-verification landscape for viewers has moved fast and is still moving: a growing set of US states require age assurance for adult sites, the Supreme Court upheld Texas's law in 2025, and the UK Online Safety Act brought its own age-assurance duties into force the same year. This is genuinely unsettled ground that varies by jurisdiction, so treat specific requirements as something to confirm with counsel for the states and countries you actually serve, and expect your acquirer to ask how you are handling it.

The disputes are about the statement, not the product

Adult's signature chargeback is not fraud and it is not dissatisfaction. It is a cardholder who made the purchase deliberately, then saw the line item on a shared statement and needed it to not be theirs.

That reframes what actually reduces disputes here.

A discreet, consistent billing descriptor is not a cosmetic decision in this vertical, it is the single highest-leverage control you have. The descriptor must be recognizable enough that the customer connects it to a purchase they remember making, and neutral enough that it does not describe the purchase to anyone else reading the statement. Send a confirmation email at the moment of sale that states the exact string that will appear, and put that same string on the site, in the receipt, and in the cancellation flow.

Trial-to-full conversions are the second cluster. Discounted entry pricing that rebills at the real price generates disputes from members who forgot the terms, so the renewal reminder and the cancellation path carry as much weight as the sales page. Account sharing produces a third cluster, where credentials get passed around, access gets throttled, and the complaint arrives as a services-not-rendered dispute.

Because your acquirer is registered with the brands on your behalf, you have less headroom than an unregistered merchant before a monitoring program takes an interest. Run your real numbers through the chargeback ratio explainer rather than eyeballing them, keep the chargeback reason code reference open while you build representment templates, and treat prevention alerts through Ethoca and Verifi as core infrastructure. An auto-refund rule on first-cycle disputes is close to free compared to what a chargeback costs you in fees and in ratio on a registered MID.

Three tiers, and only one of them is real here

Aggregator Registered high-risk MID Offshore acquiring
Will it board adult No, prohibited outright Yes, with brand registration Yes, deep specialist appetite
Underwriting focus None at signup Content compliance, age and consent records, billing terms Varies, often lighter
Reserve None, then a 90 to 180 day hold Rolling, commonly 5% to 10% Often higher
Behavior under scrutiny Freeze and terminate Notice, remediation, adjusted terms Varies by acquirer
Realistic role None Primary processing Redundancy and non-US volume

Stripe, PayPal, and Square all prohibit adult outright, which puts them further out of reach than they are for verticals where enforcement merely arrives after the fact. Anyone processing adult volume on those platforms is doing so under a business description that does not match the business, and the deferred underwriting pattern is at its worst in that situation. When the review comes, the finding is not a rising dispute rate, it is misrepresentation at onboarding, which is the termination most likely to end in a MATCH listing that follows the principal for five years.

Offshore acquiring is a genuine part of this vertical rather than a last resort, because several specialist acquirers have served adult for decades and understand it better than most domestic banks. The honest trade is higher pricing, larger reserves, settlement in another currency, and cross-border interchange that can shave approval rates on domestic cards. It belongs in the stack as redundancy and as a home for non-US volume, not as the whole stack.

Architecture for a category that gets exited

Plan for the failure mode this vertical actually produces. You are less likely to be terminated for cause than to be handed a notice period because your sponsor bank left the category, and every registered merchant on that bank starts shopping the same week.

Three things make that survivable.

Run a primary and a backup MID at separate acquiring banks and split live traffic across both using the approach in the MID load balancing guide, so a bank exit costs capacity rather than continuity. Keep card credentials in a processor-neutral vault, as described in the token vault explainer, because a recurring membership base you cannot re-point without emailing every member for their card details is a base you will mostly lose. And keep your compliance record portable: consent and age verification files, takedown logs, and dispute evidence should live in systems you control, so the next underwriter can be satisfied in days rather than months.

Practical takeaway

Adult is not hard to bank because of what it sells. It is hard to bank because the card brands require your acquirer to register you rather than merely approve you, because content platforms carry per-performer verification duties that are evidentiary rather than declarative, because the dominant dispute is a cardholder hiding a purchase they meant to make, and because sponsor banks exit the category for reasons that have nothing to do with your file. The operator who lasts registers properly through an acquirer that already runs an adult portfolio, keeps verification and takedown records retrievable on demand, engineers the descriptor and the receipt as dispute-prevention tools, runs prevention alerts with a first-cycle refund rule, and holds a second MID at a second bank with a processor-neutral vault behind both. The operator who fails routes volume through an aggregator under a vague descriptor, treats compliance as a published page instead of a queryable record, and loses the balance, the membership base, and five years of clean underwriting in one notice period. For a walkthrough of what a durable adult payment stack looks like at your volume, apply for an architecture review.

About the author

Paul Madut designs payment infrastructure for high-risk ecommerce brands: token vaults, MID load balancing, and offshore routing for merchants processing $50K+/month.