Bot payment systems#

A chatbot's payment blocks issue an invoice through the payment system connected to this bot. Such a connection is called an integration and lives in the bot settings: "Settings" → the "Integrations" tab.

How to open an integration window, save and delete an integration is on the Integrations page. This page covers what is specific to payment systems: which fields to fill in and what to do with the Webhook URL.

Note

Connections from the "Accepting payments" tab in the project settings do not work for a bot's payment blocks: they are for shops and online schools. They are described on the Project payment systems page.

General rules#

• Each bot has its own integrations. They are not carried over to a copy of the bot — connect the system in the copy again.
• One system — one connection. You can connect several different payment systems to a bot, but each one only once.
• The currency is set in the integration, not in the payment block. Systems that work in a single currency have no currency field.
• The Webhook URL. If a "Webhook" tab appears in the integration window after saving, copy the URL from it into the payment system's dashboard. The system uses this URL to tell the bot about a payment — without it the block's "Successful payment" output will not fire.
• Team members see the keys. The integration window is opened by the bot owner and by a team member with the "Bot settings" permission — give this permission only to people you trust with access to your cash desk.
• A Pro subscription is required. The "Integrations" tab works only with it.

What to enter for each system#

YooKassa#

On the "Main" tab:

• "Shop ID" and "Secret key" — from the YooKassa dashboard;
• "Currency code" — a three-letter code, RUB by default;
• "Tax system" and "VAT rate" — they go into the receipt.

After saving, two more tabs appear. The "Webhook" tab has the URL to set as the notification URL in the YooKassa settings. The "Notifications" tab is described below.

Specifics:

• A receipt is sent with every payment, so the bot needs the contact's phone number or email.
• Having received a notification, the platform checks the payment in YooKassa itself, using this integration's keys. The payment counts only if YooKassa confirms the status, amount and currency.
• If YooKassa reports a cancellation, the payment in the bot gets the "Canceled" status.

YooMoney#

The only field is "Wallet number". After saving, a URL appears on the "Webhook" tab: set it in the HTTP notification settings of your YooMoney wallet.

Specifics:

• The invoice is issued in roubles.
• The payment counts only if at least the invoice amount was charged to the payer. A transfer protected by a protection code and a transfer that has not been accepted yet do not count.
• Receipt data is not sent.

Robokassa#

On the "Main" tab:

• "Shop integration country" — "Russia" or "Kazakhstan". It determines the invoice currency: roubles or tenge;
• "Shop ID", "Password #1" and "Password #2" — from the shop's technical settings in Robokassa;
• "Tax system" and "VAT rate";
• the "Send receipts" switch.

After saving, a URL appears on the "Webhook" tab: add it to the Result Url field in the shop's technical settings in the Robokassa dashboard.

Specifics:

• The notification is checked with "Password #2". If it is entered incorrectly, the payment will not count.
• The bot does not count Robokassa test payments.

Cloudpayments#

The window has three tabs.

• "Main": "Public ID", "API password", "Currency" and the "Two-stage payment" switch.
• "Webhook": the URL appears after saving. In the site settings in the Cloudpayments dashboard, turn on the notification about an accepted payment — Pay and Confirm — and set this URL for them.
• "Receipt": the "Send receipt" switch. When it is on, "Tax system" and "VAT rate" appear.

Specifics:

• The payment counts only if the amount in the notification matches the invoice amount.
• With two-stage payment, the money is first blocked on the card, and the platform confirms the charge itself.
• A payment made in Cloudpayments test mode is marked "[TEST]" in the bot's list of payments.

T-Bank#

The integration is called "Internet acquiring from T-Bank". Fields:

• "Terminal" and "Password" — from the internet acquiring dashboard;
• "Tax system" and "VAT rate";
• "FFD version" — the FFD version of your online cash register: 1.05 or 1.2;
• "Send receipt". Be sure to enable sending if you have an online cash register connected.

There is no "Webhook" tab: T-Bank receives the notification URL with every payment, you don't need to set it in the bank's dashboard.

Specifics:

• The invoice is issued in roubles.
• The receipt needs the contact's phone number or email.
• A decline or an expired payment term moves the payment to the "Canceled" status, a refund — to the "Refunded" status.

Prodamus#

Fields: "Shop Page" — the URL of your Prodamus payment page, "Secret key" and the "Demo mode" switch for trial payments.

After saving, the "Webhook" tab opens: add the URL from it in your Prodamus payment page settings.

bePaid#

The "Main" tab has "Shop ID", "Secret key" and "Currency". There is no "Webhook" tab: bePaid receives the notification URL with every payment. The "Notifications" tab is described below.

Specifics:

• If the bank declined a payment attempt, the buyer can try again on the same page. The payment gets the "Canceled" status only when the invoice has expired.
• Receipt data is not sent.

LiqPay#

Fields: "Public key", "Private key" and "Currency" — US dollar, euro, Russian rouble, hryvnia, Belarusian rouble or tenge. LiqPay receives the notification URL with every payment, there is no "Webhook" tab. Receipt data is not sent.

Crypto Pay#

The only field is "API Token". After saving, the "Webhook" tab opens: add the URL from it in your @CryptoBot.

JustClick#

Payment through JustClick works on the JustClick integration — it is described on the Integrations page.

A copy of notifications on your own server#

The YooKassa, Robokassa and bePaid integrations have a "Notifications" tab with the "Notification URL" field. Enter your server's address there — and the platform will send it information about the bot's payments. You need this if your own system also keeps track of payments.

• The server must respond with code 200.
• If the response is different, the platform retries for 24 hours, gradually increasing the pause between attempts.

The field is optional: the bot works without it.

Next#

• Settings of the payment blocks themselves are in the Accepting payments section.
• What data goes into the receipt is on the Receipts page.
• Where to see issued and paid invoices is on the Bot payments and orders page.