Skip to content

Payment acceptance technology

Payment gateway for websites and online business

Widget, API, mobile SDKs and payment links: integrate once and accept cards, SBP and Pay services, with transaction statuses in your dashboard.

The basics

What a payment gateway is

How the gateway connects your order system to payment methods

One point of acceptance

Cards, SBP and Pay services all run through a single integration — there's no need to connect each method separately.

Status delivery

The gateway returns the transaction result to your system, so the order updates without manual checks.

Who does what

MulenPay provides the technology — checkout forms, API and dashboard; financial operations are carried out by licensed providers and partners.

Capabilities

What the MulenPay gateway supports

Payment methods and operations available after a single integration

Bank cards

Visa, Mastercard, MIR and UnionPay: the gateway accepts cards issued in 50+ countries.

SBP and QR code

The customer pays by scanning a QR code or confirming in their banking app — no card details required.

Pay services

Customers pay with SberPay, T-Pay, Yandex Pay, Mir Pay or MTS Pay in a single tap.

Recurring charges

The gateway saves the payment method, so subscriptions renew without the customer doing anything.

Refunds and transaction history

Open the history and issue refunds from the dashboard or via API; timelines depend on the provider's terms.

Fiscal receipts

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.

Payment flow

How a payment gateway works

Five steps from the Pay button to a record in your dashboard

1. Your site creates the payment

Your system sends the gateway the amount, the order number and the payment parameters.

2. The customer picks a method

The form shows the available options: card, SBP, QR code or a Pay service.

3. The bank authorises the transaction

The customer's bank reviews the payment and decides whether to approve the charge.

4. The status reaches your server

The gateway sends an event to your system and the order status updates automatically.

5. The transaction lands in your dashboard

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

One gateway for every sales channel

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

Integration: widget, API and mobile SDKs

From a ready-made widget on the page to server-side calls from your CRM

Payment widget

The Widget.js script opens the checkout form right on the page, and its design adapts to your site.

CMS compatibility

The widget works on WordPress, Bitrix and other popular platforms.

Payment API

REST methods create payments, return statuses and trigger refunds from your backend.

Mobile SDKs

Libraries for iOS, Android and Flutter embed checkout inside your mobile app.

Payment link and QR

Generate a link and a QR code in the dashboard — no website and no developer required.

Webhooks

Your server receives a payment event, so there's no need to poll the gateway for updates.

Demo payment

Walk through the card and SBP payment flow on the demo page with no real charge.

Security

Payment security

Card details never touch your infrastructure

PCI DSS Level 1 v4.0

Card data is processed inside a certified environment — you don't have to go through the audit yourself.

3-D Secure 2.0

The customer's bank adds an extra confirmation step before the card is charged.

Anti-fraud

Suspicious transactions are screened automatically, which reduces the risk of fraudulent charges.

Card data storage

The customer enters their card number on the checkout form, so it never reaches your server.

Reliability

Payment errors and reliability

When payments go through inconsistently, the cause is usually the integration rather than the payment method

The source of truth for status

Rely on the server-side payment event, not on the customer landing back on your success page.

Orders with an unknown status

Don't fulfil an order until the payment is confirmed: check any disputed transaction in the dashboard.

Resending a notification

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

Frequently asked questions

A quick take on what businesses ask most often before connecting a gateway

It's the technical link between your website, the checkout form and the payment methods. Your site sends the gateway the amount and the order number, the customer chooses how to pay, and the result of the transaction comes back to your server. Businesses use a gateway to accept cards, SBP and Pay services through a single integration and to see every transaction in one dashboard.

Ready to connect a payment gateway?

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

Leave a request

Fill out the form — a manager will get in touch, tailor the terms and help with the integration.

By clicking the button, you agree to the processing of personal data.

TelegramTelegram