email59

Billing

The customer disputed the charge: the email to send, and the evidence the bank actually reads

A chargeback is not a polite refund request. The moment a customer contacts their card-issuing bank to challenge a payment, the card network forcibly debits the full transaction amount from your merchant balance alongside an immediate, non-refundable dispute fee. You are left with a ticking countdown clock and a bank reviewer who will spend less than ninety seconds looking at your files.

For small independent shops and software apps, chargebacks feel personal and confusing. But in practice, between 60% and 70% of disputed charges on small businesses are what the payment industry calls friendly fraud: accidental disputes where the buyer genuinely did not recognize the transaction on their online bank statement. Handling a dispute cleanly comes down to three steps: knowing your processor's rules and deadlines, sending a clear clarification email to the customer before the clock runs out, and knowing the exact proof the cardholder's bank requires if you decide to contest.

Dispute fees and response windows by platform

When a cardholder files a dispute with their bank, your payment gateway passes through network fees and enforces strict evidence submission deadlines. Missing a deadline by a single minute results in an automatic forfeiture of the dispute with zero right to appeal.

Payment GatewayDispute Fee (US)Response WindowIs Fee Refunded if You Win?Resolution Time
Stripe$15.007 to 21 days (set by card network)No (standard $15 fee is retained)60 to 90 days
Square$0.007 calendar days strictNo fee charged; held funds returnedUp to 90 days
PayPal$8.00โ€“$16.00 (dispute) / $20.00 (chargeback)10 days (claim) / 20โ€“45 days (card)Only if Seller Protection applies30 to 75 days
Shopify Payments$15.007 to 21 days (network-driven)No60 to 90 days

Notice that on Stripe and Shopify Payments, the $15 dispute fee is lost regardless of the outcome. Even if you submit rock-solid evidence and the bank rules in your favor, the $15 processing fee is non-refundable because the card networks (Visa and Mastercard) assess administrative charges to process representment. Square is the lone major processor that charges no dispute fee to the seller.

Step 1: The email to send the customer (often it is a simple mistake)

Before preparing dozens of pages of evidence for a bank clerk, your first move should always be reaching out to the customer. In the majority of cases involving small apps or online shops, the customer did not maliciously file fraud. Most accidental chargebacks occur because:

  • Unrecognized statement descriptor: Your business legal entity is registered as Acme Ventures LLC, but the customer bought from CozyKnit Supplies. When reviewing their banking app, they see an unfamiliar corporate name and press 'Report Fraud'.
  • Family member purchase: A partner, child, or coworker used the card on a shared computer or tablet without mentioning it.
  • Forgotten recurring renewal: An annual renewal charged, and the customer reacted to the alert before checking their email receipts.

If you write to the customer with hostility or accuse them of stealing, they will get defensive and refuse to help. Instead, send a calm, factual note giving them the exact purchase details, what statement descriptor appeared on their card, and clear instructions on how they can cancel the dispute with their bank.

Subject: Quick question regarding your [Product / Store Name] order #[Order Number]

Hi [Customer Name],

We received an automated notification from our payment processor that a dispute was recently filed for a charge of $[Amount] made on [Date].

Because credit card statements sometimes display unfamiliar corporate names, we wanted to reach out directly with the transaction details in case this was a simple mix-up:

  • Item / Service: [Product Name or Subscription Plan]
  • Date of Charge: [Date, Time, Time Zone]
  • Amount: $[Amount]
  • Card Billed: [Card Brand] ending in [Last 4 Digits]
  • Statement Descriptor: On your statement, this appears as [Exact Descriptor, e.g., BIZ59*EMAIL59 NY]
  • Associated Account / Delivery: [Customer Email, User ID, or Tracking Number]

If you or someone in your household made this purchase, you can resolve this easily by contacting your bank's card services department (or checking your mobile banking app) and asking them to withdraw the dispute.

If you did not authorize this charge or believe your card was compromised, please let us know right away so we can secure your account on our end.

Thank you,
[Your Name / Support Team]
[Your Company Name]

The golden rule: never click 'Refund' during an active dispute

When a customer replies saying, 'Oh, I'm sorry! Can you just refund it on your end?', your immediate instinct might be to open Stripe or Square and hit Refund. Never do this.

When a dispute is opened, the bank has already debited the money from your account. If you click Refund in your dashboard while the dispute status is active, you issue a separate credit back to the customer's card. If the customer does not formally cancel the dispute with their bank, the bank's chargeback process will also finalize, debiting you a second time. You lose the sale amount twice, plus the non-refundable dispute fee.

