Incompatibilities and Deprecations

As our development team continues to improve the core Paid Memberships Pro plugin and other PMPro Add Ons, occasionally Add Ons get merged into core or we suggest alternative solutions. Along with this, there are cases where an integration that used to exist, such as a payment gateway, will no longer be actively developed.

In this compatibility guide, we cover three categories of Add Ons that we no longer recommend using and why. We also explain why a payment gateway may no longer be supported and what that means for your membership site.

Add Ons Merged Into Core Paid Memberships Pro

With PMPro v3.0, we merged the ability for members to hold multiple membership levels at one time in the core plugin. This version also included merging two other popular premium Add Ons into core, including:

• Cancel on Next Payment Date Add On
• Stripe Billing Limits Add On
• Multiple Memberships Per User Add On

In previous releases, there were a few other Add Ons that were merged into core. If you see mention of the following Add Ons on our site or anywhere else on the internet, these Add Ons are also now part of the fully open source core plugin:

• Register Helper (now handled via User Fields settings screen).
• Member History (now a feature of the Edit Member screen).
• Email Template Admin Editor (now handled via the Email Templates settings screen).
• Better Logins Report (now offered with the Visits, Views, and Logins report).

Deprecated and No Longer Recommended Add Ons

These Add Ons have been replaced by new features in the core Paid Memberships Pro plugin or by newer Add Ons. The Add Ons below are now deprecated and should no longer be used.

Add Member From Admin Add On

The Add Member From Admin Add On allowed users with the admin or membership manager role to create a new user, add membership level settings, and optionally create an order in one single step.

Paid Memberships Pro v3.0 and higher now includes a better pathway to create a new member and adjust their memberships. Navigate to Memberships > Members and click + Add Member.

Recurring Payment Email Reminders Add On

The Recurring Payment Email Reminder Add On was a premium Add On that sent an email to remind members that their next recurring subscription payment is processing soon that has been deprecated.

Paid Memberships Pro v3.2 and higher now includes this email template within the list of email templates. Edit this template by navigating to Memberships > Settings > Email Templates > Recurring Payment Reminder.

Sponsored Members Add On

The Sponsored Members Add On was a code-based system and has been deprecated. Alternatively, we recommend the new Group Accounts Add On. This new Add On has more features and a no-code setup.

Avalara: AvaTax Integration

This Add On is being deprecated and will only receive minor updates and small bug fixes. We are working on other tax solutions for membership sites. For more information about taxes with PMPro, please read the guide here: Methods to Calculate and Apply Taxes with Paid Memberships Pro.

Add Ons Not Compatible With Multiple Membership Per User Setups

These Add Ons are not compatible when you have a site that allows members to hold multiple membership levels at a time. If your site only offers one level group where members are restricted to one active membership level at a time, these Add Ons will work for you as-is. We cannot guarantee we will continue to support these plugins over time.

Discord Integration

The Discord Integration plugin automatically sets their Discord Server Role based on their membership level in Paid Memberships Pro. While the Discord Integration is an active third party plugin, it is designed for sites where members are restricted to one active membership level at a time.

Payflow Recurring Orders Add On

The Payflow Recurring Orders Add On is designed for sites where members are restricted to one active membership level at a time. If you are looking for recurring payment options with the ability for members to hold multiple membership levels at one time, please see our other payment gateway recommendations.

Deprecated Payment Gateways

When we deprecate a payment gateway in Paid Memberships Pro, it means that we’re phasing out support for that gateway in future updates.

This is not a decision we take lightly. We are committed to maintaining existing integrations for as long as we feasibly can do so, especially because this decision impacts businesses built on the PMPro platform. But, due to various technical or compliance-related reasons, there are reasons why we must occasionally deprecate a payment gateway.

Quality of the Gateway’s Development and Compatibility

Payment gateways like Stripe and PayPal regularly update their APIs and technical standards. These updates ensure compatibility with new security protocols, compliance requirements (like PCI compliance and Strong Customer Authentication), and new features that benefit your membership site.

When a gateway stops updating its technology, or if it requires us to work with outdated APIs, it can limit the functionality and security Paid Memberships Pro provides for your site.

If we determine that a gateway we integrate with is no longer being actively developed in a way that we can build for, we will choose to deprecate that gateway.

Sustainability, Effort, and Focus

As an open-source project, we prioritize building and maintaining integrations with gateways that offer modern, robust APIs that align with where we want Paid Memberships Pro to grow.

When a gateway falls behind on updates or becomes complex to support, we evaluate whether it makes sense to continue investing our resources in its upkeep.

For example, with the recent decision to deprecate the Authorize.Net gateway, our integration relied on an outdated API version that lacked support for critical security features.

Transitioning to a New Gateway

Deprecation does not mean that the gateway will instantly stop working. Your site can still accept payments through the deprecated gateway, allowing you to plan a transition at your own pace. We recommend transitioning to a supported gateway, like Stripe or PayPal, to keep your site current with the latest security and compliance standards.

A Path for External Development

If you still want to use a deprecated gateway, consider working with a developer to create a custom integration based on the latest APIs. This option can help you retain your preferred gateway with the necessary functionality and security for your site.

For more information on updating gateways, see our guide on switching payment gateways. This allows you to bring new members into the updated gateway while keeping existing members on the older gateway until they naturally transition over time.