Integrating Robokassa: Versatile Payment Solutions
Integrate Robokassa with your iSales AI Chatbot to offer a comprehensive suite of payment methods popular in Russia and neighboring countries. This guide will walk you through configuring the Robokassa integration, enabling your bot to securely process payments for your products and services.
Robokassa Integration Status:
- Robokassa Status: (e.g., ⚫ Disabled) – This indicator shows whether Robokassa payment processing is currently active or inactive for your AI chatbot.
Core Robokassa Connection Settings:
To connect your iSales AI Chatbot with your Robokassa account, you’ll need the following credentials from your Robokassa merchant dashboard:
- Store ID: (e.g., Not set)
- What it is: Your unique shop identifier provided by Robokassa when you register your store on their platform.
- How to find it: Log in to your Robokassa merchant account. Your Store ID (often called “Идентификатор магазина”) will be visible in your shop settings or technical integration details.
- Password 1: (e.g., Not set)
- What it is: The first secret password used for authenticating and securing payment requests and notifications between your bot and Robokassa. Keep this password confidential.
- How to find/set it: In your Robokassa merchant dashboard, typically under technical settings or API integration, you will set up Password #1.
- Password 2: (e.g., Not set)
- What it is: The second secret password used for an additional layer of security, often for validating payment confirmations. Keep this password confidential.
- How to find/set it: Similar to Password 1, this is configured in your Robokassa merchant dashboard’s technical settings.
❗ Important Note on Password Creation:
When creating your passwords (Password 1 and Password 2) in your Robokassa merchant account, be sure to specify the MD5 encryption algorithm if prompted or if there’s an option for hashing method. This is often a requirement for correct integration with many platforms.
Looking for setup help? The interface mentions: “Instructions for creating a store in Robokassa.” This suggests there’s a more detailed guide or link available (likely by clicking that text) to help you through the Robokassa store setup and key generation process.
Tax and Product Configuration:
Ensure your payment processing aligns with your business’s fiscal requirements:
- VAT (Value Added Tax): (e.g.,
without_vat) – Select the VAT rate applicable to your sales.Without VAT(Default/Selected in screenshot)VAT 0%VAT 10%VAT 20%
- Tax System: (e.g.,
common_system) – Choose the tax system under which your business operates.Common VAT/common_system(Default/Selected in screenshot)Income VATIncome-Expense VATPatent VAT
- Product Type: (e.g.,
product) – Define the general category of items you are selling.Product(Default/Selected in screenshot)Service
Managing Your Robokassa Integration:
The interface provides several buttons for easy configuration:
- 🆔 Update Store ID (Button): Click to enter or modify your Robokassa Store ID.
- 🔑 Update Password 1 (Button): Click to enter or update your Robokassa Password 1.
- 🔑 Update Password 2 (Button): Click to enter or update your Robokassa Password 2.
- ——| Robokassa Processing |——
- 🟢 Enable / Disable (Toggle Buttons): Activates or deactivates Robokassa as a payment gateway.
- ——| VAT |——
- Buttons for
Without VAT,VAT 0%,VAT 10%,VAT 20%to select the appropriate VAT rate.
- Buttons for
- ——| Tax System |——
- Buttons for
Common VAT,Income VAT,Income-Expense VAT,Patent VATto select your applicable tax system.
- Buttons for
- ——| Product Type |——
- Buttons for
ProductandServiceto define the default type of item being sold.
- Buttons for
- ↩️ Back (Button): Returns to the main “Payment Processing for AI Bot” menu.
By accurately configuring your Robokassa Store ID, passwords, and tax details, you can enable your iSales AI Chatbot to securely process payments through Robokassa, offering your customers a broad range of convenient payment options. Always refer to the official Robokassa documentation for the latest setup procedures and security best practices.