• Payment Plugins Poll

    We need your feedback on the need for updated payment plugins. Please go here and give us your feedback.

  • Joomla 5.1

    For running J!5.1 you must install Fabrik 4.1
    See also Announcements

  • Subscription and download (Fabrik 4.1 for J!4.2+ and J!5.1) are working now

    See Announcement
    Please post subscription questions and issues here

    We have resolved the issue with the J! updater and this will be fixed in the next release.

We Need Your Input on Updated Payment Plugins

Do you have a use for payment plugins?

  • No

    Votes: 12 33.3%
  • Yes - If yes please select which ones

    Votes: 22 61.1%
  • PayPal

    Votes: 18 50.0%
  • Stripe

    Votes: 15 41.7%
  • Mollie

    Votes: 4 11.1%
  • Quickpay

    Votes: 2 5.6%
  • Other

    Votes: 5 13.9%

  • Total voters


Staff member
Dear Team,

We are considering the need for updated payment plugins for our platform. Although we haven't received specific requests for new plugins, it's possible that the existing ones are still somewhat effective. However, we have noticed that both PayPal and Stripe have released multiple updates since our plugins were last updated.

If there is enough interest, we will assess the requirements for these updates. Please note that any new plugins will be released as add-ons and will include a subscription fee. The exact pricing has not been determined yet.

We value your input and would appreciate your feedback through this poll.

Thank you,

Team Fabrik
My support for Mollie is for 2 reasons:
1) as a general PSP, Mollie supports all debit and credit cards, PayPal, SEPA tranfers, pay later providers, Google and Apple Pay, etc. So one plugin for all.
2) they support iDEAL, which is the cheapest and most common payment method in the Netherlands. Initially set up by the Dutch banks, it now now evolves into a EU payment platform: The European Payments Initiative (EPI). So again more versatility. Please see Wikipedia iDEAL announcement
Question for all of you. How do you see the payment processors working? In the original implementation the payment is set up as form plugin that process the payment using a rest type api. This plugin gets called first in the plugin chain. We can continue to do this. But would you also want something like a Pay Now button that pops up with the payment processor of choice (pre configured choice). This second one will be more challenging.
I vote for the rest API form plugin. Also is some kind of webhook is included ? Most of the payment gateway offers both a return message with data (success/cancel/transactionID...) and a call to a webhook which allow to register the payment data even if the user close the window after having pay (for example).
I vote as well for the current REST API; a Pay Now option may be a nice addition later down the road, even as a separate plugin (if easier), but on our end can't see where that would be needed currently. As an example with our clients, we use several of Joomdonation's components and their API payment plugins work well in our experiences.
I am well through the rewrite on PayPal. Those of you who had an interest in it, are you using the original PayPal plugin now, or will this be used in new applications? Wondering how much upgrade stuff I need to do. I may just make a a new PayPal plugin which could operate beside the existing on. Would prefer though to simply abandon the existing one for the new one.

Would welcome your feedback.