Here's how the contest works, and where your contract becomes the deciding document.
First, know the clock — it's longer than you think
Two clocks run in every dispute, and vendors mix them up constantly:
- Your window to respond: typically 5 to 21 days from when the dispute lands (Stripe's guide). Miss it and the cardholder wins by default: no evidence considered, nothing appealed. Put a calendar rule in your business today: dispute email = same-day acknowledgment, evidence assembled within the week.
- The couple's window to dispute: this is the sleeper. Per Pixally's summary of Visa's dispute conditions (13.1 "merchandise/services not received" and 13.7 "cancelled merchandise or services"), a dispute can be processed within 120 days of the transaction — or 120 days from the date the cardholder expected the services. For a retainer paid January 10 for a September wedding, the window can run to January of the following year. For weddings booked more than 540 days out, the cap applies at 540 days. These numbers come from a third-party reading of the network rules — exact windows vary by card network and reason code, so treat them as the shape of the rule, not a quote from Visa itself.
That second clock is why chargebacks feel like they come from nowhere. The wedding is long over; the paperwork window is not.
What actually decides it: the evidence hierarchy
Stripe's dispute documentation is unusually specific about what wins, and every point maps to something a wedding contract carries:
1. Proof the cardholder authorized the transaction. Fraudulent disputes account for over half of all disputes (Stripe's best-practices doc). The evidence that matters: signed receipts or contracts, AVS/CVC match results, IP matching the cardholder's billing address. Stripe attaches AVS/CVC and IP automatically — but a signed contract naming the package, the price, and the payment plan is the human-readable authorization a bank reviewer can absorb in seconds.
2. Proof of the terms the customer agreed to. For "cancelled service" disputes — the most common wedding flavor — the reviewer needs the refund and cancellation policy the customer agreed to at purchase. Stripe's guidance is to show the policy as presented, with the relevant part emphasized: a clean screenshot or excerpt of the signed contract's cancellation clause, not the entire document. (Their explicit don't: uploading your whole terms of service. Relevant excerpts only.)
3. Proof of service or delivery. For photography: gallery delivery logs, download records, email with the delivery link, correspondence where the couple confirms receipt and likes. For digital goods Stripe names system logs proving the customer downloaded content — an online gallery's download history is exactly that.
4. Chronology and organization. The same doc, twice: evidence presented chronologically, grouped by type, with an executive summary tying your story to the specific reason code. The reviewer is working through a queue; the packet that reads itself wins.
The wedding-specific traps
The cancellation dispute. Couple cancels, asks for money back, bank sides with them by default unless you show the agreed terms. This is where the cancellation ladder pays for itself: your signed contract shows the scale, the date of cancellation, the rung it landed on. Without it, "the vendor kept my money" is the entire opposing story — and it's a good story.
The "services not received" dispute on a retainer. The couple's logic: we paid, the wedding got cancelled (or we cancelled), we received nothing, refund. Your counter isn't rhetoric; it's the retainer clause: the retainer paid for reserving the date, a service completed at signing, and you declined other bookings for that date. Courts understand this argument (the case law is unpacked in the retainer article); bank reviewers understand it too, but only when the contract states it in those words. "Non-refundable deposit" alone doesn't teach them anything.
The partial-refund trap. Stripe's merchant dispute guidance and its Issuing-side docs both flag the pattern (the Issuing docs cover the issuer side — the logic carries over to how you respond as a merchant): disputing the full amount when a partial refund was already issued, or ignoring a partial refund in your evidence, reads as bad faith. If you refunded anything, lead with it — it's evidence you act in good faith, and it shrinks the contested amount.
The tone trap. Stripe's reviewers' guidance is blunt: neutral tone, relevant facts, no long explanations. A dispute packet that reads as an essay about how hurt you are loses to a packet that reads as a filing cabinet. You are not writing to the couple. You are writing to a reviewer working through a queue.
Build the evidence habit before you need it
The vendors who win disputes didn't get lucky — their records were dispute-shaped from the day of booking:
- Signed contract, stored where you can find it in 30 seconds — with the retainer, cancellation, and delivery terms visible
- Payment records tied to the contract (Stripe handles this side; your job is linking payment to the signed agreement)
- Delivery proof: gallery delivery email + download log + the couple's happy reply. Screenshot the happy one. It ages well.
- Correspondence file per wedding, with the irrelevant parts redacted (Stripe's advice for long email chains)
VowSign keeps the signed contract and the invoice together in one client record — the signed PDF downloads from there, and you assemble the rest of the packet from your delivery and correspondence files. The photography contract template carries the clause language that gives that file its teeth; the payment schedules article shows the retainer and balance lines that keep the story consistent.
The honest summary
You win a chargeback by having agreed, in writing, to exactly the terms in dispute — and by proving the parts you performed. Everything else is packaging. The expected-service window means the threat stays alive for roughly four months after the wedding; the 5–21 day response window means the loss happens by silence, not by argument. Build the file as you book, and the dispute becomes paperwork instead of panic.