All articles

Merchant of record or payment facilitator: what actually decides which one you can use

9 min read

The search starts the same way for most operators building a payment stack: a comparison article, usually written by a payments company, laying out merchant of record against payment facilitator like two items on a menu, each with its trade-offs, pick whichever suits the business. The problem shows up only after signup, during underwriting, when the provider's own compliance team reads the word escort, dating, or adult in the business description and closes the application without explanation. The comparison was never wrong about the trade-offs. It was wrong about which options were actually open before the trade-offs became relevant.

That gap costs real time. An operator who spends two weeks comparing fee schedules between a merchant-of-record provider and a payment facilitator, only to be rejected by the first one at underwriting, has lost two weeks they could have spent on the one question that actually mattered: which of these models will even look at an adult classifieds business, and what happens operationally once one of them says yes.

Most of what gets written about this choice is aimed at a software founder deciding whether to let a vendor handle VAT across thirty countries. None of it is wrong for that reader. It is simply answering a question an adult classifieds operator was never going to get to ask, because the eligibility screen closes the conversation before the fee comparison starts. The order matters: settle eligibility first, then compare terms among whatever is actually left.

What the two models actually do

The distinction comes down to one question: who is legally responsible for the transaction. A merchant of record becomes the legal seller of what's being sold. It's the name on the customer's bank statement, the party that collects the payment, and the entity responsible for calculating, collecting, and remitting sales tax across every jurisdiction it sells into. It handles refunds and chargebacks directly, and it absorbs the compliance and fraud liability that would otherwise sit with the underlying business. In exchange for taking on all of that, a merchant of record charges a meaningfully higher percentage than a standard processor; the liability transfer is priced into the rate.

A payment facilitator works differently. It gives a business fast access to card acceptance by onboarding it as a sub-merchant under the facilitator's own master merchant account with an acquiring bank, which is what makes signup quick compared with building an independent merchant account from scratch. The underlying business stays the legal seller, though. Tax calculation, remittance, and most regulatory compliance remain on the merchant's own books; the facilitator's liability runs toward its acquirer, for onboarding, monitoring, and transaction risk on its whole portfolio, not toward the end customer's tax authority.

A third structure sits underneath both: a direct, dedicated merchant account, where a business applies for its own merchant ID with an acquiring bank or a specialist processor built around high-risk categories. It is slower and usually more expensive to set up than a payment facilitator's instant onboarding, and it carries none of a merchant of record's tax and liability transfer. What it changes is who is actually looking at the application: an acquirer underwriting one specific business individually, rather than an automated risk engine tuned to flag an entire portfolio of unrelated sub-merchants.

Why merchant of record is not actually on the menu

Paddle is one of the best-known merchant-of-record providers for software and digital goods, and its acceptable use policy, published on its own help center, is specific about what it will not touch. It lists, as a prohibited category, "adult and other age-restricted content and services, including sexually-oriented or pornographic products or services, any material of a lewd and lascivious nature, dating services/applications, or any other products/services intended for this industry." Travel reservation services and timeshares are prohibited in the same list, for similar reasons. This is not a gap in the policy. It is the policy doing exactly what it was written to do.

The same document goes further than excluding adult businesses as customers. It separately prohibits any business that is itself "a regulated financial product or service," naming payment facilitators, payment service providers, money transmitters, and other merchants of record specifically. A business that already processes payments on someone else's behalf cannot become a customer of a merchant of record either. The model does not stack, and that detail matters for a classifieds directory weighing whether to become some kind of intermediary for its own advertisers' payments: that route runs into the same wall from the other direction.

The logic underneath both exclusions is the same. A merchant of record is only willing to become the legal seller, and absorb full chargeback and tax liability, when the underlying risk is low and well understood in advance. That is exactly what an adult classifieds business is not, by the standards a merchant-of-record provider uses to price its own exposure. The exclusion is not a technicality an operator can negotiate around with a bigger deposit or a longer sales call; it describes the category the provider's entire pricing model depends on avoiding.

For an adult classifieds operator, this means merchant of record is not a real option to weigh against the alternatives on price or features. It is a door that is shut before the comparison starts, and the useful move is to stop spending time on it and ask the next question instead: which of the remaining models can actually process the business.

Why a generic payment facilitator is not an automatic fallback

