As a developer, I tend to like clean, concise URLs that map directly to my RESTful resources.  Want to view a subscription?

GET /subscriptions/77

Want to edit it?

GET /subscriptions/77/edit

The URLs for Chargify hosted pages followed this convention.  Updating credit card details loosely maps to editing the subscription to change the payment information.  So, we had:

GET /h/subscriptions/77/edit/abcdef0123abcdef0123abcdef0123abcdef0123

With the ‘h’ part meaning our “hosted” namespace, and the gibberish at the end being a secret token.

Now, if I were a layperson, and IF I happened to glance at the URL for the page I was about to enter my credit card on, which one of the following would be more likely to give me warm fuzzies?

We released several new features for Chargify this week that definitely deserve mention.

Multi-Site Support

Before, when you created a Chargify account, you were given 2 “sites”: 1) your “live” account and 2) your “test” account.  This structure was somewhat limiting, both for us and our customers.  We re-architected how Sites (now with a big “S”) work, and now, you can create as many Sites as you want, and you can move them in and out of test mode.

Each Site has its own Customers, Subscriptions, and Settings.  This means each site configures its own:

• Subdomain
• Gateway settings
• Email Templates (more on that later)
• Dunning Settings

This also opens us up to support other sorts of things in the future that aren’t compatible when you only have 1 production site… like multiple currencies.  (We haven’t committed to a roadmap for multi-currency, but we do know the need is there and we want to make sure we’re ready).

As a startup, we face many of the classic trade-offs between getting things done quickly and getting them done the best way possible. The right answer is usually somewhere in the middle. Since we’re dealing with our customers’ money and business transactions, we err on the side of doing things slowly and methodically, especially on core issues.

GATEWAY COVERAGE

Hundreds of people want us to add other payment gateways. This is absolutely true for people outside the USA, because they can’t use our currently-supported gateway, Authorize.net, which means they can’t use Chargify. And that’s a shame!

We’ve been gathering info since November on what gateways people want. In parallel, we’ve been investigating ways to add gateways - quick ways vs best ways.

If you’re a developer, you might ask why we don’t write code for each of the different gateways’ APIs. Especially with things like ActiveMerchant (in Rails), we should be able to add gateways very quickly. Yes, but…