Need easy access to your data stored in Chargify? You can now export your data to a comma-separated values (CSV) file. Look for ‘Export’ links on the Subscriptions, Products and Customers tabs. Click the link and you will be prompted to download the file.
CSV files can be opened in Excel, Numbers, or your text editor of choice.
For more info on CSV files, check out: http://en.wikipedia.org/wiki/Comma-separated_values
Chargify now offers support for a new component type called ‘On/Off’.
On/Off Components come in handy when you want to have your customers opt in or out to an ancillary feature of your product or service. For example, if you run a hosting business and want to offer “24/7” support for an additional charge of $29.99 a month, you could create an On/Off Component for it.
On/Off Components are created like any other component. Once enabled, the customer will be charged that amount at the end of each billing cycle.
We will be updating the documentation for On/Off components shortly. For now, here is a sneak peak of the API for enabling a component on a subscription:
Version 0.3.5 of the chargify_api_ares gem has been released. This release includes support for the following Chargify features:
Thanks to @ryansch and @aeden for the contributions.
Check it out here: http://rubygems.org/gems/chargify_api_ares
We’ve just added some visibility in to our Post-Backs. If you’ve dealt with failed Post-Backs (followed by a period where we back off before resending) then you’re going to like this one.
There’s a new “Post-Back Status” section beneath the existing Post-Back settings. If we’ve experienced failures while trying to send you a Post-Back, the details of that error will show here. Plus, you’re able to easily restart Post-Backs once you’ve fixed the problem.
This morning we released an update that allows PaymentExpress users to bill their customers in Euros. To configure your site to accept Euros, begin by hovering over the arrow next to your site name. This will reveal a dropdown menu with the option to ‘Edit current site’. On the edit screen, select “EUR: Euro”.
While not always needed, we have found that it is a good idea to notify PaymentExpress when changing currencies so that they can ensure that no additional configuration changes are needed at the Gateway.
As always, you can submit any issues that may arise to http://support.chargify.com.
We received a few reports today from users that pointed to an issue related to not having the TLSv1 cipher enabled on our servers. After clearing the change with our security team we have re-enabled TLSv1 for Chargify.
For reference we currently support SSLv3 and TLSv1 for ssl connectivity. We have disabled SSLv2 due to security requirements related to PCI Compliance.
This should resolve the remaining connectivity issues but please let us know otherwise.
We are usually pretty good at catching anything that might cause adverse affects for our users. However it appears that we missed such an event a week ago when we increased the security on our web servers by enforcing only SSLv3 for SSL communication.
On Friday we learned that this change caused issues for those who are using .NET to connect to Chargify. The reported issue was that the SSL connection could not be established.
Thanks to @djbyter for being the hero on this one and quickly releasing an update to his popular Chargify.NET library. So, if you haven’t updated your Chargify.NET wrapper in a few days, you might want to go ahead and do that as soon as possible.
We’re sorry for any trouble this change caused.
Email deliverability is a continuing challenge for any business with a web presence. The last thing you want is for your email targetted at customers and leads to be stopped by spam folders, or worse, blocked entirely by an email service.
We have upgraded our email process to allow both increased deliverability in general as well as better visibility into the entire email process. This will improve the chances of Chargify-originated emails of reaching your customers and serve as a great foundation for even more email features in the future!
For the best results, you will want to ensure that you have an spf record configured correctly for your domain.
If you currently do not have an spf record set for your domain you will need to add the following TXT record:
v=spf1 a mx include:chargify.com ~all
If you already have an spf record set for your domain then include only the following part in your current TXT record value:
include:chargify.com
Interested in learning more about spf records and how they work? Check out this Intro to SPF records
It used to be that when someone added or updated a credit card on a subscription that had an overdue balance (i.e. the subscription was past due), there was a lag before we tried to capture that balance. This was because of auto-throttling we have in place for overdue subscriptions.
However, this could result in a less-than-optimal experience for everyone involved - if the customer updated the card themselves, they wouldn’t get alerted if there was a still a problem in capturing the balance. Additionally, since Post-backs would not be fired, there could be a lag between when the provide their updated billing information and when they re-gain access to your service.
Now, we automatically attempt to capture any overdue balances on subscriptions as soon as the card is added or updated. And, we send immediate feedback on the results of that attempt to wherever sent the request, whether it be the hosted update page, the “Change/Edit Credit Card” page in the admin UI, or the API.
Chargify merchants don’t need to do anything to benefit from this change. The only visible change is in the messaging, as highlighted in the following screenshots:
Last night we released support for creating refunds both in the Admin UI as well as the API. This feature allows you to issue refunds back to your customer’s credit cards for any payment that has been processed through Chargify. Support for refunds is currently limited to Authorize.Net, with the other gateways soon to follow. If you have a test site using our Chargify Test Gateway, you can try out refunds there as well.
Check out the docs:
