The bot builds the order
The buyer picks a product or plan in a dialogue with the bot. The bot knows the amount and the purpose and asks the API for an invoice — or the seller creates a link in the dashboard by hand.
Payments for bots
Accepting payments in Telegram bots
The bot takes the order, the buyer pays by a link in the same chat, and the bot learns the result from a webhook and delivers the goods. Russian bank cards, SBP, SberPay and T-Pay — from 2.9% per payment.
Fees from 2.9% PCI DSS 4.0.1
How it works
How a payment goes through a bot
Four steps, of which the buyer sees only two: the link and the payment page
A link arrives in the chat
The bot sends the buyer a payment link as a message. No need to visit a website or look up bank details: checkout opens straight from the chat.
The buyer pays
On the payment page they choose the method: card, SBP, SberPay or T-Pay. The amount and the purpose are already filled in; all that is left is to confirm.
The bot learns the result
A webhook tells the bot's server that the payment went through. The bot marks the order as paid and delivers the goods, access or confirmation without the seller stepping in.
Payment methods
How buyers pay inside a bot
Every method sits on one payment page; nothing has to be chosen in advance
Russian bank cards
Visa, Mastercard and Mir. Transactions are confirmed through 3-D Secure, and card details never reach the seller or the bot.
SBP
The buyer confirms the payment in their own banking app. Convenient on a phone — and a bot is almost always opened on one.
SberPay and T-Pay
One-tap payment from a banking app with no card details to type. The rate matches Russian bank cards.
Foreign cards
Cards issued outside Russia are accepted at a separate rate — from 8.9%. No separate agreement is needed for them.
Two ways to connect
No code, or through the API
The choice depends on whether the bot takes orders itself or the seller handles them by hand
Payment links from the dashboard
Fits when orders are few and the seller talks to the buyer directly. The link is created in the dashboard: amount, purpose, expiry. It goes into the chat, the buyer pays, and the seller sees the status in the dashboard. No developer needed.
REST API with webhooks
Fits a bot that takes orders on its own. The bot's server creates a payment through the API, gets a link for the buyer and a webhook with the result, checks statuses and issues refunds. Documentation is at docs.mulenpay.com.
What it does
Beyond the payment itself
54-FZ receipts
A cloud online cash register issues a fiscal receipt automatically for every payment. There is nothing extra to connect to the bot.
Refunds
Full or partial refunds from the dashboard or through the API. The bot can issue a refund itself, for example when an order is cancelled.
Analytics in the dashboard
Every bot payment in the dashboard: statuses, amounts, payment methods, exports. Reconciling orders needs no separate spreadsheet.
Payment protection
The infrastructure is certified to PCI DSS 4.0.1, and card transactions are confirmed through 3-D Secure. The bot never stores or sees card data.
Who it is for
Which bots take payments
The scenario is always the same: the bot knows what is being paid for and must learn that the payment went through
Telegram shops
Catalogue, cart and checkout inside the bot. Payment by link, order status by webhook.
Content subscriptions
Private channels and chats with paid access. After payment the bot sends an invite; when the term ends, it reminds about renewal.
Courses and training
Selling lessons, cohorts and materials through a bot. Access opens as soon as the payment is confirmed.
Services and bookings
Consultations, reservations, appointments. The bot invoices the agreed amount and confirms the booking once it is paid.
Donations and fundraising
Support for creators and projects. The payment link lives in a bot message or a channel description, and a receipt is issued automatically for every payment.
Terms
What it costs and what the limits are
The full rate table and the fee calculator are on the pricing page
From 2.9%
Russian bank cards, SBP, SberPay and T-Pay share one rate. Foreign cards — from 8.9%. The final rate depends on turnover and is fixed in the agreement.
From 10 ₽ to 300,000 ₽
The per-transaction limits are the same as for every other payment method. They cover micropayments and expensive courses alike.
Free to connect
No setup fee, no integration fee, no subscription. The commission is charged only on a completed payment.
Keep in mind
MulenPay provides the payment, not the bot
The bot itself, its scenarios and its delivery logic are written by the seller's developer or by the service the bot is built on. MulenPay provides the software and infrastructure for accepting payments: the payment page, links, API, webhooks, receipts and the dashboard. Payments are processed by licensed banks and partners. If there is no developer, start with payment links from the dashboard — they need no code — and add the API integration once the bot can take orders on its own.
Questions and answers
Frequently asked questions
Not necessarily. A payment link can be created in the dashboard and sent to the buyer in the chat by hand — no code is needed for that. A developer is needed when the bot has to create payments itself and learn about them itself: then the bot's server is connected to the REST API and webhooks following the documentation at docs.mulenpay.com.
Through a webhook: once the payment completes, a notification with the result and the payment identifier arrives at the bot's server. The bot matches it with the order and delivers the goods. The payment status can also be requested through the API, and it is always visible in the dashboard.
From 2.9% per payment for Russian bank cards, SBP, SberPay and T-Pay, and from 8.9% for foreign cards. Setup, integration and API use are free, and there is no subscription. The final rate depends on turnover and line of business and is fixed in the agreement.
A cloud online cash register issues a 54-FZ receipt automatically for every payment. Nothing extra has to be connected to the bot: the receipt contents — line items, amounts and VAT rates — are passed along with the payment.
Yes, in full or in part. A refund is issued in the dashboard or through the API — the bot can do it itself, for example when an order is cancelled. A card refund goes through the card scheme; an SBP refund is a transfer back to the buyer's account.
Setup takes one day after the application and documents are submitted. Payment links from the dashboard are available right away; the API integration is done by the seller's developer at their own pace. Support helps with setup questions: support@mulenpay.com and the Telegram bot @mulen_support_bot.
Read more
Related pages
Pricing and fee calculator
Russian bank cards, SBP and Pay services share one rate — from 2.9%.
Payment links
How to create a link in the dashboard, set the amount and expiry and send it to a chat.
Payment API
Creating a payment, statuses, webhooks and refunds — for a bot that takes orders itself.
Payments in social media and messengers
Selling in posts and messages without a website: the same toolkit outside the bot.
Fiscal receipts and 54-FZ
When a receipt is mandatory and how a cloud cash register issues it.
Is paying by link safe
What protects the buyer on the payment page and how to tell a genuine link from a fake one.
Ready to take payments in your bot?
Leave a request — a manager will pick a plan and suggest which way to connect first.
Telegram bot
@mulen_support_bot
Quick answers 24/7
Contacts and departments
All contact channels
Six departments, response times and company details
Leave a request
Fill out the form — a manager will get in touch, tailor the terms and help with the integration.