The instinct, once merchant of record is off the table, is to assume a payment facilitator must be the answer by elimination. Stripe's own prohibited and restricted businesses list, published on its legal page and updated regularly, shows why that instinct is premature. It lists "adult services, including prostitution, escorts, pay-per-view, sexual massages, fetish services, mail-order brides, and adult live-chat features" as outright prohibited, alongside pornography and AI-generated content meeting the same description. Generic online dating is treated differently: it sits in a separate restricted category, which means the business is reviewed and can be approved with extra due diligence rather than refused on sight, though the policy also names country-specific bans on dating in several markets.

The same page lists "payment facilitation and aggregation" itself, including receiving settlement proceeds on behalf of third-party sellers, as a restricted category requiring its own additional review. That detail matters for a classifieds directory considering whether to act as a sub-facilitator for its own advertisers, splitting payouts the way some marketplace platforms do: the facilitator sitting underneath that arrangement has to clear the same bar the directory is trying to clear itself.

A generic, mass-market facilitator like this is built to process a huge portfolio of unrelated sub-merchants using automated risk tools tuned for low-dispute categories. An account that clears onboarding is not necessarily in the clear afterward: the same automated monitoring that approved the signup keeps watching the account, and a facilitator managing portfolio-wide exposure to its own acquirer can decide to tighten or exit a whole category at once, not just act on individual accounts that misbehave. Visa's Integrity Risk Program reaches the acquiring bank or payment facilitator sponsoring the account, not only the individual merchant, which is part of why that kind of portfolio-level exit happens in the first place.

It would be convenient if the fix were simply to skip the generic facilitator and get a direct merchant account with a specialist high-risk acquirer instead, one that underwrites the business individually and is built around the category long-term. That changes who reviews the account and how, which is real and worth having. It does not make the business immune to the same pressure. In 2023, a payment service built specifically to serve the adult industry, processing crypto payments for adult content creators, shut down entirely after its own upstream payment processor terminated the relationship over network rule violations; its operators said afterward that no other processor would take the business except at fees too high to use. Specializing in a category changes who underwrites the business day to day. It does not remove the category from the card networks' and banking partners' own risk decisions, because every processor in this space, generalist or specialist, still settles through the same networks and banks.

What to actually ask before signing

Because neither path offers real insulation, the useful questions are not about finding the option that is permanently safe. They are about understanding, before signing, exactly what kind of relationship is being entered into and what happens if it ends. Start with the simplest one: does the agreement name the provider as the merchant of record, or does it name the business itself as the merchant, with the provider acting only as a payment facilitator or acquirer. If the business's own name is what will appear on the merchant ID and the card statement, merchant-of-record pricing and liability transfer do not apply, whatever the sales material implies.

Next, ask whether the business is being onboarded as a sub-merchant under someone else's master account, or whether it is getting its own direct merchant ID. A sub-merchant arrangement is usually faster and cheaper to start, but the account's fate is tied to the facilitator's entire portfolio and that facilitator's own standing with its acquirer and the card networks, not only to the business's individual record. A direct merchant ID is reviewed on the business's own numbers, which is worth the slower and costlier setup for an operator planning to run the business for years rather than months.

Ask who holds the reserve against future chargebacks, under what schedule it releases, and whether that schedule is written into the agreement or left to the provider's discretion. How much of each settlement gets held back, and for how long, is a detail many operators only learn after the first smaller-than-expected deposit arrives, and it is far easier to negotiate before signing than to renegotiate afterward.

Finally, ask what happens to funds already in transit if the provider decides to exit the category rather than simply close the account for cause, and whether being dropped for a category-wide exit carries the same consequences as a termination that lands the business on a shared blacklist other acquirers check before approving a new application. The answers rarely change which provider an operator ends up choosing. They change how much warning there is before the next move becomes necessary, and that warning is the only real advantage either model has to offer in a category where no processing relationship is guaranteed to last.

None of this adds up to a reason to delay getting a payment stack in place. It is a reason to spend the first phone call asking about eligibility and account structure instead of rates, and to keep a second option, even an unsigned one with paperwork mostly ready, somewhere in reserve. A classifieds directory that treats its processor as permanent will eventually be surprised by it. One that treats the relationship as the best available arrangement for now, with a documented fallback, loses a few days switching providers instead of losing the business while it scrambles to find one.

Try the DEMO

Escort directory software, ready to go