In an X post, Alex Konrad described a chargeback dispute with Stripe that he said had turned into a different kind of annoyance: long customer-support emails with what he called oddly personal flourishes.
Konrad wrote that he had been dealing with “an annoying chargeback situation” involving “a wrong email” and “an attempt by the reader to withdraw the dispute.” He said Stripe customer support had been sending “really long emails (400+ words) interspersed with oddly personal touches.”
Konrad also wrote that Pangram had identified the messages as “a mix of human and AI.” In the supplied evidence, that remains Konrad’s description of the result, not an independently inspected Pangram output tied to the emails he referenced.
Konrad’s preferred alternative was much simpler. “Feels like the worst of both worlds to me,” he wrote. “I would prefer a much shorter email from a human, or bullet points from an AI that didn’t pretend.”
What Stripe’s public dispute guidance covers
Stripe’s dispute best-practices documentation addresses the evidence merchants submit to card issuers when they challenge a dispute. The supplied page does not present that guidance as a policy for how Stripe support agents should write customer emails.
On that page, Stripe says card issuers “review thousands of dispute responses every day” and that “writing a long explanation to them isn’t going to make your responses more convincing.” It recommends keeping evidence “relevant to the dispute reason and to the point.”
The same documentation says merchant-submitted evidence should be “factual, professional, and concise,” and warns that unnecessary material can “obscure your argument.” On customer communications, Stripe says merchants should include “only the relevant excerpts.” If a long email thread is included, the company recommends redacting duplicated copy in the chain.
What the supplied evidence does and doesn’t show
The available material supports two narrower points: Konrad publicly made these claims on X, and Stripe publicly advises merchants to keep dispute evidence concise and relevant when responding to card issuers.
It does not establish that Konrad’s experience reflects a broader Stripe support practice. It also does not independently verify the Pangram assessment Konrad described, or identify any separate Stripe policy in the supplied evidence governing the tone or length of support emails.
Comments