Chargebacks in adult classifieds: what actually threatens your merchant account

The chargeback problem is not what people assume

Most operators think of a chargeback as a cost line: a few euros lost when a customer's bank sides with them over a purchase. That is the smallest part of what a chargeback actually does. Every dispute is also a data point that Mastercard and Visa read about the merchant, not just about the transaction, and it is invisible until enough of those points line up and close the account that the whole business runs on.

The distinction that matters is between stolen-card fraud and disputed billing, and in a listings business almost everything you will deal with is the second kind. Someone signs up, pays with their own card, uses the listing, and then disputes the charge anyway. They recognize the amount. They recognize making the purchase. The bank does not ask why before opening a case, and neither does the ratio that a chargeback adds to.

This hits an adult directory harder than most shops for a simple reason: the business is already classified as high risk, which means the margin for error was thin before a single dispute arrived. The ratios that card networks watch are calculated against total transaction volume, and a new directory does not have much volume. A dozen disputes that would round to nothing at a supermarket chain can be enough to move the needle on a business processing a few hundred payments a month.

The stakes are not a fee. Getting a merchant account approved in the first place already takes weeks of paperwork with an underwriter who does not have to say yes. Losing one over a bad chargeback ratio means going through that process again, this time with a closed account on the record that the next underwriter will ask about, while no card payment clears in the meantime. The business that depends entirely on one merchant account is one flagged month away from a gap it cannot bill through.

What actually drives disputes in a listings business

The single most common driver is recurring billing that the payer forgot about. An advertiser signs up for a weekly or monthly package, the listing keeps running, and a month later a charge appears that they no longer connect to a deliberate decision. The reflex is not to write to support and ask what it was. The reflex is to call the bank and say they do not recognize it, because that path is faster and costs the payer nothing.

The second driver sits on the statement itself. If the name that appears next to the charge is a generic code that means nothing to the person looking at their banking app, they will not recognize it a month after the purchase, and an unrecognized line is disputed on reflex far more often than a recognized one. This single detail, tested on an actual card statement rather than assumed from what the payment provider's dashboard shows, resolves more disputes before they happen than any policy written afterward.

The third driver has nothing to do with fraud and everything to do with discretion. Some payers dispute a charge they made deliberately simply because they would rather not explain it if someone else reviews the same statement, and disputing costs them nothing while asking for a refund would require writing to you first. This pattern shows up across the whole high-risk category, not only in this one, and no verification step catches it because the person really did make the purchase.

The fourth is the easiest to fix and the one operators leave for last: a refund path that does not exist or is hard to find. If the fastest way to get money back is a form nobody can locate, the bank becomes the fastest way to get money back instead, and every one of those calls becomes a chargeback that a two-line reply could have prevented.

The two thresholds a processor is actually watching

None of this is your payment provider's personal opinion. Mastercard and Visa each run a monitoring program that reads a merchant's dispute ratio directly, independent of what your processor decides on its own, and processors set their own internal limits well below the network's so they get to act before the network forces them to.

Mastercard's rule is public and specific: a merchant enters the Excessive Chargeback Merchant program when it records at least 100 chargebacks in a calendar month and a chargeback-to-transaction ratio of 1.5% or higher, with both conditions required at once, not either one alone. A worse tier applies at 300 chargebacks and a 3% ratio. The ratio itself is not measured against the same month's sales; it compares the current month's disputes to a recent month's volume, so a slow month that follows a strong one can push the number up on paper even though nothing about how the business is run has changed. Getting out again takes three consecutive clean months, not one.

Visa runs a comparable program of its own, and its published thresholds have gotten materially stricter over the past two years rather than looser, with real fines attached once a merchant is flagged and an account review that follows. The underwriting questions a processor asks before approving an adult business in the first place exist largely because the processor is trying to keep its whole portfolio under these same network thresholds, and a merchant with a clean dispute history is the reason a processor stays comfortable renewing instead of reviewing.

The practical translation is that a bad month does not announce itself while it is happening. The ratio that puts a merchant into a monitoring program is calculated after the month closes, using data the merchant usually cannot see in real time, which means the only reliable defense is watching the count of disputes as they arrive rather than waiting for a report that already reflects a decision made weeks earlier.

Alerts, evidence and the habit of fighting back

Two services exist specifically to catch a dispute before it becomes a chargeback: Ethoca, owned by Mastercard, and Verifi's CDRN, owned by Visa. Both work the same way. When a cardholder complains to their bank, the alert reaches the merchant first, typically with about a day to act, and a refund issued inside that window stops the case from ever being filed as a formal chargeback, which means it never touches the ratio at all. For a business whose income runs almost entirely over card rails, subscribing to at least one of these is one of the cheapest ratio-protection measures available, and it only works if someone is actually watching the queue every day rather than checking it when there is time.

These alert services are not free, and most charge per alert regardless of what happens next, so the decision to subscribe is worth running against your own dispute count rather than assuming it pays for itself. In a small team, the person best placed to watch that queue every day is usually the one who already reviews the identity verification queue, because both jobs come down to the same skill: recognizing an ordinary account from one that needs a closer look before it turns into a problem you cannot undo.

Not every dispute is worth catching that way, and some are worth fighting properly instead of refunding on sight. Representment, the formal response that contests a chargeback with evidence, wins when the merchant can show the charge was authorized and the service was delivered as described: a timestamped record of the terms the advertiser accepted, the IP address and time of signup, the login history showing the listing was actually used, and any support correspondence tied to that account. Much of this overlaps with the records a directory already keeps for identity verification, and the two record-keeping habits are worth designing together rather than as separate systems, since the retention period that protects you in a dispute is not automatically the same one that a data-privacy rule allows.

Fighting every dispute regardless of the odds is its own mistake. Representment takes staff time whether it succeeds or not, so the working rule is simple: refund immediately when the story is plausible and the amount is small, and reserve the fight for cases with real evidence behind them and enough money at stake to justify the hours.

What to do, in order

Start with the statement descriptor, because it is the one fix that touches every future transaction at once. Buy something small on the account yourself and read exactly what your own bank shows, then change it if it would confuse you.

Next, make asking for a refund at least as easy as making the original payment: one visible link, one short form, and a person who reads it the same day it arrives, because every hour that path stays hidden is another chance that a customer calls their bank instead.

Then put someone in charge of the number itself. Subscribe to an alert service if the volume justifies the cost, check the dispute count weekly rather than waiting for the monthly statement, and treat the ratio as a metric that gets reviewed on a schedule, the same as revenue or traffic, not something that only gets attention after a warning letter arrives.

Write down what happened after any month the ratio moves, even if it stays under threshold. A short note on what changed, which fix was tried, and whether it worked turns a scare into a record you can hand to a new processor if you ever need one, instead of a vague memory that a bad patch happened once and got better on its own.

Finally, keep a second merchant account relationship warm even when the first one is healthy. A clean month does not guarantee the next one, a card network can tighten a threshold with no warning, and the difference between a business that survives a flagged month and one that does not is usually whether a second way to collect payment already existed before the first one needed it.