Robokassa

Issue Robokassa payment links right inside the conversation

Connect Robokassa to the AI agent: payment links, invoice statuses and 54-FZ receipts. The agent issues an invoice in chat and chases the unpaid ones.

How the agent works with Robokassa

The agent works with Robokassa through signed requests to auth.robokassa.ru: it assembles a payment link with the amount, the order description and a 54-FZ fiscal receipt, reads the status of an issued invoice by its number and shows the currencies and payment methods available to your particular shop. The check request on connection is the list of shop currencies: it immediately shows that the signature matches and the shop responds.

There is no token in Robokassa — access rests on the shop passwords, and they are not interchangeable: password #1 signs the payment itself, password #2 signs notifications and the status check. So the agent needs both, otherwise half of the work falls away. The signature itself is assembled from the shop identifier, the amount, the invoice number and the password and hashed with MD5, so the amount in the signature and the amount in the link have to match to the kopeck — otherwise the payment is rejected at the entrance, before the checkout page.

The agent does not handle money: it issues an invoice and reads its status — initiated, on hold, paid or refunded — while crediting and withdrawal stay on the Robokassa side and under your contract with them. On a schedule it walks through the invoices it issued itself and reminds you about the unpaid ones. There is no bank account statement here and there cannot be: Robokassa is about accepting payments from customers, a bank is connected as a separate connector.

Robokassa returns its errors as numeric codes, and the agent decodes them rather than showing a bare «the request failed»: the code tells a signature mismatch apart from a shop that is not live yet and from an invoice number that does not exist. It holds the request rate itself — up to five per second with a small allowance for a burst — so a series of status checks does not run into a refusal. If there is no data on an invoice or the shop does not return it, the agent says so directly instead of showing an empty table.

Integration scenarios

A payment link right in the chat

The agent builds a payment link with the amount, the description and a 54-FZ fiscal receipt — ready to send to the customer straight away.

Status of an issued invoice

The agent tells you by invoice number where the payment stands: initiated, on hold, paid or refunded — without opening the merchant account.

Reminders on unpaid invoices

On a schedule the agent walks through the invoices it issued and reminds you about the ones that are still unpaid.

Currencies and payment methods

The agent shows the currencies and payment methods available to your shop, so a link is issued in whatever is convenient for the customer.

How much came in today

The agent walks the invoices issued over the day, counts the paid ones and shows the total collected, naming separately what went to a refund or stayed on hold.

Why a payment failed

The agent decodes the numeric error code — a signature mismatch, a shop not through moderation yet, an invoice number that does not exist — and says what to fix.

Robokassa examples

Robokassa
Frozen chats — click a question
Выстави клиенту счёт на 48 700

Ссылка на оплату готова — 48 700 ₽, чек по 54-ФЗ приложен.

  • Назначение: «Поставка партии №118»
  • Оплата картой, СБП или кошельком — что удобнее клиенту

Отправить в переписку?

How to connect

Before you connect

  • A Robokassa account with owner rights on the shop
  • The shop past moderation: before that only test mode works
  • A website or page where the payments are accepted
  1. 1

    Create a shop in your Robokassa account

    Register at partner.robokassa.ru and create a shop: the identifier and the passwords belong to the shop, not to the account.

  2. 2

    Copy MerchantLogin under Technical settings

    The shop identifier (MerchantLogin) sits in the shop card under «Мои магазины» → «Технические настройки». It is the shop login, not your account e-mail.

  3. 3

    Make sure the hash algorithm is MD5

    The signature hash method sits in the same card. MD5 is the default and the only one that matches — switch anything else back.

FAQ

With three values from My shops, Technical settings: the shop identifier (this is the shop login, not the sign-in e-mail), password #1 and password #2. Check that the hash algorithm is MD5, otherwise signatures will not match, and test passwords will return error 29.

It builds payment links with a 54-FZ fiscal receipt, checks the status of an invoice by its number and shows the currencies and payment methods available to the shop.

No. Robokassa is about accepting payments from customers: the agent sees issued invoices and their statuses, not a bank account statement. For account operations a bank is connected as a separate connector.

The agent does not handle money: it issues an invoice and reads its status, while crediting and withdrawal stay on the Robokassa side and under your contract with them.

Related integrations

Category
Banks
Connection
API key
Documentation
Robokassa

Connect Robokassa

Connecting takes a couple of minutes, and your data stays in your own systems.

Connect