nsfwdev.com

Blog · Payments

Adult Merchant Accounts: How High-Risk Underwriting Works

How an adult merchant account is actually underwritten: who decides, what banks look at, and what an integrator can and cannot do about the answer.

Getting card payments onto an adult site is an underwriting exercise, not a signup form. Here is who actually decides, what they read before deciding, and where an integrator helps compared with where the bank has the only vote.

Why "high risk" is a category, not an insult

An adult merchant account sits in a bucket that card networks and banks treat differently from a coffee subscription. The reasons are structural rather than moral: recurring billing produces disputes, subscription products produce cancellation confusion, digital goods cannot be proved delivered the way a tracked parcel can, and the category carries brand rules the networks apply on top of ordinary risk.

That combination is why most mainstream payment aggregators exclude adult content in their acceptable-use terms and decline the application on category grounds before anyone looks at your site. It is not a judgment on your business. It is a decision their bank made about their whole portfolio.

The practical consequence is that adult operators work with providers who specialize in the category, and with acquiring banks who have chosen to write that business.

Who decides what

Three parties are usually involved, and only one of them approves you.

The acquiring bank

The acquirer holds the merchant account, carries the loss if you disappear owing refunds, and answers to the card networks for your portfolio behavior. The acquirer decides whether you are approved, on what rates, with what reserve, and under what volume caps. That decision belongs to them alone. No integrator, agency or reseller can make it for them, and anyone who tells you otherwise is selling something.

The payment service provider or gateway

The provider sits between your site and the acquirer. Several established providers publish that they serve high-risk and adult businesses on their own sites. CCBill describes helping businesses "set up online payments" and names adult industry expertise among its services. Segpay publishes that since 2005 it has helped businesses take payments "while implementing a compliance framework, with the controls necessary to secure a merchant account of their own." Verotel leads with "Processing Payments for High-Risk Webmasters." NETbilling describes payment processing "for E-commerce, Retail, Mobile, And Most High-Risk Businesses" and says it has partnered with banks to offer merchant account and transaction processing options.

We name those as examples of what the landscape looks like, not as recommendations, and we do not publish which providers we use on client accounts. The right fit depends on where you sell, which currencies you take, whether you rebill, and what the acquirer behind that provider is willing to write.

The integrator

That is our part of the job. We prepare the application, build the site so it matches what was underwritten, integrate the gateway and its webhooks, and run the dispute and fraud work afterwards. We describe the work on the services page under Payment processing and Chargebacks & fraud. We do not approve anything, and we do not set your rate.

What underwriters read before they answer

Underwriting is mostly document review plus a careful look at your live site. The recurring themes:

  • Business documentation. Who owns the company, where it is registered, banking details, and identification for the beneficial owners.
  • The site itself. Clear pricing, an obvious cancellation path, a support contact that works, terms and a privacy policy, and a billing descriptor a cardholder will recognize on a statement.
  • Content policy and moderation. What you publish, what you refuse, how user submissions are reviewed if you accept any, and how takedown requests are handled.
  • Record keeping posture. For US producers, 18 U.S.C. 2257 requires records of performer identity and date of birth, and a statement affixed to the material describing where those records are kept, including on "every page of a website" where the covered material appears. Underwriters look for a business that treats this as routine.
  • Age verification. Which territories you sell into, and what gate stands in front of the content there.
  • Processing history. Prior accounts, prior closures, dispute ratios if you have them, and projected volume and average ticket.
  • Refund and dispute handling. Who answers a confused customer before they call their bank.

None of that is exotic. It is the file a risk officer needs in order to say yes without personally carrying the consequence.

Keeping the account after the yes

Approval is the start of the relationship, not the end of the question. Dispute ratios are monitored, and an account with a rising ratio attracts attention from the acquirer and from the networks before it attracts anything worse.

The work that keeps ratios sane is unglamorous and mostly preventive, and it is set per site: how the statement line reads, how cancellation works, when a refund is the right answer, what the fraud controls watch for, and how a dispute file is put together. That is the part we run day to day, and it is why it sits on the services list next to the build itself. How it should be set for your billing model is a conversation, not a checklist.

Questions we get

Can approval be promised in advance?

No. The acquirer makes that call after reading the file, and the answer depends on your documentation, your site, your category and their own appetite at that moment. What can be done is preparing a complete, accurate application and building a site that matches it. Any offer of certain approval is a claim the person making it is not in a position to keep.

How long does underwriting take?

It varies by acquirer, by country, and mostly by how complete your file is on the first pass. Missing documents are the usual reason a file sits. We do not quote a number here because the number is not ours to set.

Can I use a mainstream provider if my content is fairly soft?

Read that provider's own acceptable-use terms before building anything on them, and ask them directly in writing. Category rules are usually written broadly, and a decline after launch is worse than a decline before it.

What is a rolling reserve?

A portion of settled funds the acquirer holds back for a period to cover future refunds and disputes. Whether one applies, how large it is, and how long it runs are terms the acquirer sets. They are worth understanding before you model cash flow.

Do you take payments on our behalf?

No. The merchant account is yours, in your business name, with the money settling to your bank. We build and run the plumbing around it.

Talk it through

If you are working out how payments will actually run on your site, bring the specifics: what you sell, where your buyers are, how you want to bill, and anything that has gone wrong before. Thirty minutes is usually enough to map the route and the realistic sequence. Book a call and we will walk through it with you.

Sources

Read next

Compliance

2257 Compliance for a Paysite: What It Requires

What 18 U.S.C. 2257 asks of a producer: the records, the custodian, the statement on every page, primary versus secondary producer, and where counsel decides.

Distribution

DMCA Takedowns for Adult Creators

What a DMCA takedown notice must contain, why a paysite registers a designated agent, how counter-notices work, and the practical loop of finding leaks.

Let's build yours.

A 30-minute call. We'll tell you what it costs and how fast we can launch.

Book a call