A customer called on a Tuesday afternoon. She was warm and a little rushed. She read her card number aloud while a dog barked behind her, you typed it in, she said "perfect, thank you so much," and you both hung up feeling good about the day.
Six weeks later the dispute arrives. Reason: fraudulent. She says she never authorized it.
You remember the call vividly. That's the trouble. The memory is yours alone, and a card network has no way to read it.
Why the phone sale is the loneliest kind of sale
A phone order is a card-not-present transaction. Nobody inserted a chip or entered a PIN, and there's no checkout page with a timestamped checkbox. Stripe supports keying in cards for phone orders through the Dashboard or virtual terminal, where available on your account. Those payments typically carry none of the signals online checkouts leave behind: no device fingerprint, no session, no 3D Secure authentication.
That last point matters. 3D Secure can shift fraud liability toward the issuer when the cardholder authenticates. A card keyed in by hand rarely has that protection. If the cardholder says "that wasn't me," the question of who authorized the charge falls on you to answer.
So with a phone order, the sale itself leaves almost nothing behind. What's left are the pieces around the call. The work is collecting those pieces and arranging them so a reviewer who has never heard of you can see a real person agreeing to a real purchase.
What a reviewer is actually asking
In a fraud dispute, the reviewer is not asking whether you delivered. They're asking whether the cardholder, or someone with the cardholder's permission, made this purchase. Delivery helps, but it's secondary to identity and intent.
For a phone order, three questions carry most of the weight:
- Did the person on the call have the card's details? Matching data suggests they did.
- Did that person want what was sold? A specific description, agreed price and stated delivery details show intent.
- Is the person connected to the cardholder? Same name, same address, same contact point, or a prior purchase history.
Every piece of evidence you submit should answer one of those three questions. If a document doesn't, leave it out. (More is not better; a cluttered file buries the strong parts.)
The evidence that survives a call
The verification results
When you keyed in the card, Stripe likely ran address and security code checks if you entered those fields. The results of AVS (address verification) and CVC checks sit on the charge record. A full match on both is one of the cleanest signals available for a phone order, because someone had to know the billing address and the three-digit code, which are things a person holding a stolen card number alone often lacks. Screenshot the payment details showing those results. If you skipped entering the CVC, you can't retroactively create it, which is worth remembering for later.
The recording, if you have one
If you record calls, a clip where the customer states their name, confirms the product and price, and agrees to the charge is powerful. But handle this carefully.
Recording consent rules differ by place. Some jurisdictions need only one party's consent; others require everyone on the call to agree. If your calls weren't recorded with proper notice, don't submit a recording you may not have had the right to make, and don't assume it's fine. Check the rules where you and the customer are located, or ask a lawyer. If a recording is lawful and clear, trim it to the relevant minute or two and note the exact timestamps in your written response. A reviewer will not listen to forty minutes.
The written trail around the call
This is where most phone sales are won, because most of them have no recording. Look for:
- A confirmation email or text you sent after the call, with the item, price, and a receipt. Even better if the customer replied to it.
- Your call log showing the incoming number, the time and the duration. Make sure the number matches what's on the customer's file.
- Notes you took during the call, if they were written at the time rather than reconstructed later. Timestamped CRM entries count for more than a memory typed up this week.
- Later contact from the customer: a question about delivery, a request to change something, a thank-you. Any of these shows engagement with the order after it was placed.
The delivery or fulfillment proof
Tracking that shows delivery to the cardholder's billing address is strong. If you shipped somewhere different, explain why, and show where that address came from. A customer who said "send it to my sister's" on a call is plausible, but only if something in writing connects the instruction to the order.
The mistake that sinks phone-order disputes
The typical losing response is a story. "The customer called, I took the order, she was friendly, it's definitely her." It might be completely true. But a narrative with no attachments looks the same as a merchant making it up.
The winning version turns every sentence of that story into something a stranger can verify. Instead of "she was friendly," attach the thank-you text. Instead of "I took the order," attach the CRM note with its timestamp. Instead of "it's her," show the AVS match and the shipping address that matches her billing address.
The rule is simple: if you couldn't point to it, you can't claim it.
Build the habit before the next call
You can't improve the evidence from a call that already happened. You can improve the next hundred. Phone sales are a small enough channel that a few habits go a long way:
- Read the order back aloud and have the customer say yes.
- Enter the billing address and CVC every time.
- Send a confirmation message before you hang up, or within minutes.
- Note the call in your system the moment it ends.
None of this takes long, and all of it is the paper trail you'll want in six weeks.
Your next moves
- Open the disputed charge today and screenshot the AVS and CVC results. If they weren't run, note that plainly rather than leaving a gap.
- Pull your phone log for the day of the sale and confirm the number, time and duration. Add it to your evidence only if it matches the customer on file.
- Search your email and texts for any message to or from the customer after the call. Save every one, even a one-word reply.
- Check your recording rules before using any audio. If you're unsure, leave it out and rely on the written trail.
- Write a one-page timeline (call, confirmation, shipment, delivery, first contact) with an attachment named next to each line, then submit before the deadline. Stripe gives you one submission, so make it complete.
The spoken yes needs a witness
A phone order is built on trust, which is exactly why it's fragile in a dispute. The customer meant it when she said yes, and you meant it when you said thank you. The network wasn't there for either, so you have to bring the room with you in the form of records.
Argeback is built for the moment when the deadline is days away and your proof is scattered across a call log, an inbox and a notes app. It pulls your Stripe disputes together, drafts an evidence-backed response from what you have, and files it before the 7-day window closes, even if you're reading the notification on your phone. If phone sales are part of your business, you can see how it works at argeback.lumenlabs.works.