Payment Gateway vs Payment Processor: What Merchants Need to Know

Merchants use the words gateway, processor, acquirer, aggregator and PSP interchangeably. Providers rarely correct them, because the ambiguity is commercially convenient. But the distinction determines who holds your money, who can freeze it, who underwrites your business and who you should be negotiating with. This guide makes the roles concrete.

The roles, defined properly

Payment gateway

A gateway is a technology layer. It presents a checkout, collects payment instructions securely, applies basic validation and fraud screening, routes the transaction to a processing partner and returns the result to your systems via API responses and webhooks.

A pure gateway never holds your money. It has no underwriting relationship with you in the financial sense. If your gateway also settles funds, it is doing more than gateway work — and you should ask under which licence or partnership.

Payment processor

A processor moves the transaction through the rails. It communicates with card networks, wallet operators or bank infrastructure, handles authorisation, capture, refunds and disputes, and produces the settlement data that determines what you are paid.

Acquirer or sponsoring institution

The acquirer is the licensed financial institution that carries the risk of your merchant account. It underwrites you, holds the scheme or rail relationship, and is ultimately responsible if you fail with outstanding disputes or customer obligations. Reserve requirements and offboarding decisions usually originate here, even when they are communicated by someone else.

Payment service provider (PSP)

PSP is a commercial umbrella term for a company bundling gateway, processing and often settlement into a single contract. Most merchants contract a PSP and never see the layers underneath.

Payment aggregator

An aggregator processes many merchants under its own master relationship, onboarding you as a sub-merchant. This makes onboarding fast and cheap, but you inherit the aggregator's risk profile: if the aggregator's relationship is withdrawn, your account goes with it, regardless of your own conduct.

Local method provider

In South Asia specifically, wallet operators such as bKash, Nagad, JazzCash, Easypaisa, eSewa and Khalti and the bank rails behind UPI, IMPS, NEFT and RTGS are their own layer. Your PSP's relationship with each of them determines your real method coverage and per-method performance.

Why the distinction matters commercially

Who can freeze your funds

The party that holds settlement funds controls your cash flow. If your provider is a gateway reselling someone else's processing, a decision three layers up can hold your money while your direct counterparty tells you truthfully that it is not their call. Always ask: which legal entity holds funds between collection and settlement, and in which jurisdiction?

Who underwrites you

Underwriting sets your pricing, reserve, limits and category acceptance. If your provider cannot describe its underwriting chain, it cannot defend your account when it is questioned.

How stable your setup is

Direct relationships are more stable than sub-merchant arrangements. Sub-merchant models are faster to launch and cheaper at low volume; they are also more fragile and more likely to produce sudden category-wide offboarding. Neither is universally right — but you should know which one you have.

Where the money leaks

Fees can be layered at each level. A merchant contracted to a reseller of an aggregator of a processor is paying three margins. Ask for a fee breakdown that states who charges what.

Direct model versus aggregation: a practical comparison

Direct merchant account. Your own MID, your own underwriting, typically better economics at scale, stronger stability, slower onboarding, more documentation, and often minimum volume expectations.

Aggregated sub-merchant account. Fast onboarding, minimal minimums, simple pricing, shared risk profile, greater exposure to decisions you do not control, and typically less negotiating room on reserves.

Most merchants start aggregated and move direct as volume and sophistication grow. High-risk merchants often need direct or specialist structures earlier, because aggregation of restricted categories is exactly what regulators and banks scrutinise. See how high-risk payment processing works.

How a transaction actually flows

1. The customer selects a method in your checkout.
2. The gateway captures the instruction and applies validation and fraud rules.
3. The gateway routes to a processor for the chosen rail.
4. The processor requests authorisation from the wallet operator, bank or card network.
5. A result returns through the chain, and your system receives a webhook.
6. Funds settle from the rail into the acquirer or provider's account.
7. The provider deducts fees and reserves and settles the remainder to you on the contracted cycle.
8. Settlement reporting lets you reconcile every step against your own ledger.

Disputes, refunds and returns run the same chain in reverse, with their own timings and evidence requirements. The API mechanics of steps two to five are covered in how payment APIs work.

Questions that reveal what you are actually buying

1. Are you a licensed institution, an authorised agent, or a technology provider?
2. Which entity holds my funds before settlement, and where is it incorporated?
3. Do I have my own merchant identifier, or am I a sub-merchant?
4. Who makes the underwriting decision on my account?
5. Who sets and releases my reserve?
6. Which of your local method relationships are direct, and which are through partners?
7. Who do I escalate to if funds are held, and what is the response commitment?
8. If your upstream relationship ends, what happens to my in-flight funds and my account?

A provider that answers all eight precisely is a provider you can plan around.

What this means in South Asia

Regional structures add a layer. A merchant may contract an international PSP, which uses a regional partner, which holds local banking and direct wallet integrations in Bangladesh or India. Each hop adds cost, latency in problem resolution and one more party who can withdraw. Providers with genuine direct local banking and direct wallet integrations reduce that chain — which is why the question "do you hold direct local banking?" is worth more than any pricing comparison.

Market context: Bangladesh payment gateway, India payment gateway, Pakistan payment gateway, Nepal payment gateway, and the cross-border payment guide for South Asia.

Choosing between models

Choose a gateway-only solution when you already hold your own processing and banking relationships and need technology, routing and reporting.

Choose a full PSP when you want one contract covering technology, processing and settlement and are comfortable with the provider's structure.

Choose an aggregator when speed and low volume matter more than control, and your category is unambiguously accepted.

Choose a specialist high-risk provider when mainstream providers exclude your category, when you need cross-border settlement, or when you need local collection in markets where you have no legal entity.

How PayEurasia is structured

PayEurasia combines gateway technology, direct local method integrations and dedicated local banking across four South Asian markets, settling cross-border to merchants on transparent terms. We tell merchants which relationships are direct, how settlement works and where funds sit — because those are the answers that determine whether a payment relationship survives its first difficult month.

Read the payment infrastructure overview or contact our team.

Frequently asked questions

What is the difference between a payment gateway and a payment processor?

A gateway is the technology layer that captures payment instructions, applies validation and routes transactions, returning results to your systems. A processor moves the transaction through the rails, handling authorisation, capture, refunds and disputes and producing settlement data. Many providers bundle both.

Who actually holds my money before settlement?

Usually the acquiring institution or the PSP's settlement entity, not the gateway. Ask explicitly which legal entity holds funds, in which jurisdiction, and who authorises release, because that party controls your cash flow.

What is a payment aggregator and should I use one?

An aggregator onboards you as a sub-merchant under its own master relationship. It offers fast, low-cost onboarding but ties your account stability to the aggregator's risk profile. It suits smaller, unambiguously low-risk merchants; larger or restricted-category merchants usually need direct or specialist structures.

Do I need my own merchant account?

Not initially. A dedicated merchant account gives better economics at scale, stronger stability and more negotiating room on reserves, but requires more documentation and volume. Many merchants begin aggregated and migrate as they grow.

Why does the provider structure matter for high-risk merchants?

Because restricted categories are exactly where upstream banks and regulators intervene. A long chain of intermediaries means more parties who can withdraw support with no notice, and slower resolution when funds are held. Direct relationships are materially more durable.

How can I tell what type of provider I am dealing with?

Ask whether they are licensed, authorised as an agent, or purely technology; whether you receive your own merchant identifier; which entity holds funds; who underwrites and sets reserves; and which local method relationships are direct rather than partner-supplied.