Finally stopped using "convenience fees" as a catch-all label in my app receipts

For months I was just slapping a "convenience fee" on every small transaction my payment app processed. Then a customer in Austin flagged it saying it looked like a hidden charge and they almost disputed it. I checked my processor's rules and sure enough you have to specify what that fee is for like same-day processing or card type. Now I break it out line by line and my dispute rate dropped 12% in 2 weeks. Has anyone else dealt with vague fee labels causing chargebacks?

3 comments

3 Comments

alexc9310d agoMost Upvoted

Nah I actually disagree with both of you. Breaking fees out line by line can backfire too. I tried that and customers started picking apart each line like they were auditing me. "Why is this 30 cents for processing? Why that percentage?" It just created more questions. Sometimes a flat "service fee" is cleaner and less confusing for everyone. Plus hiding behind a bunch of numbers doesn't automatically build trust. A simple honest label works if you explain it once on your website or terms page. People hate surprises sure but they also hate reading a receipt that looks like a tax form.

david3719d ago

Adding to what you said about them looking like hidden charges, I found that being upfront about why the fee exists actually builds trust with customers. Once I started slapping a one-liner like "2.9% for Visa/MC processing" next to the fee line, people stopped questioning it as much. Surprising how a little clarity can cut down the hassle on both ends.

derek65619d ago

Yeah "a little clarity can cut down the hassle" is honestly the key. I've noticed it everywhere, not just business stuff. Like when someone at Chipotle just says "that'll be extra" instead of listing the add-on price, you feel kinda cheated. But if they just say "guac is $2" you're like cool whatever. People just hate surprises with money.