Revolut payment setup for your subscription bot on Telegram & Discord

If you run a subscription bot on Telegram or Discord, Revolut gives your members a secure checkout experience while you receive funds directly to your Revolut Business account.

Revolut is a strong fit when your audience already uses Revolut and you want to reduce checkout friction with a familiar provider.

As a general guideline as of January 2026, Revolut personal accounts are available in 40+ countries (primarily the EEA and UK, plus the US, Australia, Brazil, Japan, New Zealand, Singapore, Switzerland, and select territories). Revolut Business availability is more restrictive and commonly depends on where your company is registered (often the UK/EEA, and sometimes the US) and where the applicant resides. Availability can change with local regulations, so always confirm eligibility directly with Revolut before you build pricing around it.

This guide shows you how to connect Revolut in BotSubscription so your bot can offer Revolut as a payment provider during checkout.

Why use Revolut with your Discord payment bot?

Direct payouts: Funds go directly to your Revolut Business account (BotSubscription does not hold your money).
Works across platforms: Use one setup for members subscribing via Telegram chats and Discord servers.
Great regional option: Useful when your audience prefers Revolut or when other processors are limited in your region.

Prerequisites for Revolut setup

Before you connect Revolut, make sure you have:

A Revolut Business account. Use the Revolut Business signup page if you don’t already have one.
Your Revolut API keys (Public Key and Secret Key).
Admin access to your bot’s settings (you’ll use the /settings command).

Connect Revolut to your Telegram & Discord subscription bot

Step 1: Open Merchant Accounts in Settings

In Telegram or Discord, open your bot’s Settings, then navigate to Merchant Accounts.

BotSubscription Merchant Accounts screen showing the Install Merchant Account button — Open Merchant Accounts to add Revolut as a payment provider

Step 2: Install a merchant account

Select Install Merchant Account to add a new provider.

Step 3: Select Revolut

Choose Revolut from the available payment providers list.

Payment provider selection screen used to choose Revolut as a payment method — Select Revolut from the payment provider list

Step 4: Review the required Revolut credentials

BotSubscription will show which credentials you need to provide:

Revolut Public Key
Revolut Secret Key

Revolut configuration preview showing required Public Key and Secret Key fields — Review the required Revolut credentials before setup

For payment providers that support test mode, BotSubscription lets you install merchant accounts separately for Sandbox and Production, so you can test without charging real money. See Sandbox vs Production environments.

Step 5: Paste your Revolut Public Key and Secret Key

Open your Revolut Business dashboard and locate your Merchant API keys.

Merchant API settings: open Revolut Merchant API settings

Copy the Public Key and Secret Key, then paste them into the BotSubscription configuration form and click Submit.

Revolut credentials form in BotSubscription showing Public Key and Secret Key fields — Paste your Revolut Public Key and Secret Key

Step 6: Confirm Revolut is connected

After BotSubscription validates your keys, you’ll see a success confirmation.

At this point, members will see Revolut as an option when they subscribe and pay.

Common issues

Revolut is not showing up for members

Make sure Revolut is installed and active in Merchant Accounts.
Confirm your bot is in the right environment (Sandbox vs Production), because the bot only shows payment providers for the active environment. See how environments affect payment providers.

“Invalid key” or “Authentication failed”

Double-check that you copied the Public Key and Secret Key (no extra spaces).
Confirm you didn’t swap them: paste the Public Key into the Public Key field, and the Secret Key into the Secret Key field.
Make sure you used the keys that match your environment (Sandbox keys for Sandbox, Production keys for Production).

Last updated: January 25, 2026

API Endpoint