Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I do have the occasional customer claim to have "cancelled 3 months ago" via email. We keep good records of such things, so we know him to be mistaken but I always make a point of apologizing and issuing an immediate refund.

I word my "Why did you open a chargeback" mails the same way, and offer to handle things via a refund (and to please close the dispute because it affects our business). But the people who use their credit card company instead of email or the prominent Cancel button on the website don't tend to ever respond to those mails.

It's frustrating, because so many people have had to deal with health clubs and Comcast that they just assume every business will fight against them if they want to cancel.



Perhaps the ethical thing to do in those situations is to fight the dispute? Acquiescing encourages bad actors.

Your current course of action is probably still best for your business and sanity, though. Hmm...

I assume you send an invoice/receipt email every month by default, to reduce the chance that a user forgot to cancel and to make it easier for those that wish to. (If not, I think Stripe Billing offers this, though I'm not sure...)

(disclaimer, I work at Stripe, though not on Radar or Billing, thoughts my own, etc)


  But the people who use their credit
  card company instead of email or
  the prominent Cancel button on the
  website don't tend to ever respond
  to those mails.
What's the user experience for someone whose credit card details have been stolen and used to sign up for your service?

Presumably such a person wouldn't have the credentials, the e-mail, or the cancel button?


> We keep good records of such things, so we know him to be mistaken

I assume Coschedule also believe they keep good records of such things, and indeed when they checked those records, they found I had cancelled when I said I did, but they'd continued to bill me anyway. You are truly exceptional to run a business where mistakes never happen, and when they do, they are always the customer's fault.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: