The most important conversation of your sale may already be gone, and the person who can make it disappear is the one disputing you.
Picture a small seller. She sells custom illustrations, and every deal happens in Instagram DMs. The buyer sends a rough idea. She quotes a price. They go back and forth about revisions, and he says, in so many words, "yes, that's perfect, send the invoice." He pays through a Stripe link. Three weeks later the charge comes back as a dispute: unrecognized, or not as described, depending on the day he picks.
She opens the thread to prove it, and it's thinner than she remembers. A few messages are marked unsent. The part where he approved the final sketch is a gray line that says a message was removed.
This is the quiet hazard of selling in chat. The relationship feels warm, informal and human, which is why you do it there. But the record sits on a platform you don't control, and the other person can edit it.
Why chat is weaker evidence than email
A chargeback reviewer works for the card issuer. They read a short file, usually in minutes, and they have no way to call anyone. They are looking for a coherent story supported by records that look hard to fake.
Email has a head start here. It carries headers, addresses and timestamps, and it feels institutional. A cropped screenshot of a chat bubble carries almost none of that. Anyone can produce one in an image editor, and reviewers know it. A lone screenshot isn't worthless, but it is easy to discount.
Chat has three specific weaknesses:
- Deletion is asymmetric. On Instagram and WhatsApp, a sender can unsend messages. On Discord, users can delete their own messages, and moderators can delete others'. Your copy may lose half the conversation without warning.
- Disappearing modes exist. Instagram's vanish mode and WhatsApp's disappearing messages are designed to leave nothing behind. If a deal happened in one, assume you have to reconstruct it.
- Identity is soft. A handle isn't a cardholder. A reviewer has no reason to believe that @moonlit_buyer22 is the person whose card was charged unless something ties the two together.
That last one is the real gap, and it's the one most sellers never think about.
The idea: tie the chat to the charge
The lesson isn't "don't sell in DMs." It's that a chat only counts as evidence once it's anchored to the payment on both ends. You need a bridge from the conversation to the transaction, and the bridge has to exist before anyone is angry.
Think of it as three links:
- Who: something connecting the chat handle to the cardholder's name or email.
- What: the terms they agreed to, stated in one place a stranger can read.
- When: a visible sequence showing agreement, then payment, then delivery.
A raw thread rarely supplies all three. A thread plus a few deliberate habits does.
Move the key moments somewhere durable
You can keep the whole sales conversation in chat and still make the decisive moment survive. The trick is to restate it in a medium that leaves a record the customer can't retract.
After the buyer says yes, send the checkout or invoice link and write something like: "Confirming: one custom portrait, two revisions included, $180, delivered as a digital file within ten days. Pay here when you're ready." Then, once they pay, Stripe emails them a receipt to their real address, and your payment link or invoice can collect their email at checkout.
Now the story has anchors. The chat shows the negotiation, the invoice shows the terms in your words, and the Stripe payment shows the email and card details. That email gives you a legitimate way to reach them outside the chat, so one confirming message like "Your illustration is delivered. Here's the download link" lands in their inbox, not just their DMs.
None of this is adversarial. It reads as ordinary professionalism, and it happens to be what a dispute reviewer wants.
Capture the thread properly, not just prettily
When a dispute does arrive, the quality of your capture matters. A tight screenshot of the three best messages is the weakest version. Better practice:
- Show the whole arc. Scroll from the first contact to the final delivery, with each screenshot overlapping the last so nothing is missing between them. A reviewer should be able to see that no messages were skipped.
- Keep the header visible. The account name, profile and the date separators give context a cropped bubble can't.
- Use the platform's own export when it exists. WhatsApp lets you export a chat from a conversation's menu. Instagram and Discord both let you request a copy of your account data, though it may take time and the formats vary, so check what yours contains. Exports aren't magic proof, but they show the text in order and are harder to dismiss as hand-edited.
- Save it now, in two places. If the customer unsends something tomorrow, the copy you saved today is the one that counts. A folder per order, named with the Stripe charge ID, keeps this from becoming a scavenger hunt.
One caution: don't alter, annotate over, or "clean up" screenshots. Put your commentary in the written response instead. A marked-up image looks like manipulation.
What to do when the other side unsent the good part
If messages have vanished from the buyer's side, say so plainly and stay factual. Don't accuse. Something like: "The customer's approval of the final design was sent on this date; the message later shows as removed in the thread. The surrounding messages, the payment link sent immediately after, and the customer's payment within minutes are consistent with that approval."
Then let the other records carry the weight: the timestamps on your payment link, Stripe's record that the payment completed, the delivery email, any download logs. Reviewers don't need a perfect transcript. They need the sequence to be believable, and a gap that you describe honestly is more credible than one you try to hide.
If the conversation was in disappearing mode, don't pretend otherwise. Build the case from what survives outside the chat.
Your next moves
- Today, pick your last five chat-based sales and check whether each thread is intact on your side. For any that matter, save a full-arc capture or an official export into a folder named after the Stripe charge ID.
- Add a confirming message to your sales routine. Before sending a payment link, restate the product, price, what's included and the delivery timing in a single message.
- Collect the buyer's email at checkout on every link you send in chat, so you have a real address that connects the handle to the cardholder.
- Send the delivery in two places. Deliver in the chat if you like, but also email the file or access link, and keep a copy of that email.
- Turn off disappearing messages on your side of business conversations where the app allows it, and tell customers politely that you keep order records.
Where this leaves you
Selling through conversation is how a lot of small, human businesses work, and it shouldn't have to feel risky. The risk lives in the seam between a warm chat and a cold payment record, and a few deliberate habits close it.
Argeback is built for the moment after the seam fails. It ingests your Stripe disputes, helps assemble the evidence you did keep, including chat captures and delivery records, into a clear response, and files it before the seven-day deadline, even from your phone. If your deals live in DMs, you can see how it works at https://argeback.lumenlabs.works. Either way, save today's threads tonight.