After launching a payout module without a hold, a marketplace's seller balance went negative by 500,000 rubles due to mass returns. To prevent recurrence, we design systems with escrow and automatic calculations. Our team, with 7 years of fintech experience, has implemented payout modules for 20+ marketplaces—from startups to platforms with 10,000 sellers. Over 5 years in the market, we've built reliable financial cores that handle thousands of transactions daily. Automating seller payouts reduces operational costs by 40% and eliminates manual entry errors. Financial control of a marketplace is key to transparency and compliance with Federal Law 115-FZ.
In this article, we'll break down the key components: financial model, money lifecycle, payment gateway integration, refund handling, and document workflow. You'll learn how to avoid common mistakes and build an infrastructure that scales with your marketplace.
Automated Payout System: Architecture and Key Modules
How does the payout lifecycle work?
The buyer pays—the money arrives at the platform's account. The platform deducts its commission (typically 5–15%) and transfers the net amount to the seller. The core entities are balances and transactions stored in the database:
seller_balances ( seller_id, available_balance, hold_balance, total_earned, currency, updated_at ) balance_transactions ( id, seller_id, type, amount, balance_before, balance_after, reference_type, reference_id, status, created_at, description ) -- type: order_credit | commission_debit | payout_debit | refund_debit | adjustment Fund movement stages
- Order payment—the amount minus commission is credited to the seller's
hold_balance. - End of hold period (7–14 days after delivery)—transfer from
holdtoavailable. - Payout request—seller initiates withdrawal.
- Approval and transfer—platform sends funds via payment gateway.
- Confirmation—status set to
completed, deduction fromavailable_balance.
The hold protects against chargebacks—without it, the seller could withdraw funds and the buyer could immediately request a refund. Learn more about the escrow mechanism.
Why is the payout model important?
Automatic scheduling is the sweet spot: it reduces support load by 2x compared to manual payouts and doesn't require constant monitoring. A hybrid model (scheduled + on-demand) adds flexibility but is more complex to implement. For a marketplace with 1,000 sellers, operational cost savings can reach 2 million rubles per year. For a platform with 10,000 sellers, savings can exceed 20 million rubles annually.
| Payout Model | When to Choose | Features |
|---|---|---|
| On-demand | Few sellers, high margin | Manual work, accounting burden |
| Scheduled | Stable order flow | Minimal operations, inflexible for sellers |
| Hybrid | Large marketplaces | Trade-off, but more complex in code |
Automated scheduled payouts reduce support load by 2x compared to manual. Hybrid payout model is 1.5x more effective than purely scheduled in terms of seller satisfaction.
How to integrate payment gateways?
We choose a gateway based on marketplace requirements. Each provider has a specific webhook notification format. We configure handling of success/error and automatic balance reconciliation.
| Payment Gateway | Commission | Features |
|---|---|---|
| ЮKassa Split | 3–6% | For Russia, automatic payment splitting |
| Tinkoff Partners | — | Bank transfers, legal entity support |
| Stripe Connect | 2.9% + $0.30 | International, multi-currency support |
| PayPal MassPay | — | Mass payouts abroad |
Refund processing
On refund, the amount is deducted from the seller's available_balance; if insufficient, from hold_balance. If both are empty, a negative balance is created, blocking future payouts. In the system, this is recorded with type='refund_debit'.
- Refund to buyer—from escrow/platform balance.
- Deduction from seller:
refund_amount+ commission reversal (optional). - Record in
balance_transactions.
Document Workflow and Reporting
For Russian sellers, we generate:
- Certificate of completed work / agent report
- Invoice (if VAT applicable)
- Sales register
PDF files (via Puppeteer) are stored in cloud storage. Separate templates for sole proprietors and self-employed. All documents are available in the seller's account archive.
Seller Interface
- Current balance (available / on hold)
- Transaction history with Excel export
- Payout request form with payment details
- Payout statuses (processing / completed / failed)
Before the first payout—reconciliation of details: BIC verification and a test transfer of 1 ruble.
Security and Control
- Withdrawal limits (daily, per transaction)
- Double confirmation for amounts above threshold
- Anomaly monitoring
- Daily reconciliation with payment system
We guarantee compliance with Federal Law 115-FZ and full audit of all transactions.
What's Included in Turnkey Development
- Detailed API specification and data model
- Integration with the chosen payment gateway
- Automatic scheduled payout module
- Generation of accounting documents
- Seller's personal account with balance and history
- Deployment on the client's infrastructure
- Team training and documentation
- 30 days of technical support after launch
Timeline: 6 to 8 weeks for a typical system. Contact us to get a preliminary architecture for your system. Order development—start with an audit of your current payout flow.