Payment widget
A small snippet of code — and your site accepts cards, SBP and Pay services right on the product or service page. The customer never leaves for a third-party address, while card details are entered in the secure MulenPay form, not on your server.
shop.example.com
Product page · #4821
MulenPay.widget('checkout').mount('#pay')On-page checkout
LiveCard
Wallet
Bank
PCI DSS COMPLIANT
What it is
The widget is a checkout form that opens on top of your page: the customer sees your site, your order and the amount, enters card details or picks SBP, and after paying stays right where they were. A redirect to a payment page is a different flow: the customer leaves for the payment service's address, pays and comes back. Both are secure and cost the same; the difference is what the customer sees and what you need to do on the site.
The form is embedded in the layout or opens as a modal. The browser address doesn't change, and the cart and checkout stay on screen.
The site sends the customer to the MulenPay payment page. The payment happens there, and afterwards the customer returns to the address you specified.
The choice isn't final: the payment is created the same way and can be shown either in the widget or by link. If the site runs on a builder with no code access, start with the link and add the widget when you can.
Benefits
A simple solution that works on any website
The widget embeds without complex technical setup. Suits online stores, landing pages and corporate websites.
Russian bank cards, SBP, SberPay, T-Pay and foreign cards are switched on and off in the shop settings — the customer picks the convenient one without leaving your page.
Rate from 2.9% per payment for Russian cards and SBP, free setup, no subscription fee.
Card details are entered in the secure MulenPay form, the service is certified to PCI DSS 4.0.1, and payments are confirmed with 3-D Secure.
Ready-made modules for WordPress, 1C-Bitrix, OpenCart, PrestaShop, Drupal, Joomla and InSales, plus guides for seven more platforms.
Check the whole path — from the button click to the order status change and the receipt — before customers see the widget.
How to embed
From pasting ready-made code to full API integration
The script is added to the page, the payment is created on your server via API, and the widget opens it for the customer. Works for any site where you can add your own code.
Ready-made modules exist for WordPress, 1C-Bitrix, OpenCart and other platforms: installed by the site administrator, no code to write.
If you need full control over the form and logic, the payment is created with a REST API request and the result is delivered to your endpoint.
Platforms
Seven platforms have a ready-made module: it adds MulenPay to the list of payment methods and the customer pays at checkout. Seven more — CRMs, site builders and learning platforms — have no module, and payments are connected by payment link or via API. Each platform's page says which path fits it.
If your platform isn't listed, the widget still works: all it needs is a way to add a script to the page and a server that creates the payment via API.
Embedding example
The payment is created on your server with an API request — so the amount and order contents can't be tampered with in the browser. The response contains a payment identifier. You pass it to the widget on the page, and it opens the checkout for the customer with the right amount.
The snippet on the right shows only the general shape: adding the script and the call with the identifier. The script address, parameter names and result handling are described in the documentation — copy from there, not from here.
Open the documentation<!-- add the widget script -->
<script src="…/widget.js"></script>
<!-- call with the identifier of a payment created via API -->
<script>
widget.open({ payment: 'payment identifier' })
</script>Schematic. The exact script address, parameters and events are in the documentation at docs.mulenpay.com.
What you can configure
Checkout shouldn't look like a foreign insert
Russian bank cards, SBP, SberPay, T-Pay and foreign cards are switched on and off in the shop settings. Keep only what your customers actually pay with.
The form's colours and fonts adapt to the page design so that checkout doesn't look like someone else's window and doesn't scare the customer off at the last step.
The form language is set for your site's audience: no separate widget per language version is needed.
Order items, VAT rates and the data for the 54-FZ fiscal receipt are passed with the payment — a cloud online cash register generates it.
The site receives the payment result at its endpoint and changes the order status automatically, with no manual reconciliation against the dashboard.
Set when the payment is created on the server, so the customer sees exactly the order and amount that are in the cart.
Security
The widget frees the site from the requirements on storing and transmitting card data
The card number, expiry and verification code are entered in the MulenPay form that opens on top of your page. This data never reaches your server, and you don't have to store it.
The service is certified to the current version of the card data security standard and reconfirms compliance every year. The certificate is on a separate page.
A card payment is confirmed by the customer's bank, so a payment with a stolen card won't go through without the cardholder's confirmation.
Test payment
One run before publishing saves a lot of back-and-forth with customers after
Open the page with the widget, place an order and go through checkout as a customer — the test payment procedure is described in the documentation.
The order status on the site changed, the payment is visible in the dashboard, the receipt went out, and a refund from the dashboard puts the order back in the right state.
Write to support: support@mulenpay.com or @mulen_support_bot on Telegram. Include the page address and the payment identifier — it makes the investigation faster.
Getting started
Onboarding takes one business day: registration, keys, widget installation. Style the form to match your site, manage payments, refunds and reporting in the dashboard.
Terms
The full rate table and fee calculator are on the pricing page
Russian bank cards — Visa, Mastercard, MIR — SBP, SberPay and T-Pay share one rate.
Cards of foreign banks have their own rate: the final one is fixed in the contract.
The per-operation limit is shared by all payment methods in the widget.
The widget and modules are free, onboarding takes one business day. The fee is charged only on completed payments.
FAQ
Read more
Installing the widget costs nothing; the fee is charged only on payments.
How it differs from direct bank acquiring and who it suits.
What 54-FZ requires and why you don't need to buy a device.
What to show the customer when a payment fails.
How to connect the payment system in the Store section and set up the webhook.
Connect the widget and start accepting payments right on the product page.
Telegram bot
@mulen_support_bot
Quick answers 24/7
Contacts and departments
All contact channels
Six departments, response times and company details
Fill out the form — a manager will get in touch, tailor the terms and help with the integration.
