Ready-made modules
Integrations with CMS platforms | MULENPAY
These platforms have a ready-made payment module: install it and enter the keys from your dashboard.
WordPressMulenPay connects to WordPress through a ready-made payment gateway for WooCommerce: the plugin adds a payment method to the standard checkout, creates the payment and updates the order status from the webhook itself. There is no integration to write from scratch.1C-Bitrix1C-Bitrix has a ready-made module: it adds MulenPay to the store's payment systems, redirects the customer to the payment page and updates the order status itself once the payment is confirmed.OpenCartThe OpenCart module adds MulenPay to the payment methods and lets you control when it shows: a minimum order total, a geo zone and the status assigned to an order once it is paid.PrestaShopThe module for PrestaShop 1.7+ and 8.x creates the order in an awaiting-payment status, builds the payment through the MulenPay API and, once confirmed, moves the order to "Payment accepted" — or to "Cancelled" if the payment was cancelled.DrupalThe Drupal module provides a payment-creation service and a ready webhook endpoint. Unlike out-of-the-box store modules, you wire the payment call into your own code — the module gives you a method, not a checkout button.JoomlaThe Joomla module installs as a regular zip archive and exposes a helper that returns a payment link. You embed the pay button into your own e-commerce component — the module handles creating the payment, not the checkout.InSalesInSales connects not through a plugin but through a small Node.js relay service: the store sends the buyer to its address, the service creates the payment in MulenPay, and after payment it records the transaction on the InSales order.TildaThere is no ready-made payment module for Tilda — the platform connects payment systems from its own fixed list. You can still accept payments: a payment link is created in the MulenPay dashboard and attached to a button in any block.amoCRMThere is no ready-made amoCRM app, and manager-led sales hardly need one: a payment link is created in the MulenPay dashboard and sent to the client straight from the deal card — by email, chat or messenger.Bitrix24Bitrix24 is a CRM and should not be confused with 1C-Bitrix: an online store on 1C-Bitrix has a ready-made payment module, while in the CRM payment is sent to the client as a link from the deal card.GetCourseWe have no ready-made payment module for GetCourse: the platform works with its own list of payment systems. Payments can still run through a payment link — it is sent to the student by email or messenger, and access is granted once the payment is confirmed.ModXWe have no ready-made payment module for ModX. There are two working paths: the quick one is a payment link on a button, and the thorough one is an API integration your developer builds into the site or into an add-on such as miniShop2.MoodleWe have no ready-made payment plugin for Moodle. You can take money through a payment link and enrol the student once the payment is confirmed, or automate it by building your own enrolment plugin on top of our API.WebflowA ready-made payment module for Webflow does not exist and cannot: the built-in store works only with the platform own list of payment services. You can still accept payments through a payment link placed on a button of an ordinary page, bypassing the built-in cart.
Your platform is not on the list? Write to us — we will suggest connecting through the API or a payment link.
Comparison
How the platforms differ
On some the payment method appears at checkout on its own; on others the module exposes a method and a developer embeds the button
| Platform | How it connects | What it takes |
|---|---|---|
| WordPress | Payment method at checkout | A WooCommerce plugin |
| 1C-Bitrix | Payment method at checkout | A module in /bitrix/modules plus a payment system |
| OpenCart | Payment method at checkout | Module files copied into the store root |
| PrestaShop | Payment method at checkout | Module installed from the admin panel |
| Drupal | Payment-creation method for a developer | A service call from your own code |
| Joomla | Payment-creation method for a developer | A function call from your own component |
| InSales | Payment-creation method for a developer | Your own server with Node.js 18 or newer |
| Tilda | Payment link, no module | A button with a link in a Tilda block |
| amoCRM | Payment link, no module | A payment link sent from the deal card |
| Bitrix24 | Payment link, no module | A payment link sent from the deal card |
| GetCourse | Payment link, no module | A payment link sent to the student |
| ModX | Payment link, no module | A link on a button or an API integration |
| Moodle | Payment link, no module | A payment link or your own enrolment plugin |
| Webflow | Payment link, no module | A button with a link on a Webflow page |
Questions and answers
Common questions about integration
What people ask before installing a module
WordPress and WooCommerce, 1C-Bitrix, OpenCart, PrestaShop, Drupal, Joomla and InSales. Each platform has its own step-by-step guide.
Use the REST API, the payment widget or a payment link: they do not depend on a CMS and work with custom sites and mobile apps.
For ready-made modules a site administrator is enough: install the module, paste the Shop ID and Secret Key, and set the webhook URL.
In the dashboard, under the store API keys. Keys are issued and revoked there, and you can rotate them at any time.
Cards, SBP and Pay services — the same set as with a direct integration. Fiscal receipts are generated automatically.
Need help with the integration?
Write to us — we will help install the module and verify that payments work.
Phone
+1 (767) 555-0147
International number
Telegram bot
@mulen_support_bot
Quick answers 24/7
Legal address
RBY Commerce Ltd.
8 Copthall, Roseau Valley, 00152, Commonwealth of Dominica
Leave a request
Fill out the form — a manager will get in touch, tailor the terms and help with the integration.
