Welcome to the Chargify Support Center

There are several ways to get Chargify help!

  • Make sure you've read our Documentation. These docs contain most of what you need to know.
  • The Forums are a wealth of tips, tricks, and user-to-user help, all moderated by Chargify staff.
  • For technical questions or issues, you can open a ticket. Normal turn-around time is several hours for critical issues and several days for non-critical issues.
  • For sales and business questions, call 1-800-401-2414.
  • Ask Twitter. We have a vibrant community and they will often answer tweets to help others. Include @Chargify in your tweet.

 
 

Chargify Support

v1.14.5 Released

Michael O Klett Jan 25 • Announcements / Changelog

  • Slight API CHANGE: Usages listings are now paginated by default! This endpoint now takes a `page` and `per_page` parameters, as well as `since_id` and `max_id` to filter your results. See "List Usage" on http://docs.chargify.com/api-metered-usage
  • Hosted card update pages are now guarded by a basic fraud-detection device: after several card update attempts on a given subscription, subsequent attempts will be blocked
  • Added an `archived` attribute to the component API responses which returns `true` or `false` (See "Component Output Attributes at http://docs.chargify.com/api-components)
  • Switched the JSON encoding library used on the Subscriptions index API JSON for faster responses (this time, incoming JSON is parsed the old way so as not to cause any changes)
Known Bugs:
  • The webhook test is not working in all cases
  • Not all component types are returning the `archived` flag.

Hosted Page Change: Use GET not POST

Kori Francis Jan 24 • Announcements / Changelog

Previously, you could have used POST to GET the hosted pages. We've recently locked this down so that it's no longer allowed to serve the hosted pages in response to a POST.  You will need to use a proper GET request instead.

If you do see the following error, please check the HTTP verb that you're initially using:

The change you wanted was rejected.
Maybe you tried to change something you didn't have access to. 

Why was this change made?

We deployed this change as a security countermeasure against potential Cross-Site Request Forgery attacks.  Ensuring that the proper HTTP request verbs are used to render the hosted pages helps keep our system and your users safe.

If you have any issues related to this, please open a support ticket.

 

Overview | Recent

Getting Started