# Banks and payment acceptance Banks and payment services connect under **Integrations**. The general rules (kinds of connection, card statuses, Read only, disconnecting) are on the [Connecting services](/help/integrations) page. How the agent asks before changes is described in [Action confirmation](/help/trust). The agent works with the rights of the user or key you connected. A bank key or token opens your accounts: keep it like a password. Signing and sending payments stay with you in the online bank. ## T-Bank Business Accounts, statements, payments, payroll and cards. More on the [integration page](/integrations/tinkoff). ### What the agent can do Reads accounts, balances and statements, breaks down transactions by counterparty and category. It prepares a payment order if the user's rights allow it; signing and sending stay in the bank. ### Before you start The phone number that holds access to the company in T-Business. No tokens to copy. ### Steps ### Click Connect via T-Bank Under Integrations open the **T-Bank Business** card and click **Connect via T-Bank**. ### Sign in to T-Business Sign in at business.tbank.ru with the number that holds access to the company. If several companies are registered to the number, check the INN of the one you need. ### Confirm access Once confirmed, the connection is labelled with the company name. ### Permissions to grant - **Access level.** In **«Настройки профиля и доступы» → «Компания» → «Пользователи»** (Profile settings and access, Company, Users) there are three levels: «Директор», «Подписант», «Менеджер» (Director, Signatory, Manager). Only the Director changes levels, so connect as the Director. - **Accounts.** Access is set per account: on the dashboard pick the account → **«Настройки» → «Доступ к счету»** (Settings, Account access), tick the user → **«Сохранить»**. An unticked account stays invisible to the agent. ### Limitations - Transactions are available from June 2023 onwards; download earlier statements from the online bank by hand. - Several companies on one number connect separately. Name the one you need in the request: "for the LLC accounts, not the sole proprietor". ### How to revoke access Click **Disconnect** in the card here. In T-Business untick the user in «Доступ к счету» or change their level. ### Troubleshooting - **The agent does not see every account**: the account is not ticked in «Доступ к счету». - **Reconnection required status**: click **Reconnect** and sign in again. ## SberBusiness Accounts, statements, payments, counterparties, corporate cards and payroll through Sber API. More on the [integration page](/integrations/sberbank). ### What the agent can do Reads accounts and statements, the counterparty directory, cards and payroll data within the rights you chose when connecting Sber API. ### Before you start - SberBusiness access for the company head or a user with a power of attorney: they sign the Sber API application. - A way to issue a TLS certificate and save it with its key in PEM format. - A registered redirect address (Redirect URI) from the service parameters. ### Steps Sber takes longer than other banks: the bank grants access only with its certificate and a single-use code. ### Connect Sber API in SberBusiness **«Все продукты и услуги» → «Сбербанк API» → «Sber API» → «Подключить»** (All products and services, Sberbank API, Sber API, Connect). Choose the rights. The application is signed by the company head or a user with a power of attorney. ### Activate the service and copy its parameters After activation open **«Параметры промышленного сервиса»** (production service parameters): Client ID, Client Secret and Redirect URI are there. Keep the scope too, the authorization needs it. ### Issue the certificate In **«Сертификаты шифрования»** (encryption certificates) issue a TLS certificate for your Client ID. If the bank gave you a .p12 container, export the certificate and the private key from it into separate PEM files beforehand. The key must be unencrypted. ### Fill in the form In the **Sberbank** card fill in **Client ID**, **Client Secret**, upload the **Client certificate** and the **Certificate private key**, and enter the **Redirect URI** (the same registered address). Leave **Authorization code** empty for now. ### Go through SberBusiness authorization Open `https://sbi.sberbank.ru:9443/ic/sso/api/v2/oauth/authorize` in the browser with the parameters `response_type=code`, `client_id`, `redirect_uri` (the same address as in the form), `scope` (including `openid`) and random `state` and `nonce`, and sign in. The bank sends you back to the Redirect URI with a code parameter in the address. ### Paste the code and connect at once Copy the code value into **Authorization code** and click **Connect** right away: the code is single-use and expires quickly. ### Permissions to grant The ones you ticked when connecting Sber API in the first step. The agent sees only what they allow: for statements, rights to accounts and statements are required. ### Limitations - The certificate must belong to the same Client ID as in the form, and the private key must match the certificate. - An authorization code works once. If connecting failed, get a new code and paste it. ### How to revoke access Click **Disconnect** in the card here. The rights of the Sber API service itself live in SberBusiness, in the «Сбербанк API» section. ### Troubleshooting - **The connection rejected the code**: the code expired or was already used. Authorize again and click Connect right after pasting. - **Certificate error**: the certificate was issued for another Client ID, or the key is encrypted or does not match the certificate. Export the pair from .p12 again. ## Tochka Bank Accounts, statements, payments and SBP. More on the [integration page](/integrations/tochka). ### What the agent can do Reads accounts and statements and prepares payments within the key's permissions. ### Before you start An online bank user with the right to manage integrations. ### Steps ### Open Integrations and API Tochka online bank → **«Сервисы» → «Все сервисы» → «Интеграции и API»** (Services, All services, Integrations and API). ### Create a JWT key Click **«Создать JWT-ключ»** (Create JWT key), set a name and the access period, then continue. ### Grant permissions and confirm by SMS All permissions are ticked by default. For several companies, permissions are set separately. ### Copy the key and client_id The key appears in **«JWT-ключи»** (JWT keys). Paste it into **JWT Token** and the client_id next to it into **Client ID**: it is needed for webhooks. ### Permissions to grant Permissions for accounts and statements are required: without them requests return "Forbidden by consent". ### Limitations - A JWT key has no refresh: when its period ends, issue a new key by hand and paste it again. - Reissuing the key changes client_id: update the Client ID field too. ### How to revoke access Delete the key in «JWT-ключи»: access closes at once. Here, click **Disconnect**. ### Troubleshooting - **"Forbidden by consent"**: the key has no permission for this account or statement. Issue a key with the permissions you need. - **Credentials not accepted status**: the key expired or was deleted. Issue a new one and click **Re-enter credentials**. ## Modulbank Accounts, balance, transaction history and payment orders. More on the [integration page](/integrations/modulbank). ### What the agent can do Reads companies, accounts and transaction history. ### Before you start The user account that sees the companies and accounts you need: the token sees only those. ### Steps ### Open the token screen Menu **«+» → «Интеграция с банком»** (Bank integration), or **«Настройки» → «Услуги» → «API Банка» → «Генерация токена авторизации»** (Settings, Services, Bank API, Generate an authorization token). ### Tick the permissions Tick **account-info** (companies and accounts) and **operation-history** (transaction history). ### Paste the token Copy the token into **API Token**. ### Permissions to grant account-info and operation-history. The token equals access to the account, keep it like a password. ### Limitations The token works for a limited period and the bank cancels it automatically when that period ends. ### How to revoke access Click **Disconnect** here. The bank lets you revoke the token before it expires. ### Troubleshooting - **A company is missing**: the token was issued under another user account. Issue it under the one that holds the company. ## Alfa-Bank Business Accounts, statements, transactions and payments through Alfa API. More on the [integration page](/integrations/alfabank). ### What the agent can do Reads accounts, statements and transactions. ### Before you start A settlement account with cash management services and Alfa-Business Online connected. ### Steps ### Request Alfa API access Write to alfa_api@alfabank.ru with the company details. The contract arrives for signing in Alfa-Business Online, and after signing the bank issues a Client ID. ### Create a certificate request Create a CSR with openssl req, filling in the company data and INN. The bank returns a PEM certificate; the private key stays with you only. ### Pass the sandbox Test the methods in the sandbox and email the bank with the subject «Завершено тестирование» (testing completed): the bank opens production access. ### Fill in the form In the **Alfa-Bank Business** card fill in **API Key**, **Client certificate** and **Certificate private key**. ### How to revoke access Click **Disconnect** here. The certificate's private key is kept only by you: delete its copies when access is no longer needed. ### Troubleshooting - **Connecting fails after the key is issued**: sandbox testing is not finished, so production access is not open yet. ## YooKassa Payment acceptance: payments, refunds, receipts, invoices, recurring payments. More on the [integration page](/integrations/yookassa). ### What the agent can do Views payments and their statuses, issues refunds and invoices within the shop's key. ### Before you start The shop owner role or «Разработчик» (Developer) in the YooKassa account: keys are hidden from other roles. ### Steps ### Copy the shopId Pick the shop at the top of the account and open **«Настройки → Магазин»** (Settings, Shop): the ID is labelled shopId. Paste it into **Shop ID**. ### Issue a secret key **«Интеграция → Ключи API»** (Integration, API keys) → **«Выпустить ключ»** (Issue key), confirm with the SMS password. ### Copy the key at once The key is shown once. Paste it into **Secret Key**. ### Limitations Each shop, including the test one, has its own shopId: the key and the shopId must come from the same shop. ### How to revoke access Reissue or delete the key in «Интеграция → Ключи API». Here, click **Disconnect**. ### Troubleshooting - **Credentials not accepted status**: the key was reissued. Paste the new one via **Re-enter credentials**. ## Robokassa Payment acceptance: links and invoices, statuses, holds, recurring charges, refunds, receipts. More on the [integration page](/integrations/robokassa). ### What the agent can do Creates payment links and invoices, checks statuses and issues refunds if the refunds API is connected. ### Steps ### Open the shop's technical settings At partner.robokassa.ru: **«Мои магазины» → «Технические настройки»** (My shops, Technical settings). Paste the shop identifier (MerchantLogin) into **Merchant Login**. It is the shop's login, not your sign-in email. ### Check the hash algorithm The method there must be MD5. If another one is selected, switch back to MD5. ### Copy the production passwords From the production block move **Password #1** and **Password #2**. **Password #3** is only for refunds and appears once the refunds API is connected. ### How to revoke access Change the shop passwords in «Технические настройки». Here, click **Disconnect**. ### Troubleshooting - **The signature does not match**: the shop uses something other than MD5, or test passwords were pasted instead of production ones. ## Adesk Management accounting: transactions, cash flow, P&L, projects, budgets. More on the [integration page](/integrations/adesk). ### What the agent can do Reads transactions, cash flow and P&L reports, projects, liabilities and budgets. ### Steps ### Sign in as the account owner The API key belongs to the whole account and sees every legal entity, bank account and project of the profile. ### Copy the key from the profile **«Настройки» → «Профиль»** (Settings, Profile), the API access key block. Paste it into **API Token** without spaces at the ends. ### Limitations Without a trial or a paid subscription Adesk closes every API method and answers "Payment required". ### How to revoke access Click **Disconnect** here. The key in Adesk belongs to the whole account. ### Troubleshooting - **"Payment required"**: renew the Adesk subscription. - **API sign-in is locked**: after several wrong keys in a row Adesk locks sign-in for a while. Copy the key again from the profile instead of guessing.