Nov 11

SHA-2 Migration - What You Need to Know

On Dec 15, 2014 Chargify will begin using a new SSL certificate signed by SHA-2 instead of SHA-1.  The change should be seamless for most users, but old API clients may have issues.  We have set up a test system so you can check ahead of time that your API integration will continue to work. Find out what you need to know.

Oct 14

Dropping support for SSLv3 - may cause API connection problems

Effective immediately, we are dropping support for SSLv3

A new security attack (dubbed the POODLE attack) that came about today, makes continued use of SSLv3 connections very risky.

Thus, as with Twitter, HipChat, Harvest, Freshbooks, Braintree Payments (part of PayPal), and many other respected websites, we have made the quick & difficult decision to immediately stop accepting SSLv3 connections to

While this change is good for security, it may cause problems for some of our merchants and a few of their customers…

Sep 18

Editable Custom Fields

Subscription custom fields (metadata) can now be created, edited, and updated from within Chargify:

Previously, custom fields could be defined from within Chargify, but metadata could only be attached to a subscription via the API.

Read More

Aug 26

Schedule a Product Change for Next Renewal

Now you have another option to manage product changes for your customers with a new feature: Delayed Product Change. This allows you to bypass proration concerns in a smart way by telling Chargify to schedule the product change to the subscription’s next renewal date.

Aug 15

Subscription CSV Export Enhancements

Today we made Subscription CSV exports a lot better:

1. Filter results down to a subset of records, and only the resulting set of records will be exported

2. Include component allocations (current count & current cost) and estimated next billing amount