Moving the Changelog
We’ll soon be shutting down this changelog. Instead, please visit the Changelog forum on our support site for all your latest Chargify release news: http://help.chargify.com/forums/20053862-changelog
P.S. You might want to check out our latest release: v1.7.2 adds the ability to add coupons to existing subscriptions via the admin UI!
Release v1.7.0: Taxes
Version 1.7.0 brings a brand new feature to Chargify: Taxes!
The ability to define taxes in Chargify is something that many of you, especially those in the EU, have been asking for awhile.
Check out the documentation here: http://docs.chargify.com/taxes
As always, If you have any questions, give us a shout on twitter (@chargify /cc @npverni).
Release v1.5.0: Component Enhancements
Version 1.5.0 brings a bunch of component enhancements to Chargify. These enhancements include:
- Fractional cent component pricing
- Price bracket support for Metered Components (already available for Quantity Components)
- The ability to archive components
- The ability to create components via the API
- The ability to view component allocations/usages in the Admin UI
- The ability to record usage and update allocations in the Admin UI
API users, please note: To accommodate the fractional cent change we made some adjustments on our end that altered how prices are stored. Because of this, we have deprecated the price_in_cents field in favor of the unit_price field. The price_in_cents field is still returned for backwards compatibility, but may not accurately represent the current state of the component if it has been updated since the change. We recommend updating your API calls to use the unit_price field as soon as possible.
Thanks to everyone who provided feedback and suggestions. If we missed something that you were looking for, give us a shout on twitter (@chargify /cc @npverni).
Changing the default API page size
Currently, if you fetch from the API and don’t specify a
per_page parameter, you will get a default batch of 2000 resources. Which is, basically, just way too much.
We’re making improvements to Chargify tonight which will make a fetch of 2000 subscriptions 10 to 20 times faster. However, a sample set of 2000 subscriptions results in a JSON response that is 3.2MB of text. And that’s JSON — XML would be even bigger. Even with optimized database queries, we’re burning considerable amounts of CPU just to assemble a response of that size. In short, the default of 2000 was a bad idea.
Tonight, we’re reducing the default page size from 2000 to 200 resources, so please plan accordingly. (A sample JSON response of 200 subscriptions is 320kB in size.) You can still request larger pages (using the
per_page parameter), but just be prepared to wait for it and parse the large result.
Also, make sure you note our planned downtime for tonight at 01:00EST.
Short Downtime Tonight
Chargify will be down tonight (Friday night/Saturday morning) for a short time while we make some database optimizations. This change will result in faster site and API response times.
When: Saturday, March 19, 2011 at 01:00EDT
Duration: Approximately 15 minutes
Why: Database optimizations to improve response times
Expectation: During the downtime, Chargify will return a “503 Service Unavailable” HTTP response.
If you access Chargify via a web browser during the downtime, you will see a maintenance page. Any customers who visit your hosted signup page during this time will also see the maintenance page. The maintenance page directs users to the @billingstatus Twitter account which will be kept up to date during the maintenance. The @chargify Twitter account will also be updated during the window.
If you access Chargify via the API during the downtime, you will receive a response with a blank body and a “503 Service Unavailable” status code in the header.
Release v1.2.6: Card Expiration Emails
Want to notify your customers when their credit cards will expire? Now you can! Check out the settings tab to configure card expiration emails. Your customers will be notified 3 times in the month leading up to the expiration.
Release v1.2.3 (Part 2) - Coupon Enhancements
A few weeks back we asked for your feedback on ways to improve the current coupon functionality in Chargify. We are happy to announce the release of the 3 features that got the most votes.
- Recurring coupons: Now you can configure coupons to continue to apply after initial signup. This is a great way to give customers a permanent discount. Recurring coupons can be configured to recur indefinitely or for a fixed period of time.
- Remaining credit: Coupons can now be configured to leave a remaining negative balance after they are applied. For example, if a customer is subscribes to a $70 product with a $100 coupon, they will be left with a -$30 balance.
- Delay until after Free Trial: Previously, if you have a product with a free trial, any coupons applied to those subscriptions would be ignored. Now, you can configure coupons to delay their application until after the free trial is up.
For more information, check out the updated coupon documentation: http://docs.chargify.com/coupons
Release v1.2.3 (Part 1) - Cancel at end of Pay Period
One feature that many users have asked for is the ability to delay the cancellation of subscriptions until the end of the pay period. This especially comes in handy when you have a product that customers pay for in advance.
You can now accomplish this in Chargify via the Admin Interface as well as the API. For more info, check out the relevant docs:
Cancellation UI: http://docs.chargify.com/cancellation
Subscription Update API: http://docs.chargify.com/api-subscriptions (see the cancel_at_end_of_period option for updates)
- Fixed a bug that caused blank return params when the signup was completed without a credit card
- Changed statement language for “Balance Due” to “Ending Balance” to clear up confusion over having a positive “Balance Due” and a “PAID” stamp at the same time
- Fixed a bug that resulted in an Internal Server Error when search results returned enough results to require pagination