Payment Processors Display Misleading Fees and Then Gaslight Users When Challenged—Written Refund Promises Are Denied, and Support Gives Contradictory Bot-Like Excuses

Summary

A payment provider’s app displayed “Fees: $0 per deposit” for a specific location; the user was then charged $4.95 at the register. A support agent promised in writing that the fee would be refunded once the payment completed, then the charge posted with no refund. Over three days, four agents gave mutually contradictory explanations—one said the $0 display was accurate, another said the displayed number was the retailer’s estimate, the chatbot cited a 2.5% fee that “doesn’t apply,” and the refund promise was retroactively declared “not accurate.” Replies were polished, templated bullet lists at 3 AM, repeatedly asking for screenshots already sent four times and misreading $4.95 as $4.59, yet insisting “I’m a human.” No supervisor ownership, no refund, and only a 15-day formal complaint process—for a $4.95 error caused by the provider’s own app. This is unsolved because payment providers control the fee display, the dispute record, and the appeal channel with no independent verification layer, no enforceable record of written commitments, and no escalation path that produces accountability. The pain is severe precisely because it is a small rehearsal of a catastrophic scenario: as the user put it, “If it fights this hard over five dollars, I don’t want to find out what happens with a real problem.” For high-risk merchants already comparing opaque 6%–12% gateway quotes against frozen reserves and slow settlement, this is the same trust failure at the core of “The Decline File”—the provider will not tell you the real fee, will not honor what it said, and no one can make it.