Skip to content

Payments for VPN bots

Connect payments on your VPN website to a Telegram bot. A customer pays for a subscription; your server confirms the payment and activates or renews access.

MulenpayExample integration

VPN subscription

User #1042

30 days

Secure connection

Awaiting payment

Ready to pay

Card or SBP
Access after payment
Pay for subscription

Payment on the service website

From payment to access, without manual matching

MulenPay handles the payment layer; your service manages subscriptions and VPN access.

  1. The customer selects a plan

    Your website creates an order with a user, subscription period and amount. The order ID links the payment to the right account.

  2. Pays for the subscription

    The MulenPay payment page shows the amount and available methods. The customer confirms the transaction.

  3. Your server receives the status

    A webhook reports the payment result. Your server matches the order and verifies the confirmed payment status through the API.

  4. The bot confirms access

    After successful payment, your service activates or renews the subscription. The bot sends the result and setup instructions.

First purchase, renewal and recurring payments

One payment integration for different stages of a VPN account.

A new customer

Link the first payment to an account. Once it is confirmed, your server activates VPN access and the bot helps the customer get started.

Access renewal

Create a new order for the chosen period and update the expiry date after payment. Your service controls the renewal logic.

Recurring payments

If recurring payments are approved for your project, connect charges to subscription renewal. Saving a payment method requires customer consent.

Keep payments connected to access

Three rules for integrating a website, VPN panel and bot.

Link each order to an account

Store user, order and payment identifiers on your server. The bot needs to know which subscription to update.

Activate access after confirmation

A redirect to a success page does not confirm payment. Use a server notification and verify the payment status.

Handle repeated notifications

Process each paid order once. A repeated webhook must not activate access again or extend the subscription twice.

Agree on terms for your VPN service

Share your project website, plans and bot workflow. A manager will confirm payment methods, fees and the integration process.

Questions about integration

MulenPay provides a payment page, APIs, webhooks and a dashboard. Your developer maintains the bot, VPN panel and access logic. Compatibility with a specific panel needs to be checked when designing the integration.

Discuss payments for your VPN bot

Tell us about your project so we can agree on a payment flow and onboarding terms.

Let’s talk about your project

Setup, pricing or support — choose the way you prefer to get in touch.

Write to the team

Your name and one contact are enough. Add details if you wish.

How should we contact you?

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

TelegramTelegram