They are layers, not alternatives
Most payment comparisons go wrong by treating these terms as rival products. A gateway is the technology layer: it captures payment details at checkout, encrypts and tokenises them, and passes them for authorisation. It moves data, not money, and it does not underwrite anyone. A processor executes the transaction, routing authorisation requests to the networks and handling settlement. An acquiring bank holds the merchant account that receives the funds and carries the ultimate financial risk for the merchants it underwrites. A payment aggregator, also called a payment facilitator, sits on top: it holds one master merchant account with an acquirer and onboards many businesses as sub-merchants beneath it, taking on underwriting and risk monitoring in exchange for fast onboarding and a blended price. A merchant of record is different again: a legal role, not a technical one, where the provider becomes the seller and takes tax and liability.
- Ask which layer a provider actually occupies before you compare it with another.
- Remember that a gateway alone still leaves you needing a merchant account and a processor.
- Treat merchant of record as a legal arrangement, not a payment feature.
- Expect most modern providers to bundle several layers into one product.
Who holds the merchant account
This single question explains most of the differences in price, speed and control. With an aggregator, the provider holds the master account and you are a sub-merchant beneath it, which means you have no merchant ID of your own and the provider's risk team decides your fate. With a payment facilitator you may get a sub-merchant ID, which helps reporting and gives you slightly more standing without changing the underlying structure. With a direct acquirer relationship you get your own merchant ID, your own interchange-plus pricing, and direct control over routing and dispute handling. The trade-off is that the acquirer underwrites you directly, which takes longer and demands more documentation. For a business with a short operating history, thin financials or a higher-risk category, the aggregator is often the only door that opens at all.
- Ask whether you get your own merchant ID or a sub-merchant ID.
- Ask whose risk team can freeze your settlements, and on what grounds.
- Ask what documentation underwriting requires, and how long it takes.
- Ask whether a direct acquirer relationship is available at your current volume.
What it means for pricing
Aggregators price for simplicity: a flat or blended rate that is easy to forecast and requires no negotiation. That predictability has a price, and it shows up as volume grows, because a blended rate has to cover the most expensive transaction types in your mix. A direct acquirer relationship usually means interchange-plus, where the card network's interchange passes through at cost and the acquirer adds a disclosed markup. That is more transparent and usually cheaper at steady volume, but it fluctuates month to month and requires someone in your finance function who can read a settlement statement. Neither model is universally better. The right test is your effective rate, calculated as total fees divided by gross sales, compared across providers using the same volume, average ticket, method mix and dispute rate.
- Compare effective rates, not headline percentages, across an identical transaction profile.
- Ask whether the quote is blended, interchange-plus, or tiered, because tiered is the least transparent.
- Ask whether pricing is fixed for the contract term or can be changed on notice.
- Re-run the comparison whenever your method mix or average ticket shifts materially.
What it means for settlement and chargebacks
Settlement timing differs structurally. Aggregators often pay out on a fast, configurable schedule but retain broad discretion to hold funds, and automated risk rules can freeze an account quickly with limited notice. Direct acquirer relationships typically settle over a slightly longer cycle but with reserve terms set out and disclosed in the contract. Chargeback exposure is the more consequential difference. Under an aggregator, the provider absorbs the underwriting and monitoring work but chargeback liability usually still sits with you as the sub-merchant. Under a merchant of record arrangement, liability moves to the provider. Whichever model you use, the acquirer's risk team is the part of the relationship that matters when something goes wrong, and a cheap headline rate is worth very little if settlements are frozen during a dispute spike.
- Ask for the reserve calculation method, the trigger conditions and the release schedule in writing.
- Ask what notice you get before funds are held, and what the escalation path is.
- Ask who is liable for a chargeback under each model you are considering.
- Ask about the payout calendar, cut-off times and any minimum settlement amount.
What it means for onboarding speed
Onboarding is where the models diverge most visibly. An aggregator can approve a straightforward business in minutes to a few days, because it is applying its own risk rules to a sub-merchant rather than submitting you to a bank. A direct merchant account with an acquiring bank takes days to weeks and involves manual underwriting, financial statements, and often a longer KYC process. A local acquirer in an emerging market is slower still, because it usually requires a locally incorporated entity, a local bank account, local directors or representatives, and a local compliance file. If you need to test a market this quarter, that difference alone decides the question. If you are committing to a market for years, the slower path may still be worth walking. Ask how long a hold typically lasts and what evidence clears it fastest.
- Ask for a realistic, written onboarding timeline rather than a marketing estimate.
- Ask what the KYC document list is before you commit engineering resources.
- Ask whether you can start on an aggregator and migrate later without re-integrating.
- Weigh onboarding speed against the cost of being locked into the wrong model.
How a small merchant should choose
Start from the market, not from the provider. If you are selling into Western markets with a simple corporate structure, a full-stack provider such as Stripe or Adyen will cover you well. If you are selling into Latin America, Southeast Asia or Africa and need Pix, SPEI, OXXO, QRIS, GCash or mobile money, a regional cross-border specialist such as dLocal, EBANX or Rapyd will get you live far faster than trying to contract with local acquirers country by country. Consider a direct local acquirer relationship only when one market's volume is large enough that the per-transaction saving covers the cost of a local entity, local banking, local compliance and the people to run it. Until then, the aggregator is not a compromise, it is the right tool. That is a reasonable trade at the start of a market entry and a poor one once you are at scale.
- Choose by target market first, then by pricing, then by feature list.
- Use a cross-border specialist for emerging-market local methods rather than a domestic acquirer.
- Revisit the direct acquiring question market by market, not globally.
- Keep a second provider identified so a single relationship is not a single point of failure.
Questions merchants ask
What is the difference between a payment gateway and a payment processor?
A gateway is the technology that captures and encrypts payment details at checkout and passes them for authorisation. It moves data, not money. A processor executes the transaction, routing authorisation requests through the card networks to the issuing bank and handling settlement. Most modern providers bundle both, which is why the terms get blurred, but the distinction matters if a vendor offers only a gateway and you still need a merchant account elsewhere.
Is a payment aggregator the same as a payment facilitator?
In practice, yes. Aggregator is the older term and describes the structure: many merchants grouped under one master merchant account. Payment facilitator is the formal designation for the company holding that master account and onboarding sub-merchants beneath it. One nuance worth checking is whether you receive a sub-merchant ID, which helps reporting and gives you slightly more standing with the schemes.
Do I need my own merchant account to accept payments?
No. If you sign up with an aggregator and can take a payment the same day without submitting financials, you are a sub-merchant under the provider's master account and you do not have your own merchant ID. You get speed and simplicity in exchange for less control over pricing, routing and disputes. Your own merchant account becomes worth the effort once volume is steady and predictable.
When should a small merchant move from an aggregator to a local acquirer?
When one market's volume makes the arithmetic work. A direct acquirer relationship usually lowers the per-transaction cost and gives you control over routing and disputes, but it requires a local entity, a local bank account, local compliance and often local staff. Move when the saving on per-transaction cost comfortably exceeds those fixed costs over a horizon you can actually plan for, not simply because volume went up.
Who is liable for chargebacks under each model?
Under an aggregator or payment facilitator, the provider handles underwriting and monitoring but chargeback liability usually stays with you as the sub-merchant. Under a direct acquirer relationship, liability is yours under terms set out in your merchant agreement. Only a merchant of record arrangement moves liability to the provider, along with tax remittance and the legal role of seller, and it is priced accordingly.
What is a merchant of record and do I need one?
A merchant of record is the entity legally accountable for a sale: it remits the relevant taxes, absorbs chargeback liability, maintains compliance obligations and appears on the buyer's statement. It suits digital and subscription sellers facing VAT or sales tax across many countries, and businesses scaling faster than their finance function. It is less relevant for physical goods, where customs and import tax obligations cannot be delegated away so easily.