Failed transactions are an everyday part of e-commerce. As a merchant, the last thing you want to see is the error message ‘card declined.’ On average, B2C and B2B can expect a failed transaction rate of approximately 11.5%. One of the most common decline reasons is outdated card information. That’s an enormous amount of revenue left on the table for such an easy issue to fix. 

For some time now, Recurly has supported Subscription Pricing, a feature of Recurly.js designed to make it quick and easy for our merchants to display detailed subscription pricing information to their subscribers. This feature provides the ability to include any of your subscription plans, as well as a coupon code, add-ons, a gift card, etc.

Please note: This blog has been updated to reflect that Recurly’s API v2.6 will sunset rather than reach end of life. The text below has been updated to reflect this change. 

In March, we discussed how Recurly approaches the maintenance of our API, including changes, updates, performance improvements and other essentials that minimize friction and provide a top-notch development experience. API consumers who implement continuous API upgrades are afforded a variety of advantages, which our previous blog outlined and which we encourage you to review.

A few months ago, we laid out Recurly’s approach to optimizing subscription billing using machine learning. Today, we have a follow-up with more details about our approach, answers to common questions, and discussion about the improvements we’re gaining for our customers.