Dating Site Chargebacks: Fighting 'I Cancelled' and Fraud Claims
Dating site chargebacks often start with a forgotten renewal. See which evidence wins each dispute code, and when a refund costs you less than fighting.

Photo: Pixabay
On this page 7 sections
- The Dating Subscription Disputes You'll Actually See
- Answer Each Dispute Code With Its Own Evidence
- When Visa Compelling Evidence 3.0 Applies to a Member
- Using Login, Messaging and Profile Activity as Evidence
- Proving Renewal Notice and Cancellation Access
- When Refunding Beats Fighting a Dating Subscription Dispute
- Keeping Dating Site Chargebacks Below Visa and Mastercard Thresholds
Key takeaways
- A monthly member needs about five months of billing history before Visa's Compelling Evidence 3.0 can answer a fraud claim. Annual renewals alone never create the two qualifying charges.
- On Mastercard, winning a chargeback doesn't remove it from your Excessive Chargeback count. Only disputes you prevent stay off the books.
- With an illustrative $34.99 monthly plan and a $25 dispute fee, you have to win about 71% of cases just to break even.
- Send activity counts and timestamps as evidence, never message content. Members who don't know deleting the app doesn't cancel the plan are a dispute you can prevent.
Dating site chargebacks mostly come from three stories: the member forgot the plan renews, the member regrets an upgrade, or a partner found the charge and the cardholder called their own purchase fraud. Renewal disputes are winnable when you can show the renewal was disclosed and the member kept using the account after the charge posted. Fraud claims turn on login and device data that tie the purchase to the cardholder, and when you don't have those records, a fast refund usually costs less than the fight.
Dating is a hard category for disputes because the product is personal. Members often go straight to their bank without contacting you, and some would rather not admit the subscription exists at all.
The Dating Subscription Disputes You'll Actually See
Each story lands in a different dispute category, and the category decides which evidence the issuer will read. On Visa, "I cancelled" claims usually arrive as reason code 13.2, Cancelled Recurring Transaction, part of Visa's Consumer Disputes group. Mastercard's equivalent for consumer disputes is its Cardholder Dispute code, 4853.
| What the cardholder says | Likely dispute category | Evidence that answers it |
|---|---|---|
| "I cancelled" or "I didn't know it renewed" | Visa 13.2 Cancelled Recurring; Mastercard 4853 | Renewal disclosure, reminder email, no cancellation on file, activity after renewal |
| "I deleted the app months ago" | Visa 13.2; Mastercard 4853 | Help pages and receipts saying deletion doesn't cancel; an empty cancellation log |
| "I paid for premium and got nothing" | A consumer dispute (not as described or not provided) | Logs showing premium features were delivered and used |
| "I don't recognize this charge" | Card-absent fraud (Visa 10.4) | Device and IP data matching the account; earlier undisputed purchases |
| A stolen card used by someone else | Fraud | Usually nothing worth filing. Accept it and block the account |
The deleted-app dispute is the one dating merchants lose most avoidably. Many members assume removing the app ends the subscription. If your help pages and renewal reminders don't say otherwise in plain words, a reviewer will side with the member even when your terms technically cover it.
The partner-found charge is frustrating because the cardholder really did buy the subscription. Your discreet billing descriptor for a dating site has to balance the member's privacy against enough recognition that they don't dispute their own purchase. Regretted upgrades often come from add-ons: a boost bought late at night, then a "not as described" claim when no matches follow. How you handle billing for boosts, roses and credits decides how defensible those charges are.
Answer Each Dispute Code With Its Own Evidence
Merchants often build one large evidence packet and send it for every dispute. That buries the strongest material, and the deadlines are short. Under Visa's rules, a cardholder has up to 120 days to raise a 13.2 dispute, and the merchant has 30 days to respond. Mastercard gives cardholders 120 days and merchants 45 days to respond with representment evidence. Your processor will usually want your file earlier than the network deadline, so ask for its internal cutoff.
For a cancelled-recurring claim, the issuer wants two answers: did the cardholder cancel before the renewal, and were the renewal terms disclosed? Your cancellation log showing no request answers the first. Proof the member kept using the account after the renewal posted contradicts the claim directly, because someone who cancelled doesn't log back in the following week to send messages.
Fraud claims are about identity, so disclosures and cancellation records don't help. What helps is showing that the person who bought the plan was the cardholder.
When Visa Compelling Evidence 3.0 Applies to a Member
Visa's Compelling Evidence 3.0 (CE 3.0) rules let a merchant answer a 10.4 card-absent fraud dispute with purchase history. Per published summaries of the rule, you need two earlier undisputed transactions on the same card, each processed more than 120 and no more than 365 days before the dispute. At least two data elements must match across all three transactions, drawn from account or login ID, delivery address, device ID or fingerprint, and IP address, and one of the two matches must be the IP address or device ID.
Here is the part generic guides skip: your billing interval decides whether a member can ever qualify. Take three illustrative members, each disputing a renewal as fraud, with the dispute dated September 20, 2026. The qualifying window runs from September 20, 2025 to May 23, 2026.
| Member | Plan and start date | Prior charges in the window | CE 3.0 possible? |
|---|---|---|---|
| A | Monthly, joined April 1, 2026 | April 1 (172 days) and May 1 (142 days) | Yes, if the data matches |
| B | Monthly, joined May 1, 2026 | May 1 only; June 1 is 111 days old | No |
| C | Annual, joined September 1, 2025 | None; the first charge is 384 days old | No |
Assumptions: renewals bill on the 1st, the same card is used throughout, and no other purchases were made. So a monthly member generally needs about five months of history before CE 3.0 is available, and a member who renews once a year never builds two qualifying charges from renewals alone. Add-on purchases change that. A boost bought on the same card in the window counts as a transaction, which is one more reason to capture IP and device ID on every purchase, not only at signup. Watch the edge, too: one published summary notes that Stripe's API documentation states the window as 120 to 364 days, so ask how your processor counts it.
Before you build templates, ask your processor whether its dispute portal accepts CE 3.0 data fields and how it submits them.
Using Login, Messaging and Profile Activity as Evidence
Dating platforms log a lot of member behavior. Strong activity evidence includes:
- Login timestamps with IP address and device ID, especially after the renewal or after the date the member says they cancelled
- Counts of messages sent and received, with dates
- Profile edits and photo uploads
- Likes or swipes during the billing period
- Use of paid-only features, such as seeing who liked them or sending priority messages
- The account email and phone number, matched to the cardholder's details where you have them
Send counts and timestamps, never message content or other members' information. Pasting a member's private conversations into a dispute file creates a privacy problem far bigger than one lost subscription payment, and it exposes people who never disputed anything. Check your privacy policy and any state privacy law that applies before deciding what goes into a dispute package, and confirm that decision with counsel.
Open the file with a short summary: the renewal date, the claimed cancellation date if there is one, and a table of activity between them. Attach the raw logs behind it. A reviewer follows a clear timeline faster than an export of every log line.
Proving Renewal Notice and Cancellation Access
For "I cancelled" and "I didn't know" claims, you need to show what the member saw and what they could do about it.
Keep a dated archive of your checkout pages, because a dispute months after signup needs the screen as it looked that day. The archive should show the price, the billing interval, the fact that the plan renews automatically, and the renewal price if it differs from an intro rate. Store the consent record (the checkbox or button press with its timestamp and IP address), the receipt email, and every renewal reminder with its delivery log.
Then document the exit. Screenshot the cancellation path on web and in the app, and log every cancellation request with a timestamp. If the member did cancel and your system billed them anyway, refund immediately. That's a merchant error, and fighting it turns a billing bug into a ratio problem.
Intro pricing raises the stakes. A discounted first month that renews at full price is a common source of "I didn't know" disputes, and card network rules add disclosure and notice steps for trials and promotional offers; our guide to card network rules for dating site free trials covers them. Many states also have automatic renewal laws, and federal consumer-protection law reaches deceptive recurring billing. Requirements differ by state and change over time, so treat this as general information and confirm your setup with a qualified attorney.
Mobile billing adds a wrinkle. If a member subscribed through Apple's or Google's in-app purchases, the app store billed them, and refunds generally run through that platform rather than your merchant account. Members who signed up on your website sometimes check their phone's subscription settings, don't see the plan, and assume it's cancelled. State on every receipt which channel billed them and where to cancel.
When Refunding Beats Fighting a Dating Subscription Dispute
Here is the decision with illustrative numbers. Assume a $34.99 monthly renewal and a processor dispute fee of $25 charged whether you win or lose. Your processor's fee and policy may differ.
| Your choice | What it costs you | Counts toward monitoring? |
|---|---|---|
| Refund when the member contacts you | $34.99, no dispute fee | No, because no dispute is filed |
| Fight and win | $25 fee plus staff time; you keep the $34.99 | Yes (see below) |
| Fight and lose | $34.99 plus $25, or $59.99 | Yes |
| Ignore the dispute | Same as losing: $59.99 | Yes |
Fighting saves money only when the fee is smaller than the charge amount multiplied by your chance of winning. For this plan, $25 ÷ $34.99 means you'd need to win about 71% of the time to break even. A $179.99 annual renewal under the same fee needs about a 14% win rate, though as the CE 3.0 example shows, annual members rarely have the history to fight a fraud claim.
The rule most merchants get wrong: winning doesn't erase the dispute from your ratio. Under Mastercard's Excessive Chargeback program, represented chargebacks are not used to recalculate thresholds, so a won case still counts. Only prevention keeps a dispute off the books.
In practice, refund when the member reaches you before filing, when your logs show a cancellation attempt, or when there's been no activity since the renewal. Fight when the account was used after the renewal and your disclosures hold up. Never refund a transaction that has already been charged back, because you can end up paying twice.
Keeping Dating Site Chargebacks Below Visa and Mastercard Thresholds
Visa's Acquirer Monitoring Program (VAMP) folds fraud and disputes into one number: TC40 fraud reports plus non-fraud disputes, divided by settled transactions, measured per descriptor. Fraud reports count even when the issuer never files a chargeback. For U.S. merchants, the "Excessive" level was set at 2.2%, scheduled to drop to 1.5% on April 1, 2026. Mastercard's Excessive Chargeback Merchant program starts at 100 chargebacks in a month and a 1.5% ratio, with a high tier at 300 chargebacks and 3%. It divides this month's chargebacks by last month's transactions, and Mastercard runs a separate Excessive Fraud Merchant program for fraud alone.
Those are network rules. Your processing agreement may set a lower internal limit, and that limit is what triggers rolling reserves on dating sites long before any network fine. Get your processor's current figures in writing.
Timing makes this harder. Disputes arrive weeks after the renewal that caused them, so a seasonal signup spike shows up as disputes when that cohort first renews. Track disputes weekly by plan type and acquisition source. One affiliate sending low-intent traffic can drive an outsized share of fraud claims, which overlaps with romance scammers using stolen cards.
Prevention does more for the ratio than any win. Send a reminder before longer-plan renewals with a one-click cancel link, make cancellation as easy as signup, auto-refund a first renewal on an account with zero activity, and put a support URL or phone number in your descriptor. Ask your processor which network dispute alert services it supports and what each alert costs next to your dispute fee. On fraud claims, 3-D Secure authentication at signup can shift fraud liability for that first transaction to the issuer; how that carries to later renewals depends on network rules and your setup.
Start this week by pulling last quarter's disputes and sorting them by reason code. For each one, check whether you had what that code requires: a clean cancellation log for 13.2, or two qualifying prior charges with a matching IP or device for a fraud claim. The gaps tell you what to start logging. If your current processor treats every dispute as a reason to tighten terms, MannyPay offers high-risk merchant accounts, and you can request a free processing quote and hear back from a MannyPay specialist within one business day.
Sources
- Compelling Evidence 3.0 Requirements: What Visa Mandates and What Actually Wins the Case (cside)
- Visa Compelling Evidence 3.0: New Dispute Rules for 2026 (Chargebacks911)
- Visa Compelling Evidence 3.0 (CE3.0): Rules and 2026 Changes (Chargeflow)
- Visa 13.2: Cancelled Recurring (Chargeback.io)
- Visa Chargeback Reason Code: 13.2 Cancelled Recurring (ChargebackStop)
- Visa Chargeback Reason Codes & Rules: 2026 Merchant List (Chargeflow)
- Visa's Updated VAMP Program: What Merchants Need to Know (Forter)
- Visa Acquirer Monitoring Program (VAMP) (Chargeback Gurus)
- VAMP Merchant Guidance (Trust Payments)
- Solidgate Visa Monitoring Programs Documentation
- Mastercard Chargeback Guide: Time Limits and Thresholds (Chargeback.io)
- The Mastercard Chargeback Threshold: Explained (Chargebacks911)
- Mastercard Excessive Chargeback Program (ECP) Guide 2026 (Chargeflow)
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


