One point of acceptance
Cards, SBP and Pay services all run through a single integration — there's no need to connect each method separately.
Payment acceptance technology
Widget, API, mobile SDKs and payment links: integrate once and accept cards, SBP and Pay services, with transaction statuses in your dashboard.
The basics
How the gateway connects your order system to payment methods
Cards, SBP and Pay services all run through a single integration — there's no need to connect each method separately.
The gateway returns the transaction result to your system, so the order updates without manual checks.
MulenPay provides the technology — checkout forms, API and dashboard; financial operations are carried out by licensed providers and partners.
Capabilities
Payment methods and operations available after a single integration
Visa, Mastercard, MIR and UnionPay: the gateway accepts cards issued in 50+ countries.
The customer pays by scanning a QR code or confirming in their banking app — no card details required.
Customers pay with SberPay, T-Pay, Yandex Pay, Mir Pay or MTS Pay in a single tap.
The gateway saves the payment method, so subscriptions renew without the customer doing anything.
Open the history and issue refunds from the dashboard or via API; timelines depend on the provider's terms.
A receipt is generated for every online payment: the gateway integrates with the Ukassa and Webkassa online cash registers.
MulenPay provides software and infrastructure solutions. The service does not offer financial, payment, banking or investment services in its own name: all financial operations are carried out by licensed providers and partners.
Who it's for
Any project where payment happens online and the order lives in your own system
Cart payments are tied to the order and the status reaches your CMS without manual checks.
Sale proceeds are split automatically between the platform and the seller.
Checkout runs inside the app through an SDK, with no detour to a browser.
Course access opens on payment status, with checkout via a link or a landing page.
Recurring charges renew the plan without customers re-entering card details.
A prepayment link confirms the booking and cuts the risk of no-shows.
Payment flow
Five steps from the Pay button to a record in your dashboard
Your system sends the gateway the amount, the order number and the payment parameters.
The form shows the available options: card, SBP, QR code or a Pay service.
The customer's bank reviews the payment and decides whether to approve the charge.
The gateway sends an event to your system and the order status updates automatically.
The payment is saved to the history with its amount, status and order details.
We break down the full payment flow — statuses, declines and refunds — in our internet acquiring guide; the link is at the bottom of the page.
Get started
Leave a request — we'll pick the integration format that fits your stack and get the technical side done within one business day.
Integration options
From a ready-made widget on the page to server-side calls from your CRM
The Widget.js script opens the checkout form right on the page, and its design adapts to your site.
The widget works on WordPress, Bitrix and other popular platforms.
REST methods create payments, return statuses and trigger refunds from your backend.
Libraries for iOS, Android and Flutter embed checkout inside your mobile app.
Generate a link and a QR code in the dashboard — no website and no developer required.
Your server receives a payment event, so there's no need to poll the gateway for updates.
Walk through the card and SBP payment flow on the demo page with no real charge.
Security
Card details never touch your infrastructure
Card data is processed inside a certified environment — you don't have to go through the audit yourself.
The customer's bank adds an extra confirmation step before the card is charged.
Suspicious transactions are screened automatically, which reduces the risk of fraudulent charges.
The customer enters their card number on the checkout form, so it never reaches your server.
Reliability
When payments go through inconsistently, the cause is usually the integration rather than the payment method
Rely on the server-side payment event, not on the customer landing back on your success page.
Don't fulfil an order until the payment is confirmed: check any disputed transaction in the dashboard.
If your server didn't accept the webhook, resend the payment event from the dashboard.
We cover decline symptoms and the diagnostic order in detail in our article on payment gateways and payment errors; the link is at the bottom of the page.
Q&A
A quick take on what businesses ask most often before connecting a gateway
Further reading
Decline symptoms, who is responsible for what, and the diagnostic order for support teams and developers.
What happens between the Pay button and the confirmed transaction, step by step.
When a business needs a terminal, when an online form works better, and how to combine both channels.
Leave a request — we'll pick the integration format that fits your stack and hand over your access keys.
Telegram bot
@Mulenpay_support_bot
Quick answers 24/7
Legal address
RBY Commerce Ltd.
8 Copthall, Roseau Valley, 00152, Commonwealth of Dominica
Fill out the form — a manager will get in touch, tailor the terms and help with the integration.