A payment aggregator is a service that gives a business access to several payment methods through a single contract and a single integration. Instead of separate connections to a bank, SBP and Pay services, the merchant gets one payment form and one dashboard.
How it differs from direct acquiring
With direct acquiring a company signs a contract with a specific bank, passes its review and integrates with its payment gateway. Every additional payment method is a separate story: its own contract, its own integration, its own reports.
An aggregator absorbs that work:
| Direct acquiring | Aggregator | |
|---|---|---|
| Contracts | One per method | One |
| Integrations | Several | One |
| Reporting | Fragmented | In one dashboard |
| Time to launch | Longer | Usually faster |
Who it suits
- Small and mid-sized businesses without a dedicated payments team.
- Projects that need many methods at once: cards, SBP, Pay services.
- Teams launching fast who cannot wait out long approvals.
What to look at when choosing
- The set of payment methods and whether they share one rate.
- Transparency: what the rate covers, whether onboarding is charged.
- Fiscalisation under 54-FZ if you sell to individuals.
- Integration options: ready-made modules, an API, payment links.
- How refunds and disputes are handled.
One distinction matters: an aggregator provides the technology and infrastructure, while the settlements themselves are carried out by licensed financial organisations. That is how MulenPay operates — see internet acquiring.
