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

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 sat inside program limits, the content library had documented consent records, and the last review passed clean. The bank decided it did not want adult on its books, several levels above anyone who has seen the merchant's numbers. Adult is 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 require, what the disputes really look like, and how to build a stack that treats a bank exit as a routing 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, and Mastercard runs a parallel regime. The practical effect under both is that 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 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, and approval is slower because the bank is attaching its own name to your file at the network. Pricing carries the registration fees plus the category's tail risk, so effective rates of 4 to 8 percent with a rolling reserve, commonly 5 to 10 percent held for six months, are typical rather than evidence you were quoted badly.

Underneath the formal programs sits an informal filter: sponsor banks derisk categories for reputational reasons that appear in no rulebook, which is why compliant adult merchants, including sellers of physical products, 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 before it goes live, and a complaint process with a defined takedown and appeal path. Visa's posture tracks the same way.

Two things follow that operators 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 clip from eighteen months ago is an infrastructure commitment, and it is what an acquirer asks for once a complaint reaches the brand. Platforms that cannot produce it get removed from processing rather than a remediation window.

The second is that US federal record-keeping law under 18 U.S.C. 2257 already imposes producer obligations, and payments compliance sits on top of it rather than replacing it. Age verification for viewers has meanwhile moved fast and is still moving: a growing set of US states require age assurance, the Supreme Court upheld Texas's law in 2025, and the UK Online Safety Act brought its own duties into force the same year. Confirm specifics with counsel for the jurisdictions you 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 cosmetic in this vertical, it is the single highest-leverage control you have. The string has to pass two tests that pull against each other: recognizable enough that the cardholder connects it to a purchase they remember, neutral enough that it describes nothing to anyone else reading the statement.

The failure mode is almost always the first test: merchants reach for something so generic that it reads as unfamiliar, and an unfamiliar line item is precisely what a cardholder disputes. A neutral trading name paired with a working support number or URL inside the character limit does more than either half alone, and the mechanics, including truncation and how the soft descriptor differs from the hard one, sit in the billing descriptor guide. Whatever you settle on has to appear everywhere: the checkout page, the confirmation email, the receipt, the cancellation flow, and your support macros. A descriptor the customer was shown before the charge posts is one they rarely dispute.

Trial-to-full conversions are the second cluster, where discounted entry pricing that rebills at the real price generates disputes from members who forgot the terms, so send the renewal reminder before the card is charged and make cancelling take no more clicks than subscribing did. Account sharing is the third, where credentials get passed around and the complaint arrives as a services-not-rendered dispute, which makes concurrent-session limits a dispute control as much as a licensing one.

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 against the enrollment thresholds in the Visa and Mastercard monitoring programs explainer and treat prevention alerts through Ethoca and Verifi as core infrastructure, not an optional line item. An auto-refund rule on first-cycle disputes is close to free next to what a chargeback costs in fees and in ratio.

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 prohibit adult outright, so anyone processing adult volume there does so under a business description that does not match the business. 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, 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, foreign-currency settlement, and cross-border interchange that can shave approval rates on domestic cards, which makes it redundancy and a home for non-US volume rather than the whole stack.

Architecture for a category that gets exited

Plan for the failure mode this vertical actually produces: not a termination for cause, but a notice period because your sponsor bank left the category, with every merchant on that bank shopping the same week.

Three things make that survivable.

The first is a primary and a backup MID at separate acquiring banks, with live traffic split across both so a bank exit costs capacity rather than continuity. A backup that has never seen a transaction is not a backup, because an untouched account gets closed for dormancy or fails on the day you need it, so send it a steady minority share from the start. The routing layer that makes this practical is covered in the payment orchestration guide.

The second is credential neutrality, the part merchants skip and then cannot recover from. If the stored card sits inside one processor's vault, a membership base you cannot re-point without emailing every member for their card details is one you will mostly lose, so hold the credentials somewhere neither acquirer controls and confirm you can export them.

The third is a portable compliance record: consent and age verification files, takedown logs, and dispute evidence belong in systems you control rather than a vendor's admin panel, 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 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 for reasons unrelated to your file. The operator who lasts registers through an acquirer that already runs an adult portfolio, keeps verification and takedown records retrievable on demand, engineers the descriptor and receipt as dispute-prevention tools, and holds a warm 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.