Do I need this module?

Probably not, unless you clearly understand its purpose relative to other modules in the Drupal ecosystem. TL;DR: Membership module connects Drupal to external systems which are responsible for the lifecycle of a membership.

I want to sell [recurring] memberships to my site, e.g., access to a role.

Does your payment processor support tokenization?

If you can let Drupal 8 manage [recurring] payments and your payment processor will tokenize a payment method for repeat use, you probably want to use Commerce License.

Does your payment processor support subscriptions natively?

If you sell recurring subscriptions and your processor does not support tokenization but it does support subscriptions through its own mechanism, then Membership is for you. You may also need to defer to the processor for recurring billing or member data management, leaving you in a condition where you wish to only react to the external system's actions.

Examples of such payment processors are those operating in the high-risk space or the subscription features of mainstream gateways like Braintree. Think also Google Play and The iTunes store.

Commerce integration and membership provider modules are found at GitHub.

Versions

Drupal 8+

While this module shares a namespace with earlier Drupal 5/6 modules, it does not inherit any code or architecture.

Development occurs on GitHub (fork and submit pull requests there) while utilizing the Drupal.org issue queue.

This project is still very much under development and meta-discussions around future plans and architecture are welcome.

Drupal 7

There is no Drupal 7 version. See related modules, below.

Drupal 5/6

Thank you to Boobaa for the work on the initial Drupal 5 module and for coordinating the continued use of the module namespace. These earlier versions are, however, unsupported.

Related modules

Supporting organizations: 
Sponsored Development

Project information

Releases