Setting up payments to 1C-Bitrix marketplace sellers

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Our competencies:
Development stages
Latest works
  • image_website-b2b-advance_0.png
    B2B ADVANCE company website development
    1177
  • image_bitrix-bitrix-24-1c_fixper_448_0.png
    Website development for FIXPER company
    811
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    564
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    747
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    655
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    976

Seller Payouts Setup for Marketplace 1C-Bitrix

Seller payouts are a financial operation: the platform transfers the seller's revenue minus commission. 1C-Bitrix has no built-in tools for this. We need to implement balance tracking, payout request and confirmation process, and optionally — automatic transfer via payment gateway API.

Seller Balance Tracking

Balance is formed from financial operations recorded at each event:

  • + on sub-order payment confirmation: amount = subtotal - commission
  • on confirmed payout: amount = payout_amount
  • on customer refund: amount = -refund_amount + refund_commission

Table mp_finance_log:

Field Type Description
ID int, AI
VENDOR_ID int FK to seller
TYPE varchar sale / commission / payout / refund
AMOUNT decimal(10,2) Positive = income
REFERENCE_ID int ID of sub-order or payout request
STATUS varchar pending / confirmed / cancelled
CREATED_AT datetime

Current balance = SUM(AMOUNT) WHERE VENDOR_ID = X AND STATUS = 'confirmed'.

Payout Process

Manual payout (standard scenario for most marketplaces):

  1. Seller in personal account clicks "Request Payout", specifies amount (not exceeding available balance)
  2. Entry created in mp_payout_requests with status pending
  3. Platform manager sees request in administrative interface
  4. After actual transfer, manager confirms payout in system → status changes to completed, seller balance decreases

Minimum payout threshold, frequency (not more than once per week) — configured in b_option.

Automatic payouts via payment APIs (Tinkoff, YuMoney, CloudPayments, QIWI B2B) — add complexity but eliminate manager's manual work. On auto-payout, system initiates transfer to seller's details by schedule (Bitrix agent, for example, on Fridays). Seller's payment details must be stored encrypted.

Tax Documents

Platform must generate financial documents with payouts: service invoices (for commission), sales reports. PDF document generation via tcpdf or template. Documents linked to payout and available for download by seller and admin.

Timeline

Balance tracking and manual payouts with interface — 1–2 weeks. Automatic payouts via specific gateway API — additional 1–2 weeks. Financial document generation — additional 3–5 days.