Can I add support for a membership plugin that isn’t in the supported list?

Yes, but it’s a real development project. Benecaster’s bridge system is built around a documented BridgeInterface contract, and implementing one means writing a PHP class that translates your membership plugin’s subscription model into Benecaster’s — tier lookups, user status, and event callbacks for activation, cancellation, tier changes, renewals, and payment failure. You’ll also need to understand the target plugin’s own API well enough to hook into those events reliably.

Once implemented, your bridge registers via benecaster_boot and Benecaster’s core, token system, and subscription events all route through it automatically — no core modifications needed. The full interface reference and a worked example are in the developer documentation.