Robust subscription support for Ruby on Rails apps using Stripe, including out-of-the-box pricing pages, payment pages, and subscription management for your customers. Also makes it easy to manage logic related to new subscriptions, upgrades, downgrades, cancellations, payment failures, and streamlines hooking up notifications, metrics logging, etc.
To see an example of Koudoku in action, please visit Koudoku.org.
Koudoku is authored and maintained by Andrew Culver. If you find it useful, consider checking out Churn Buster. It's designed to help you handle the pain points you'll run into when doing payments at scale.
Include the following in your Gemfile:
gem 'koudoku', :git => 'https://github.com/andrewculver/koudoku.git'**Note: ** For the time being, please use this repository directly and do NOT use the gem from RubyGems. The gem is really out of date and causing all kinds of trouble
After running bundle install, you can run a Rails generator to do the rest. Before installing, the model you'd like to have own subscriptions must already exist. (In many cases this will be user. It may also be something like company, etc.)
rails g koudoku:install user
rake db:migrateAdd the following to app/views/layouts/application.html.erb before your <head> tag closes:
<%= yield :koudoku %>(This allows us to inject a Stripe <script> tag in the correct place. If you don't, the payment form will not work.)
After installing, you'll need to add some subscription plans. (You can see an explanation of each of the attributes in the table below.)
Plan.create({
name: 'Personal',
price: 10.00,
interval: 'month',
stripe_id: '1',
features: ['1 Project', '1 Page', '1 User', '1 Organization'].join("\n\n"),
display_order: 1
})
Plan.create({
name: 'Team',
highlight: true, # This highlights the plan on the pricing page.
price: 30.00,
interval: 'month',
stripe_id: '2',
features: ['3 Projects', '3 Pages', '3 Users', '3 Organizations'].join("\n\n"),
display_order: 2
})
Plan.create({
name: 'Enterprise',
price: 100.00,
interval: 'month',
stripe_id: '3',
features: ['10 Projects', '10 Pages', '10 Users', '10 Organizations'].join("\n\n"),
display_order: 3
})To help you understand the attributes:
| Attribute | Type | Function |
|---|---|---|
name |
string | Name for the plan to be presented to customers. |
price |
float | Price per billing cycle. |
interval |
string | Optional. What is the billing cycle? Valid options are month, year, week, 3-month, 6-month. Defaults to month. |
stripe_id |
string | The Plan ID in Stripe. |
features |
string | A list of features. Supports Markdown syntax. |
display_order |
integer | Order in which to display plans. |
highlight |
boolean | Optional. Whether to highlight the plan on the pricing page. |
The only view installed locally into your app by default is the koudoku/subscriptions/_social_proof.html.erb partial which is displayed alongside the pricing table. It's designed as a placeholder where you can provide quotes about your product from customers that could positively influence your visitors.
You can supply your publishable and secret API keys in config/initializers/koudoku.rb. However, by default it will use the STRIPE_PUBLISHABLE_KEY and STRIPE_SECRET_KEY shell environment variables. This encourages people to keep these API keys out of version control. You may want to rename these environment variables to be more application specific.
In a bash shell, you can set them in ~/.bash_profile like so:
export STRIPE_PUBLISHABLE_KEY=pk_0CJwDH9sdh98f79FDHDOjdiOxQob0
export STRIPE_SECRET_KEY=sk_0CJwFDIUshdfh97JDJOjZ5OIDjOCH(Reload your terminal for these settings to take effect.)
On Heroku you accomplish this same effect with Config Vars:
heroku config:add STRIPE_PUBLISHABLE_KEY=pk_0CJwDH9sdh98f79FDHDOjdiOxQob0
heroku config:add STRIPE_SECRET_KEY=sk_0CJwFDIUshdfh97JDJOjZ5OIDjOCHBy default a pricing_path route is defined which you can link to in order to show visitors a pricing table. If a user is signed in, this pricing table will take into account their current plan. For example, you can link to this page like so:
<%= link_to 'Pricing', main_app.pricing_path %>(Note: Koudoku uses the application layout, so it's important that application paths referenced in that layout are prefixed with "main_app." like you see above or Rails will try to look the paths up in the Koudoku engine instead of your application.)
Existing users can view available plans, select a plan, enter credit card details, review their subscription, change plans, and cancel at the following route:
koudoku.owner_subscriptions_path(@user)In these paths, owner refers to User by default, or whatever model has been configured to be the owner of the Subscription model.
A number of views are provided by default. To customize the views, use the following generator:
rails g koudoku:viewsKoudoku ships with a stock pricing table. By default it depends on Twitter Bootstrap, but also has some additional styles required. In order to import these styles, add the following to your app/assets/stylesheets/application.css:
*= require 'koudoku/pricing-table'Or, if you've replaced your application.css with an application.scss (like I always do):
@import "koudoku/pricing-table"While more robust coupon support is expected in the future, the simple way to use a coupon is to first create it:
coupon = Coupon.create(code: '30-days-free', free_trial_length: 30)Then assign it to a new subscription before saving:
subscription = Subscription.new(...)
subscription.coupon = coupon
subscription.saveIt should be noted that these coupons are different from the coupons provided natively by Stripe.
The included module defines the following empty "template methods" which you're able to provide an implementation for in Subscription:
prepare_for_plan_changeprepare_for_new_subscriptionprepare_for_upgradeprepare_for_downgradeprepare_for_cancelationprepare_for_card_updatefinalize_plan_change!finalize_new_subscription!finalize_upgrade!finalize_downgrade!finalize_cancelation!finalize_card_update!card_was_declined
Be sure to include a call to super in each of your implementations, especially if you're using multiple concerns to break all this logic into smaller pieces.
Between prepare_for_* and finalize_*, so far I've used finalize_* almost exclusively. The difference is that prepare_for_* runs before we settle things with Stripe, and finalize_* runs after everything is settled in Stripe. For that reason, please be sure not to implement anything in finalize_* implementations that might cause issues with ActiveRecord saving the updated state of the subscription.
During the installation process, a path and API key will be printed out that you can configure in the Stripe account panel that will allow your application to receive information about recurring transactions as they happen. (These are useful for reacting to expired credit cards on file and revenue tracking.)
Support for Stripe Webhooks is still quite limited. You can implement the following template methods of the Subscription:
payment_succeeded(amount)charge_failedcharge_disputed
As mentioned before, be sure to call super in your implementations. No additional information from Stripe is currently handled from the webhook request body.