Archive for the ‘Payments 101.201.301’ Category

Customer Retention – the little stuff matters

Wednesday, September 8th, 2010

The three tenets of our CashBox solution are 1) to increase customer acquisition, 2) maximize customer retention, and 3) enable operational excellence for online merchants that sell digital goods & services to consumers and small business (SMB).

Acquisition is straightforward – allow consumers to choose the right product / plan at the right price in the correct language and currency, and to pay in their payment method of choice.

Operational excellence around billing and customer information is also obvious – securely store all sensitive data while managing and nurturing the overall customer relationship (PCI DSS & SOX are methods of enforcing parts of this).

Where the waters get a bit murky for some folks is customer retention…

The concept is simple. If a transaction fails, try it again, and again, and again. However, retention involves multiple moving parts, so every little detail matters and the compound effect of many small tweaks can be quite large. Some factors that make an impact on retention include:

  • Failure type
  • System availability
  • Transaction type (one-time, subscription, etc)
  • Time since last billing
  • Time between retries
  • Number of retries
  • Payment processor used
  • Transaction routing (# of stops along the way)

Many of these factors are specific to the business model used (Time between billings, transaction type) and some are the result of merchant preference (time between retries, number of retries). Yet others are system related (payment processor, transaction routing, system availability). While the first two areas can experience continual improvement with testing and optimization, the system related issues are *somewhat*out of control of the merchant. The *somewhat* refers to the fact that merchants have a choice of business partners.

Let’s take a closer look at the three system-related factors listed and how we address them.

  • System availability
    • The uptime of connections to the payment processor from the gateway, and the connection from the payment processor to the Interchange.
    • Vindicia: Part of our solution to this problem is a built-in gateway in order to eliminate uptime issues between the billing system and the payment processor. We also have hardware directly in the datacenters of certain partners with direct connections to further reduce any connectivity issues. As a final step, if the payment processor’s connection is down, we automatically queue the transactions for retry.
  • Transaction Routing
    • The number of systems involved in submitting a transaction makes a big difference. The typical flow would involve:
      • Creating a transaction in the billing system
      • Passing the transaction to a gateway
      • Submitting the transaction to a payment processor
      • Receiving information from the card network interchange
      • Capturing the transaction (or other actions, depending on processor response)
    • Vindicia: As mentioned above, we have combined the billing system and gateway (first three steps above) for more control over the transaction flow and greater payment success rates. This also gives more control over the retry logic by directly interpreting error codes from the payment processors into different retry flows. Billing companies & in-house systems that have not directly integrated to payment processors cannot compete with our results.

I’ll save descriptions of the other factors for another post. Optimizing customer retention is goal with constantly moving goalposts. When embarking down the path, merchants have a choice of either becoming experts at payment networks and card retry logic or choosing a partner that is already an established leader in the space.

Fall 2010 Webinar Series

Tuesday, August 31st, 2010

We’ve received great feedback on the topics we’ve handled with our best practice webinar series over the past couple of years (view the archives).  In addition, we constantly get new ideas from viewers on what they would like to hear about.  With that in mind, we’re happy to announce our Fall Webinar Series.  The four webinar topics delve into

  • The pros and cons of the freemium business model, much in vogue these days
  • The impact of Facebook Credits on your monetization strategy
  • A deeper look into the whole payment ecosystem with updates on recent regulatory changes
  • How to strategically manage your chargebacks

We invite you to register for these webinars and, as always, provide feedback on what you’d like to hear about.

Customer Data Ownership

Monday, August 9th, 2010

New companies are being formed every day – here in Silicon Valley, we see a lot of activity and buzz around all of the companies that are creating the next big thing. This is always exciting to follow, but for us here at Vindicia, it is doubly interesting. We take note of the business models and the target markets for these startups as we’ve built our business on meeting the needs of companies selling digital goods online to consumers. One trend we’ve been seeing lately is a sharp growth in the number of consumer-focused startups. This is great, but as many players are new to accepting direct payments from consumers, considerable thought should be given to the business strategies and how to be successful both near- and long-term.

(more…)

Secrets to Successful Implementations

Wednesday, July 14th, 2010

If I had a dollar every time I’ve heard “We have to get the project rolling right now.  We’re going to want to go live in <insert irrationally small number here> days,” I would have my own private island.

It’s natural that when companies sign a contract, the exec sponsors want to get things moving quickly.  The decision has been made, and it’s time to get on to reaping the benefits of the best SaaS platform on the market.  Looking across all of our clients, it’s easy to see who will get their implementation up and running first.  The funny thing is, it is actually independent of the size of the client, or how “process oriented” they are.  It comes down to three simple things.

1)       Defined Scope

Clients who get live quickly do so in part because they define a scope and stick to it.  There’s always a new feature to add, something that will make it even more cool, but if you want to get live, you make the conscious choice to save that new feature to phase II.

2)      Focused Resources

If your deployment team is also responsible for the corporate LAN, the CEO’s laptop support, resetting passwords for wayward users, and refilling the coffee pot, well, they’re going to have a hard time focusing on getting the work done.  (OK, a full pot of coffee probably helps, but the CEO is going to have to find the printer on his own!)

3)      Make Decisions Quickly

Even the smallest organizations can get bogged down if they debate simple questions endlessly.  Businesses don’t fail because the background on the offer page was the wrong color.  On the other hand, businesses do fail if you don’t get to market and start generating revenue.  Nominate someone from each of the key functional areas, and give them the authority to make the call.

If you adhere to these simple precepts, the implementation of a best-in-class billing system takes less time than you would imagine.

Retention, More Than Meets The Eye

Tuesday, July 6th, 2010

I am often asked about how Vindicia is able to retain more paying users than other systems – internal or competing solutions. The question is fair, what secret sauce does Vindicia possess that separates us from our competitors? The answer is a bit complicated, but in short, we have internal logic and payments experts that determine the optimal frequency and number of retries for each product in a client’s catalog and reason code returned from the payment processors.

The next question is – how well does it work? That’s easier to answer. We constantly analyze the number of transactions recovered per merchant and per industry segment and we recover between 1% – 5%  of overall transactions each month for our clients. Of course, if the transactions recovered represents a saved subscribers, the true value of our retry logic is the subscription amount times the number of billing periods that would have otherwise been lost.

The savvy online merchant might then ask – what are my industry peers acheiving? The interesting takeaway is that retention numbers and retry logic success depend more on similar business models and customer demographics than they do by industry. A facebook application offering subscriptions and targeting 25-35yo professionals would probably have more in common with Symantec or Zendough than with MouseHunt.

Finally, the question comes to  – couldn’t I build my own retry logic? Absolutely, there is nothing stopping a company from building their own internal retry logic. In fact, many successful online businesses have done just that. However, when they built their internal systems, there was no SaaS billing vendor that they could turn to. For a company to build their own system, they need to be prepared to spend large amounts of money (millions) and develop internal payments experts. That’s what our founders did at eMusic.com before they started Vindicia, and that’s the situation a lot of large online businesses find themselves in today. But I would highly recommend talking to a few companies that have built their own system before embarking down that path. The answer you’re most likely to get is – what do you want to be experts in? Your product or billing and payments infrastructure?

As a final point, as you look at other billing systems, dig in deeper to find out how they handle retention. Most of the solutions that claim to increase retention are just blindly sending the same transaction through multiple times without any adjustments or understanding of the reasons for decline. This is an area where real world results count for a lot – don’t be afraid to ask for them.