Our documentation has moved!

You are currently viewing a legacy version of our help articles.
For the most up-to-date version, please use the new Chargify Help & Support Site.

Chargify Direct out of beta - generate your own credentials

We're happy to announce that we've officially taken Chargify Direct out of beta.  Some of our largest merchants with the most recognizable names are using Chargify Direct to control the customer signup experience on their own site while offloading PCI worries by not having to process or transmit the credit card number.  We're going to continue to add features to this service, but as of now, the core service is completely stable and ready for all merchants.

You can read more about the technical aspects of Chargify Direct in our docs: http://docs.chargify.com/chargify-direct-introduction

You can also generate (and regenerate) your own Chargify Direct credentials from the Settings pane of your Chargify Site.  (Note that, unlike API v1 credentials, Chargify Direct credentials are per-site instead of per-account)

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


  • 0
    Dan Bowen

    This is awesome news! I've integrated Chargify Direct into our self-service portal (http://www.getchargely.com) and it's been working great for us so far.

    Were any notable changes made recently that made you decide to take it out of beta? Are there any specific changes that might break backwards compatibility with existing integrations?

    I am going to re-test our integration but was just curious if there is anything I should look out for.



  • 0
    Edward Wielage

    Hi Michael,

      I am able to create subscription using provided Chargify Direct Ruby example. But when I try to do it with ASP.NET or HTML, I am getting invalid signature error despite of providing all valid data. 

      we are using the signature key , created from http://chargify-direct-signature.heroku.com/ .

      Do you have some ASP.NET or plain HTML examples for Chargify Direct ?

      Please, help us to resolve this error as earliest as it is shoo stoppers for us. 

    Thank you. 

  • 0
    jason warren

    i got the exact same problem.  anyones have found a solution ? 

  • 0
    Tim Shnaider

    I can verify both signup and card_update work fine, here is Node JS code for card_update.  

    I wasted about 1 1/2hrs trying to get card_update working before reading the documentation carefully and noticing that subscription_id was required in secure[data].


    var siteChargifySettings = self.siteVersion.getIntegration('chargify').settings;

    var formData = {};

    formData.api_id = siteChargifySettings.direct_api_id;

    formData.nonce = self.generateId();

    formData.timestamp = Date.now();

    formData.secureData = 'subscription_id=' + activeSubscription.id + '&redirect_uri=' + encodeURIComponent('http://test2.portal.test.com:8080/chargify/creditcardupdated');

    formData.url = 'https://api.chargify.com/api/v2/subscriptions/' + activeSubscription.id + '/card_update';

    formData.signature = crypto.createHmac('sha1', siteChargifySettings.direct_api_secret).update(siteChargifySettings.direct_api_id+formData.timestamp+formData.nonce+formData.secureData).digest('hex');

Please sign in to leave a comment.
Powered by Zendesk