Instead, explain to the customer that their bank holds the money in escrow. Once they call their bank to drop the dispute, ask them to reply with a screenshot or PDF of the bank's withdrawal confirmation letter. You can then submit that withdrawal letter as your primary evidence, which guarantees an immediate win.

The evidence the bank actually reads (and what they ignore)

If the customer does not respond or the dispute was filed with fraudulent intent, you have to contest it through representment. When submitting evidence to Stripe, Square, or PayPal, understand how the evaluation works: an entry-level bank claims officer reviews dozens of disputes an hour. They spend between 60 and 90 seconds scanning your uploaded PDF.

They will not read emotional paragraphs about how hard you work as a small business. They will not scroll through 40 pages of unformatted database dumps. They look for specific, objective anchors that prove authorization, receipt, or fulfillment.

1. Physical Goods & Online Stores

  • Carrier tracking showing delivery: The single most critical piece of evidence. A tracking number alone is not enough; the tracking screenshot or export must show the status 'Delivered', the delivery date, and the destination city/state/ZIP matching the customer's checkout shipping address. (See our guide on shipping emails and tracking links).
  • Itemized receipt: A clean copy of the original order receipt showing unit prices, quantities, taxes, and shipping fees. (See our guide on receipt emails and required billing data).
  • Signature confirmation: For high-ticket items (mandatory under PayPal Seller Protection for orders of $750 or more), include the carrier signature record.

2. Digital Goods, SaaS & Apps

  • Sign-in & activity audit logs: Server logs showing the customer logged in from an IP address geographically consistent with their billing details, along with timestamps of usage before and after the charge.
  • Usage proof: Concrete proof of value delivered: files exported, API calls completed, projects created, or emails delivered.
  • Policy clickwrap consent: A screenshot of your checkout page showing the checkbox or explicit notice where the customer accepted your Terms of Service and Cancellation Policy prior to payment. (See our guide on refund policies and card return timelines).
  • Communication history: Customer support tickets or live chat logs showing the customer asking questions about the product using the same registered email address.

Visa Compelling Evidence 3.0: Winning 'Fraud' disputes with past records

The most common dispute reason code across all card networks is Visa Reason Code 10.4: Fraud in a Card-Absent Environment. Customers use this code when claiming, 'I never bought this; someone stole my card.' Historically, merchants almost always lost 10.4 disputes because proving who was sitting behind a screen was nearly impossible.

To stop abusive chargebacks on repeat buyers and subscription services, Visa enacted Compelling Evidence 3.0 (CE 3.0). Under CE 3.0, if you can prove the cardholder had established an undisputed payment history with you prior to the disputed transaction, the issuing bank is legally required by Visa to reverse the dispute and return your money.

Visa CE 3.0 RequirementSpecific RuleExample Proof
Prior Undisputed PurchasesAt least 2 prior settled transactions on the exact same card credentialPrevious subscription renewals or order invoices from 5 and 9 months ago
Transaction Time WindowPrior transactions must have occurred between 120 and 365 days prior to the disputeOrders older than 4 months, but under 1 year old
Core Digital Footprint (Required)At least 1 core identifier must match across all 3 transactionsMatching Customer IP Address OR Device Fingerprint / ID
Secondary Matching ElementAt least 1 secondary identifier must also match across all 3 transactionsCustomer Account ID, verified login email, or physical shipping address

If you operate a subscription service or a store with recurring customers, store customer checkout IP addresses and persistent user account IDs in your database. When a Visa 10.4 dispute arrives, presenting a table linking the disputed charge to two prior undisputed charges meeting the 120โ€“365 day window shifts liability back to the cardholder's bank automatically.

The refund-or-fight decision: a worked cost calculation

Every dispute carries hidden friction: preparing documentation takes 30 to 60 minutes of administrative work, and losing a contested dispute often comes with added processing penalties. Deciding whether to fight or accept the loss requires calculating the expected financial return.

Scenario A: $35 Physical Item (No Tracking Scan)

  • Disputed Amount: $35.00
  • Dispute Fee: $15.00 (lost immediately)
  • Evidence on hand: Standard postal stamp without tracking scan.
  • Estimated Win Probability: <5% (banks strictly require carrier delivery proof).
  • Cost of Labor: 30 minutes to assemble receipts ($15 value).
  • Financial Outcome: Fighting guarantees a total loss of $35 (item) + $15 (fee) + $15 (labor) = -$65 net loss.
  • Decision: Accept the dispute immediately. Do not waste time contesting without carrier delivery scans.

