Tuesday, July 23, 2013

Credit Card Recurring Bills, do you use tokens?

Our business is based on monthly recurring billing but our architecture, set up nearly a decade ago, is stupid.  Basically, when a user signups, we put their credit card info into our merchant account at the credit card processing place and tell it to bill them monthly. If they cancel or make changes, we go in manually and change it. If their credit card declines, we get the report and also go through it manually. Lots of man hours.  Some mistakes. Yick.

It seems that a better system would be to start by placing the credit card at the vendor's shop (ie no change) but then to trigger the billing by sending over a file, presumably daily, of who to bill and how much. This is the "token" part.  As part of this, we should get back a decent automated report of successful  and not successful billings.

Is anyone out there who is a small business (tier 3), say under $25 million, using tokenized billing for recurring credit card billing. I'd like to share experiences.


1 comment:

BBat50 said...

We wish we had started with tokenization but we didn't, we are on recurring billing like you.

We have an elaborate overly-complex system where we update credit cards, change billing plans, and make other modifications at th eAPI level but each one is a custom set of code that relies on some flaky API calls from our vendor.

We keep looking at changing to a cleaner more updated tokenization system. This might be the year.