Setting Up Payments in Bitrix24 Store
Payment in Bitrix24 Store is configured via Store → Payment. Compared to 1C-Bitrix, the number of built-in payment systems is limited, but it covers the main scenarios for common e-commerce markets.
Available Payment Systems
Bitrix24 Store supports out of the box:
- YooKassa (YuKassa) — the most widely used option
- Sberbank (online payment via acquiring)
- Tinkoff (via T-Bank acquiring)
- Cash / Bank transfer — offline payment
- Cash on delivery — for courier delivery
- Robokassa — via webhook integration
Connecting each system requires an agreement with the payment provider and obtaining API keys.
Configuring YooKassa in Bitrix24
In the Bitrix24 interface: Store → Payment → Add → YooKassa. Required parameters:
-
shopId— the store identifier in YooKassa -
secretKey— the secret key (from YooKassa settings) - Payment methods — select the available ones (card, SBP, YuMoney)
- Tax system and VAT rate — for automatic fiscal receipts
Webhook setup. The notification URL for YooKassa in Bitrix24 is generated automatically and displayed in the payment system settings. It must be added manually in the YooKassa merchant account (Integration → HTTP notifications).
Testing Payments
Before switching to live mode, test in the YooKassa sandbox:
- Enter the sandbox
shopId/secretKeyin Bitrix24 settings - Place a test order
- Verify the redirect to the YooKassa payment page
- Pay with the test card
5555555555554477 - Confirm that the order status in Bitrix24 CRM changed to «Paid»
Custom Payment Systems via REST API
If the required payment system is not supported out of the box, Bitrix24 allows creating a custom handler via REST:
// Register a custom payment system
BX24.callMethod('sale.paysystem.handler.add', {
fields: {
name: 'My Payment System',
code: 'my_payment',
sort: 100,
settings: {
PAYMENT_GATEWAY_URL: { type: 'STRING', label: 'Gateway URL' },
SHOP_ID: { type: 'STRING', label: 'Store ID' },
SECRET_KEY: { type: 'STRING', label: 'Secret Key' },
},
}
});
Timeline
| Configuration | Timeline |
|---|---|
| Connecting a standard payment system | 0.5 day |
| Setup + testing + fiscal receipts | 1–2 days |
| Custom payment system via REST | 3–5 days |