Scenario B: $120 Annual SaaS Subscription

  • Disputed Amount: $120.00
  • Dispute Fee: $15.00
  • Evidence on hand: 2 prior annual renewals from same IP (Visa CE 3.0 eligible), 45 login events in last 60 days, accepted terms checkbox.
  • Estimated Win Probability: >85%.
  • Cost of Labor: 15 minutes to export logs ($7.50 value).
  • Financial Outcome if Won: Recover $120.00 charge minus $15 dispute fee = +$105.00 net recovery.
  • Decision: Contest the dispute. High probability of reversal makes representment clearly profitable.

Beyond individual order dollars, small businesses must protect their merchant dispute activity ratio. Visa and Mastercard calculate your dispute ratio monthly (total disputes divided by total successful transactions):

  • Visa Dispute Monitoring Program (VDMP): The standard threshold is 0.9% (or 100 disputes per month). Exceeding 0.9% puts your merchant account into monitoring status, where Visa assesses fines of $50 per dispute. Crossing 1.5% incurs fines of up to $150 per dispute and risks payment processing termination.
  • Mastercard Excessive Chargeback Program (ECP): The threshold is 1.0%. Breaching 1.0% triggers Tier 1 fines of $1,000 to $5,000 against your payment provider, which gets billed directly back to your account.

Notice an important technical detail: even if you contest a dispute and win, the dispute still counts against your card network ratio. Card brands track the dispute initiation, not the final representment verdict. The only way to prevent a dispute from hitting your ratio is to resolve customer complaints before they escalate to the bank, or have the customer withdraw the dispute directly.

Automating dispute alerts: catch the deadline on day one

Because dispute response deadlines are non-negotiable, relying on someone checking the Stripe or PayPal dashboard once a week is a recipe for forfeited cases. When a dispute is created, your backend should catch the webhook immediately and queue the clarification email.

import os
import requests
from fastapi import FastAPI, Request

app = FastAPI()

@app.post("/webhooks/stripe")
async def stripe_dispute_webhook(request: Request):
    payload = await request.json()
    event_type = payload.get("type")

    # Catch new chargeback dispute filings immediately
    if event_type == "charge.dispute.created":
        dispute = payload["data"]["object"]
        amount = dispute.get("amount", 0) / 100.0
        reason = dispute.get("reason")  # e.g., unrecognized, fraudulent
        due_by = dispute.get("evidence_details", {}).get("due_by")
        customer_email = dispute.get("charge_details", {}).get("billing_details", {}).get("email")
        statement_descriptor = os.getenv("BILLING_DESCRIPTOR", "BIZ59*STORE NY")

        # Send friendly clarification email via email59
        requests.post(
            "https://email59.com/v1/send",
            headers={"Authorization": f"Bearer {os.getenv('EMAIL59_KEY')}"},
            json={
                "from": "billing",
                "to": customer_email,
                "subject": f"Quick question regarding your charge of ${amount:.2f}",
                "text": (
                    f"Hi there,\n\n"
                    f"Our payment system noted that a dispute was filed for ${amount:.2f} (reason: {reason}).\n"
                    f"On your statement, this appears as: {statement_descriptor}.\n\n"
                    f"If this was an unfamiliar descriptor or accidental report, you can easily "
                    f"withdraw the dispute through your online banking app before {due_by}.\n\n"
                    f"If you need any help or didn't authorize this, just reply directly to this email.\n"
                )
            },
            timeout=10
        )

    return {"status": "received"}

Summary: the 4-step dispute playbook

When a dispute notification lands in your inbox, follow this straightforward checklist:

  1. Check the calendar countdown: Open your processor dashboard and note the exact deadline (7 to 21 days). Add a calendar reminder 48 hours before that date.
  2. Send the customer clarification email within 24 hours: Provide the exact statement descriptor, item description, and purchase timestamp. Most disputes vanish when customers realize what the charge was.
  3. Do not issue a manual dashboard refund: Wait for the customer to formally withdraw the dispute with their bank, and attach their confirmation letter to your response.
  4. Submit clean, objective proof: If you must contest, compile carrier delivery scans with matching ZIP codes for physical goods, or IP sign-in logs and terms acceptance timestamps for software apps. Leave out emotional arguments.
Send your first email More articles