Payment Aggregator vs Direct Merchant Account: Key Differences
Basics4 minInnovialabs editorial team
In short
An aggregator accepts payments for you under its own bank contract, so onboarding is fast but you get less control and higher freeze risk; a direct merchant account takes more paperwork but gives you your own terms and stability at high volume.
The short answer
A payment aggregator (payment facilitator) is a company that already has a contract with an acquiring bank. You sign up with the aggregator, not the bank: it collects money from customers into its own account and pays it out to you minus a fee. Stripe and PayPal work this way, as do many local payment services that onboard stores under their own agreement.
A direct merchant account means you sign the contract with the acquiring bank yourself. The bank gives you your own merchant ID (MID), funds settle straight to your business account, and terms are negotiated individually.
Put simply: with an aggregator you are one of many sub-merchants under a shared umbrella; with direct acquiring you are the bank's own client.
Side-by-side comparison
| Parameter | Aggregator | Direct merchant account |
|---|---|---|
| Who holds the bank contract | The aggregator | You |
| Onboarding | Online form, often days | Bank underwriting, documents, longer |
| Fees | Usually a flat public rate | Negotiated, depends on volume and risk |
| Payout speed | Set by aggregator rules, holds possible | Set by contract, usually predictable |
| Control over settings | Limited to platform features | Wider: own MID, limits, payment methods |
| Freeze risk | Higher: automated risk monitoring | Lower, though banks can suspend too |
| Integration | Ready SDKs, widgets, CMS plugins | Via bank gateway or processor, often harder |
Contract, fees and payouts
Contract. With an aggregator you accept its terms of service. That is convenient, but terms can change unilaterally and the aggregator decides disputes. A direct merchant agreement is two-sided, so payout timing, reserves and pricing can be negotiated.
Fees. An aggregator charges for risk, infrastructure and convenience, so its rate is usually higher than what a bank offers a large merchant. In return there is no monthly fee or minimum volume. Direct acquiring gets cheaper as volume grows, but brings extra costs: gateway fees, PCI DSS compliance, maintenance.
Payouts. An aggregator may hold funds for several days and apply a rolling reserve, keeping part of revenue back to cover refunds and chargebacks. With a bank, payout timing is fixed in the contract.
Why aggregators freeze accounts
An aggregator is liable to its bank for every sub-merchant, so it reacts to risk quickly and automatically. Common triggers:
- a sudden spike in volume with no history;
- many refunds or chargebacks (disputed payments);
- products in categories its rules prohibit or treat as high risk;
- a website that does not match the declared business;
- customer complaints and signs of fraud.
The result can be held payouts, document requests or, at worst, account closure with funds held for the chargeback window. For a store with a single payment channel, that means sales stop.
How to choose: decision table
| Situation | Recommendation |
|---|---|
| New store, low volume, need to launch fast | Aggregator |
| Testing a niche or selling seasonally | Aggregator |
| Volume grows steadily and fees are now a real cost line | Negotiate direct acquiring |
| High average order value, many repeat payments | Direct account or hybrid |
| Need special payment methods, own limits, multi-currency | Direct account |
| Cannot afford to depend on one provider | Two providers: primary and backup |
Many stores start with an aggregator, then move to a direct contract or keep two channels: if one is blocked or down, customers pay through the other.
Common mistakes
- Comparing only the fee rate without reading the hold and reserve rules.
- Not checking whether your products are allowed under the aggregator's policy.
- Running a single payment channel with no fallback.
- Delaying refunds until they turn into chargebacks.
- Not storing the provider's transaction IDs in your own system, which makes reconciliation manual.