Adult Website Chargebacks: How Disputes Work

A chargeback is not a refund and it is not a support ticket. It is a formal process that runs between two banks under rules you did not write, with you as a supplier of evidence. Here is how a dispute on an adult membership site actually moves, and which parts of it you can change.

A dispute is a bank process

When a member disputes a charge, the first thing that happens is not that they contact you. They contact their bank. Visa's own description of the flow starts there: a charge is disputed, the bank reviews the charge, a temporary refund may be issued, the merchant is notified, the merchant responds, and a decision is made.

Notice where you appear in that list. You appear fourth. By the time the dispute reaches your inbox, a card issuer has heard one side of it, formed a first view, and in many cases put the money back on the cardholder's statement while it looks.

That is the most useful thing to understand about disputes: they are not a conversation with your customer. They are a submission into somebody else's process, on their deadline, in their format.

Who the parties are

Four parties sit in every card dispute, and it helps to keep them straight because each one wants something different.

The cardholder is your member. They have a statement in front of them, a charge they are unhappy about or do not recognize, and a bank with a phone number.

The issuer is the bank that gave them the card. Visa calls it the issuing bank, and it is the party that decides the dispute. The issuer's incentive is its own customer relationship, and it carries regulatory duties toward that customer that have nothing to do with you.

The acquirer is the bank that holds your merchant account. Visa calls it the acquiring bank. It notifies you of the dispute, it collects what you send back, and it passes your case to the issuer. It also carries the loss if you cannot cover refunds, which is why your dispute behavior is its business.

You, the merchant. You do not decide anything. You supply evidence.

Where the rules actually come from

Two layers sit on top of each other, and operators confuse them constantly.

The outer layer is law. In the United States, Regulation Z gives a cardholder a billing error procedure. Under 12 CFR 1026.13, a billing error includes an unauthorized extension of credit, a transaction the consumer cannot identify, and property or services "not accepted or delivered as agreed." The consumer's notice has to reach the creditor within 60 days of the first periodic statement showing the alleged error. The creditor then has to acknowledge in writing within 30 days and resolve within two complete billing cycles, and in no event later than 90 days.

The same regulation gives a second route. Under 12 CFR 1026.12(c), a cardholder may assert against the card issuer claims and defenses arising out of the transaction, but only if the cardholder "has made a good faith attempt to resolve the dispute with the person honoring the credit card," and subject to amount and distance conditions that do not apply when the merchant is the issuer or connected to it. That good-faith condition is worth reading twice, because it means a reachable support address is not only good manners.

The inner layer is card network rules — private operating rules between the networks, the banks and you, and where reason codes, evidence formats and deadlines live. We publish no thresholds, ratios or fee figures here: the authoritative versions live in documents your acquirer will hand you, and a number quoted from memory is worse than no number.

Reason codes, and what they are asking

Every dispute arrives attached to a code. The code is the question. Visa groups the causes plainly: fraud, authorization errors, processing errors, and customer disputes about goods or services not received or "not as described or faulty."

Those four groups ask genuinely different questions, and this is where adult operators lose cases they could have won.

• A fraud code asks whether the person who paid was the cardholder. Delivery evidence does not answer it.
• An authorization or processing code asks whether the transaction was taken correctly. Customer emails do not answer it.
• A consumer dispute code asks whether the member got what they bought, or whether a cancellation or refund you agreed to was actually processed. Your access logs, your terms and your cancellation record answer it.

Send the wrong evidence and you have not made a weak argument. You have made no argument, because nothing you sent addresses the question in the code.

Representment, and its limits

The step where you push back is called representment: your acquirer re-presents the transaction to the issuer with your evidence attached. Visa describes the merchant side of it as collecting evidence — receipts, confirmations, customer communications — and submitting it so the issuing bank can make a decision.

What representment can do is answer a factual question with a record. What it cannot do: argue that the member should have read the terms, substitute a general policy statement for evidence about this transaction, recover a dispute you have no logs for, or be filed after your acquirer's deadline, which is a hard edge rather than a guideline.

On an adult site there is a further constraint people find uncomfortable: the evidence you can send is limited by what you should be collecting in the first place. Screenshots of what a member watched are not a case file you want to be building. Timestamps, IP records, plan and price shown at checkout, the descriptor charged, the cancellation state and the support thread are.

Why recurring billing produces disputes

Subscription pricing and trials generate disputes for structural reasons, not because your members are dishonest.

A member signs up once and is charged repeatedly. Time passes. The charge lands on a statement beside businesses they use daily, under a descriptor they may not connect to anything. Trial pricing makes it sharper: the amount on the statement is not the amount they remember agreeing to, because the trial converted.

United States law speaks to exactly this shape of transaction. 15 U.S.C. 8403 sets three conditions before a person may charge a consumer in an Internet transaction through a negative option feature: disclose all material terms of the transaction clearly and conspicuously before obtaining billing information, obtain the consumer's express informed consent before charging the account, and provide simple mechanisms for the consumer to stop the recurring charges.

Read sideways, those three conditions are also a dispute-prevention checklist: disclosure before billing information is captured, consent recorded rather than assumed, and a stop mechanism the member can operate. We recommend building to them; what your own obligations are in your markets is a question for your counsel.

What a site can change

The dispute rules are not yours. The site is. The levers sit inside the build: the billing descriptor a member sees on their statement, the cancellation path, receipts and rebill notices, a refund policy you actually run, velocity checks and blocklists on the fraud side, and the logs that turn a dispute into a case file. Each of them is a design decision, and on most sites we are asked to look at, several are set wrong.

How each one should be set for your billing model is a call, not a blog post. We run this alongside the builds we operate — it is the Chargebacks & fraud line on our services list.

Questions we get

Is a chargeback the same as a refund?

No. A refund is a transaction you initiate. A chargeback is a reversal initiated through the cardholder's bank, and it is counted differently by your acquirer.

Can I stop disputes by making cancellation hard?

It works in the opposite direction. Regulation Z's claims-and-defenses route turns on whether the cardholder made a good faith attempt to resolve the dispute with you first, and 15 U.S.C. 8403 requires simple mechanisms to stop recurring charges. Friction moves the conversation to the bank.

Should I fight every dispute?

No. Fight the ones where the code asks a question your records answer. Where the member is right, refund and move on.

What are the ratio thresholds?

Card networks monitor dispute ratios, and the authoritative figures come from your acquirer and the networks' current published rules rather than from us. Ask your acquirer for the version that applies to your account.

Talk it through

If disputes are already a problem on your site, or you are designing billing and want the dispute surface small from the start, bring the specifics: how you bill, what your descriptor says, what your logs hold today and what your acquirer has told you. Book a call and we will go through it with you.

Sources

• — Visa, Chargebacks (Visa Acceptance Solutions)
• — 15 U.S.C. 8403, Negative option marketing on the Internet (Office of the Law Revision Counsel, U.S. House)
• — 12 CFR 1026.13, Billing error resolution (Regulation Z, Consumer Financial Protection Bureau)
• — 12 CFR 1026.12, Special credit card provisions (Regulation Z, Consumer Financial Protection Bureau)