Matchmaking Service Chargebacks: Winning 'No Good Matches' Disputes
A matchmaking service chargeback over 'no good matches' is winnable. See the reason codes, contract terms and records issuers actually weigh.

Photo: Pixabay
On this page 6 sections
- Why Two Disputes Hurt a Matchmaker More Than a Retailer
- Reason Codes Behind a Matchmaking Service Chargeback
- Define a Match in Writing, Then Check It Against State Law
- Log Every Introduction and the Client's Reaction to It
- Build the Evidence Packet Before Your Processor's Deadline
- Settle the Refund Before It Becomes a Chargeback
Key takeaways
- A "no refunds" clause won't stop a not-as-described dispute. A written definition of a match, signed by the client, gives you a real defense.
- At 30 sales a month, you can't reach the counts that trigger Visa's or Mastercard's merchant-level programs. Your processor's risk team is where the danger is.
- Refunding the undelivered part of a package when the client first complains often costs much less than losing the full sale in a chargeback.
A matchmaking service chargeback over "no good matches" is winnable when your file proves two things: what you promised the client and what you delivered, with the client's own reactions recorded along the way. Issuers don't judge chemistry. They compare the cardholder's complaint with your written terms and your records. A contract that defines a match in measurable terms, plus a log of each introduction and the client's response, turns a subjective complaint into a factual question you can answer.
Matchmakers usually lose these disputes because the evidence never existed. Nearly all of it is built before the sale and during the engagement, not after the notice arrives.
Why Two Disputes Hurt a Matchmaker More Than a Retailer
A client who buys a year of introductions is buying hope. If month seven arrives without a relationship, disappointment can turn into "I didn't get what I paid for," even when every promised introduction happened. Payment timing widens the gap. Packages are often paid in full at signing, sometimes keyed over the phone, while the value arrives over months.
Then there's the math. Visa's Acquirer Monitoring Program (VAMP), which took effect June 1, 2025, divides fraud reports plus disputes by settled transactions, according to Visa's VAMP fact sheet. A boutique firm has few sales to divide by. In an illustrative month with 30 card sales and two disputes, the ratio is 2 ÷ 30, or about 6.7%.
Many owners misread the rule at this point. That 6.7% won't put you in a Visa or Mastercard merchant program on its own, because both programs also require a minimum number of disputes. Since April 1, 2026, Visa has flagged a U.S. merchant as Excessive when its VAMP ratio reaches 1.5% and it has at least 1,500 fraud reports and disputes in the month, according to Dodo Payments' VAMP explainer. Both conditions have to be met. Mastercard's Excessive Chargeback Merchant tier starts at 100 chargebacks and a 1.5% ratio in a month, per Chargeflow's guide to the Mastercard program. A firm with 30 sales a month can't come close to either count.
Your real exposure is with your processor. Visa's fact sheet measures each acquirer's whole portfolio against much lower lines: 0.5% for Above Standard and 0.7% for Excessive. NMI's VAMP summary notes that an acquirer in the Above Standard tier pays $4 for each fraud and dispute transaction from any merchant at or above 0.5%, and $8 in the Excessive tier. So a small merchant running several percent gets noticed by the acquirer's risk team, and the usual responses are reserves, holds or a closed account. That exposure is why many processors treat matchmaking as high risk and put it on high-risk merchant accounts.
Reason Codes Behind a Matchmaking Service Chargeback
Every dispute arrives with a reason code, and the code tells you what to prove. A "no good matches" complaint usually comes in as Visa reason code 13.3, Not as Described or Defective Merchandise/Services. chargeback.io's explainer places it in Visa's Consumer Disputes group. On Mastercard the same complaint comes in as 4853, Cardholder Dispute. Chargebacks911's breakdown of 4853 describes it as service that differs from the "written or verbal description provided at the time of purchase." Note the word "verbal." What your salesperson promised on the consultation call is part of the record.
For matchmakers, disputes tend to fall into four groups. Read the exact code on your notice, since each network defines its own categories.
| Dispute category | What the client claims | What you have to show |
|---|---|---|
| Not as described | The service differed from what was promised | The written promise, and proof the service matched it |
| Not provided | The client never received the service | Dated proof of each introduction delivered |
| Cancelled | The client cancelled and wasn't refunded as agreed | The cancellation policy the client accepted, and that you followed it |
| Fraud | The cardholder says they never made the purchase | Proof the cardholder authorized the charge |
One misunderstanding costs matchmakers more than any other: a "no refunds" clause does not block a not-as-described dispute. According to chargeback.io, Visa has made clear that a merchant's refund or "all sales final" policy doesn't override the cardholder's right to dispute under 13.3. Your contract wins disputes by defining the service precisely. Forbidding refunds won't do that.
Fraud claims need different tools. 3D Secure authentication helps against stolen cards used online, and our guide to 3D Secure liability shift for online sales explains how it works. It does nothing when your real client disputes the charge as a service problem.
Define a Match in Writing, Then Check It Against State Law
The most useful sentence in your contract defines "introduction" or "match." Without it, the cardholder's view wins by default. With it, the issuer has a standard to measure your records against. A strong definition ties each match to criteria the client set and signed:
- Requirements from a signed intake form, such as age range, location, faith and whether they want children
- Mutual consent, meaning both people reviewed a profile and agreed to meet
- A defined delivery event, such as exchanged contact details or a scheduled first date
- A rule that any change to the criteria is made in writing and dated
State plainly that you don't guarantee a relationship or marriage, then check your website, ads and sales scripts against the contract. A landing page promising "your soulmate" can undercut a careful agreement. Write the refund terms in dollars: how much of the fee is earned at onboarding, how much is tied to introductions, and the refund formula if the client cancels midway.
State law can override all of it. California's Dating Service Contracts chapter (Civil Code §§ 1694–1694.4) gives buyers the right to cancel until midnight of the third business day after signing. It also requires a written contract with a copy to the buyer, and it bars requiring payments or financing over more than two years. If the contract doesn't comply, the buyer can cancel at any time.
New York's social referral service law (General Business Law § 394-c) is stricter. Its consumer rights text says a contract can't require the purchaser to pay more than $1,000. A contract costing more than $25 must furnish a minimum number of referrals per month unless the service offers search functionality or presents possible matches. Every contract must also state how far the buyer will travel to meet a referral.
A contract that conflicts with your state's statute hands the cardholder a strong argument and can expose you to more than a lost dispute. Have an attorney review it against the law where you and your clients are located. This is general information, not legal advice. If you also run an online dating platform, see our guide to internet dating safety laws and the disclosures processors look for.
Log Every Introduction and the Client's Reaction to It
If the contract is your promise, the log is your proof of delivery. Keep one timestamped record per client, ideally in a CRM:
- Intake. The signed criteria form, plus any changes the client later requested in writing.
- Each introduction. Its date and a note on how the match fit the client's criteria, with a copy of the profile you shared and the match's private details redacted.
- Client consent. The message where the client agreed to meet this person.
- The date itself. Confirmation it happened, such as a calendar invite or a follow-up text.
- Client feedback. The client's written reaction after each date.
Firms skip item five more than any other, yet it is often the strongest, because a short post-date form turns impressions into a dated record in the client's own words. "Nice, smart, no spark" doesn't hurt you. It shows the client went on an introduction that met their criteria and that the missing piece was chemistry, which you never promised. If you record consultation or coaching calls, check consent rules first, because some states require every party's agreement to a recording.
Worked Example: A Month-Five Dispute Over an $18,000 Package
Every figure here is illustrative, not industry data. Assume the firm operates in a state whose law permits this structure. Read on its face, New York's $1,000 limit would not allow this package.
- Package: $18,000, paid in full by card at signing for a one-year term
- Contract terms: $4,500 earned at onboarding, with the remaining $13,500 split evenly across six introductions at $2,250 each
- Delivery so far: onboarding complete and four introductions made, each approved in writing and followed by a feedback form
In month five the client files a not-as-described dispute: "None of the matches were right for me." The packet answers point by point. The signed intake form names an age range, a maximum distance and a wish for children, and the log shows all four matches fit. Each approval is in writing. Four feedback forms describe pleasant dates without chemistry, and one reads, "Good fit on paper, keep going." The contract's no-guarantee clause excludes any promise of a relationship.
Now look at the decision a month earlier, when the client first complained. By the contract's own schedule, the firm had earned $4,500 + (4 × $2,250) = $13,500, and two introductions worth 2 × $2,250 = $4,500 were undelivered. Offering $4,500 on cancellation would have closed the file at a known cost. Losing the dispute would reverse the full $18,000, add a dispute to the firm's ratio and possibly bring a per-chargeback fee from the processor. Even a won dispute ties up the money while the case runs.
Build the Evidence Packet Before Your Processor's Deadline
Check your processor's response deadline first. It is usually shorter than the network's window, and if you miss it you lose the case. Then assemble the packet in this order:
- Rebuttal letter. One page that names the reason code and answers the claim in a few direct sentences, each pointing to an exhibit.
- Signed contract, with the match definition and the no-guarantee clause highlighted.
- Proof of acceptance: the e-signature audit trail for the contract and intake form, and the invoice or checkout page showing the refund terms.
- Introduction log, trimmed to the entries that address the dispute.
- Client feedback and messages, especially anything showing the client wanted to continue.
- Credit already issued, if you gave a partial refund, so the issuer doesn't award it twice.
Label each exhibit, highlight the lines that matter and cut anything unrelated to the reason code. Never alter or backdate records. If you lose and the first response left out strong evidence, ask your processor whether a pre-arbitration response makes sense and what it costs.
How you take payment shapes the record too. A card tapped at an in-office signing is better proof the client was there than a number read over the phone. For remote sales, a virtual terminal for keyed payments paired with an e-signed contract and an emailed receipt leaves a cleaner trail than a keyed number alone.
Some matchmakers bill in stages tied to real, separately priced phases, such as onboarding first and the active search later. That limits how much any single dispute can reverse. The trade-offs resemble those in our comparison of annual vs. monthly billing for fees, risk and cash flow. Each charge must reflect a distinct, disclosed phase of service. Splitting one sale into pieces to dodge authorization limits or underwriting review breaks card network rules.
Settle the Refund Before It Becomes a Chargeback
A refund dispute you resolve directly never reaches your ratio. The warning signs show up early: skipped feedback forms, a client who starts declining introductions, an email asking what they're paying for. When that email arrives, act. Call the client, review their criteria together and document the conversation. If they want out, apply the contract's refund schedule promptly and get the agreement in writing.
Ask your processor about pre-dispute alert tools as well. According to chargeback.io's VAMP guide, disputes resolved through a pre-dispute alert don't count toward the VAMP ratio. That gives you one more chance to refund on your terms before a formal chargeback lands.
Before your next sale, pull three completed client files and try to build a dispute packet from each one. Fix whatever is missing first, whether that's an unsigned intake form or a refund formula that lives only in your head. If you want a processor that works with high-ticket, high-risk service businesses, request a free quote from MannyPay and a MannyPay specialist will respond within one business day.
Sources
- Visa Acquirer Monitoring Program Fact Sheet (2025)
- Dodo Payments: Visa VAMP Explained: Thresholds, Ratio, and Fees for Merchants
- NMI: VAMP: What You Need to Know About Visa's Acquirer Monitoring Program
- chargeback.io: Visa Acquirer Monitoring Program (VAMP): Full Guide
- Chargeflow: Mastercard Excessive Chargeback Program (ECP) Guide
- chargeback.io: Visa 13.3: Not as Described or Defective Merchandise/Services
- Chargebacks911: Mastercard Reason Code 4853 Defective/Not as Described
- Justia: California Civil Code § 1694.2 (Dating Service Contracts)
- FindLaw: California Civil Code § 1694.1
- FindLaw: New York General Business Law § 394-c
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.


