Drupal 8 Stripe

Posted onby admin
2014 24 Feb
  1. Drupal 8 Commerce Stripe
  2. Drupal 8 Structure
  3. Drupal 8 Statistics

Drupal 8 Commerce Stripe

When you sell on the internet, you customers either buy the product and pay it’s cost one time, or they buy a service or a subscription and signup to pay a recurring fee.

In this blog lets compare various ways of how you can use Drupal to build a site with recurring billing.

How it works with Stripe. Donorbox's integration with Stripe allows your donation funds to go straight to your bank account via Stripe. Sign up with Stripe or connect your existing account during our sign-up process to easily start accepting Stripe donations. Drupal Core Ajax; /. AJAX command for resetting the striping on a table. The 'restripe' command instructs the client to restripe a table. This is. usually used after a table has been modified by a replace or append command. Commerce Stripe integrates Stripe with Drupal Commerce payment and checkout system. This module will fully integrate the Stripe to Drupal Commerce in that way that clients can make payments straight in the shop in PCI-compliant way without leaving the actual shop page. Stripe is a simple way to accept payments online. With Stripe you can accept Visa, MasterCard, American. 8.x-2.x Provides a 'Stripe Checkout' field type that can be used to set the prices of a fielded entity. The field is rendered as a Stripe Checkout button, using Stripe's JS library. Users can click the button and pay the specified price. This module does not actually do anything after a charge has been completed. However, it provides two ways to react to a charge being made via Stripe: hook.

Example use cases of such a site could be -

  1. Selling software or support as a service. Such as services from Acquia.
  2. Providing access to premium content. Such as video tutorials from druaplize.me.
  3. Promoting selected content on the site. Such as featured listings on craiglist.
  4. Many more..

While some of the intricacies that separate recurring-billing from one-time billing are -

  1. Multiple plans which the customers can upgrade and downgrade between.
  2. Billing cycles and intervals.
  3. Failed payments, grace periods and retrials.
  4. Subscription management.
  5. Compliance considerations.

Now, Drupal is a great platform to build e-commerce sites of all sizes and variety because it brings together the best of many worlds - quick to start distributions + modules to extend functionality +custom development + integration with 3rd party services.

When building a Drupal site with recurring payments, you can typically think of the entire setup as made of the following components -

  • What you are selling.
  • Business logic behind the online store.
  • The payment gateway.

Available drupal modules, building custom drupal solutions and ready to use 3rd party tools have a overlap in all the above 3 areas and it is worthwhile to compare them.

Drupal + Recurly + Recurly Roles

Recurly adds a SaaS based middle layer to recurring payments and subscriptions. Key features include ability to support multiple payment gateways (http://recurly.com/gateways/), option to host customized checkout pages with recurrly or embed payment form in your website using javascript, customer care support among others. A full list of features can be found here (http://recurly.com/features/)

The two drupal modules (https://drupal.org/project/recurly) and (https://drupal.org/project/recurly_roles) together allow for quick integration of the service with Drupal sites. If you require to give certain users of your site privileged access or role, and do not need a full e-commerce store running on top of commerce module, this setup should get you there.

Drupal 8 Stripe

Example usage scenario

Drupal 8 Structure

  • Currency support = Multi currency support is provided only in the enterprise plan that comes at $299 / month.
  • Charge for 10 members paying 20 Euros per month = $99 + (10 x $0.1) + (1.25% of $275) ~ $104 + Merchant account charges
  • Charge for 500 members paying 20 Euros per month = $99 + (500 x $0.1) + (1.25% of $13744) ~ $322 + Merchant account charges

    Useful links to check out

  • https://blog.recurly.com/2010/08/top-ten-reasons-to-use-recurly-vs-gatew...

    Drupal + Chargify

    Chargify is another SaaS based recurring payments service that boasts of the standard features -https://chargify.com/features/recurring-charges/ but do not spell them out as clearly as Recurly does.

    To use this with your drupal site you would need to develop custom business logic, which can use the chargify API module as foundation - https://drupal.org/project/chargify_api

    Example usage scenario

  • Charge for 10 members paying 20 Euros per month = $65 + Merchant account charges
  • Charge for 500 members paying 20 Euros per month = $129 + Merchant account charges
  • Useful links to check out

  • https://chargify.com/features/recurring-charges/

    Drupal + Saasy (and others)

    Like recurly and chargify, there are numerous other SaaS based recurring payment services. Here is a good list and comparisions of them = http://www.practicalecommerce.com/articles/3280-9-SaaS-Subscription-Bill...

    From this list Saasy deserves a special mention because it has the most straight forward pricing, in which the merchant account costs are included in the pricing v, and there are no monthly charges. Their features are compared to other services here - http://saasy.com/matrix.php

    Customer sign ups happen on a secure, hosted SaaSy order page which can be branded to your site's look and feel, but cannot be embedded inside your site.

    Business logic in Drupal needs to be entirely custom coded to work with the Saasy APIs.

    Example usage scenario

  • Charge for 10 members paying 20 Euros per month = (8.9% of $275) = ~$25
  • Charge for 500 members paying 20 Euros per month = (8.9% of $13744) = ~$1224

    Drupal + Commerce Subscription Product

    Though this is now reported as an unsupported module, many have used it to create successful subscription systems in Drupal, including yours truly. The list of modules needed to configure a Drupal solution are -

  • Building a solution this way is recommended when you need to apply subscriptions to content on your site, to say promote certain content, though you can build priviledged roles/access based solutions too. Detailed process of building the business logic using commerce subcription product is well explained here -

    Though refunds, cancellation and customer support can be provided, they would be a challenge unless you build robust solutions for them.

    Example usage scenario

  • Currency support = All international currencies supported via paypal. Standard currency conversion rates are applicable though.
  • Charge for 10 members paying 20 Euros per month = (10 x $0.30) + (4.5% of $275) = ~$16 + currency conversion charges
  • Charge for 500 members paying 20 Euros per month = (500 x $0.30) + (4.5% of $13744) = ~$770 + currency convertion

    Drupal + Commerce License

    The project commerce license https://drupal.org/project/commerce_license has been developed from ground up to be a drupal module that allows sites running on top of drupal commerce to sell access to things. A submodule is included that allows to sell access to premium roles on the sites.

    To include recurring payment for licenses, you would have to use the modulehttps://drupal.org/project/commerce_license_billing and some amount of custom glue code for your business logic.

    Both these modules are in alpha stage, so it would be recommended to build a proof of concept before you bet on them for production use.

    Charges when using this solution would be the same as you would pay to your payment gateway for transactions and maintaining the merchant account.

    Drupal + Stripe

    Initiative has also been taken to build subscription suite for Drupal around the Stripe payment gateway, but it is not complete and does not seem to be under active development.

    Links you should check out -

  • At the moment of writing this post, this solution is not recommended.


    Based on the nature of your business, transaction volume, budgets, and developer resources, you have various options to choose from when it comes to building recurring online subscription systems in Drupal.

    There is no one single solution that can be used for everybody’s needs.

    Parting Note

    Recurring payments in drupal is an area where new and better solutions and itegrations are bound to take place at a rapid pace, so do share your experiences.

Drupal 8 Statistics

View the discussion thread.