In payment gateway vs payment processor vs payment aggregator, you are looking at three jobs rather than three products. The gateway moves data. The processor moves money and talks to the card networks. The aggregator holds a merchant account and rents you space inside it. One company often does all three.
The three roles at a glance
| Role | Its job | Holds your funds | Carries your risk |
|---|---|---|---|
| Gateway | Encrypts and transmits card data from checkout to processor | No | No |
| Processor | Routes authorisations and settlement through the card networks | Briefly, in transit | Only via its bank relationships |
| Aggregator | Holds a master merchant account, you sell as a sub-account | Yes | Yes, which is why it reviews you |
The column that matters when things go wrong is the last one. Whoever carries the risk makes the decisions.
Payment gateway vs payment processor vs payment aggregator, when something breaks
A single symptom, three very different causes.
Cards are declining at checkout and nothing has changed on your end. That is usually issuing banks, reached through the processor, not the gateway. The gateway is reporting a decision, not making one.
Checkout throws an error, or the page never loads the card field. That is gateway territory: credentials, an expired certificate, a plugin update, an integration change.
Payments succeed but nothing arrives in your bank, or a notice says your account is under review. That is the account holder, which means the aggregator or the acquiring bank behind a dedicated account. No amount of gateway troubleshooting touches it.
Knowing which of the three you are dealing with tells you who to contact and what to ask for, which on a bad week is worth more than the definitions themselves.
Who actually decided to stop your money?
Follow the risk, not the logo on the dashboard.
If you signed up in minutes with no underwriting and no separate merchant number, you are almost certainly on an aggregator’s account. Its risk team made the call, its terms of service govern it, and its appeal path is whatever that company published.
If you went through underwriting, submitted documents and were issued your own merchant identification number, an acquiring bank approved you and that bank can withdraw the approval. The company you speak to may be the one that placed the account, but the decision came from the bank. That structural difference is laid out on aggregator versus merchant account.
Either way, the gateway is not the author of the decision. It is the messenger, and replacing it changes nothing about the underlying problem.
Which of them can put you on MATCH?
The acquirer. MATCH, which Mastercard calls the Mastercard Alert to Control High-risk Merchants and which was formerly the Terminated Merchant File, is a database acquirers add terminated merchants to. Under Mastercard’s Security Rules and Procedures, Merchant Edition, a processor must add a qualifying terminated merchant within one business day, listings stay for five years and are then purged automatically, and only the acquirer that placed a listing can remove it, and only if it was added in error or the listing is reason code 12 for PCI non-compliance and compliance has since been confirmed. Mastercard does not assess whether a listing is accurate.
Aggregators are not exempt from this. A closure by an aggregator can still meet the criteria for a qualifying termination. Stripe publishes in its own documentation, at https://docs.stripe.com/disputes/match, that it generally cannot process for MATCH-listed businesses absent extenuating circumstances, which is a useful illustration of how much weight the listing carries downstream. What a listing actually contains is covered on our MATCH list page.
What the distinction changes about your next move
If a gateway failed, you fix an integration or install another one, and you are trading again the same day.
If an aggregator closed you, you need an account of your own, which means underwriting, documents and a bank willing to review a file that now has a closure in it. That is a slower road and a survivable one, and it starts with getting the story and the paperwork straight rather than firing off applications. If it was Stripe specifically, what happens after Stripe closes an account covers the sequence. When you are ready to rebuild both halves, the account and the checkout, our high risk payment gateway page explains how they get set up together, and high risk credit card processing covers what changes once you have your own merchant account.
Frequently asked questions
Can one company be all three? Yes, and most of the familiar names are. They provide the gateway software, act as or contract with the processor, and hold the master merchant account you sell under. That bundling is convenient right up until the moment you need to know which function made a decision about you.
Do I get to choose my gateway if I have a dedicated merchant account? Often yes, though some accounts are tied to a specific gateway by the processor that placed them. Ask during onboarding rather than after, because rebuilding a checkout you already trust is avoidable work.
Is a payment facilitator the same as an aggregator? In practice the terms are used for the same structure: an entity holding a master merchant account with sub-merchants selling underneath it. Payment facilitator is the formal card-network term. Aggregator is the everyday one.
Which one sets my rates? The pricing you see comes from whoever holds the account relationship, built on top of interchange set by the card networks and the acquirer’s own margin. That is why rates depend on your volume, your average ticket and your industry rather than a published card.
If my processor drops me, does my gateway contract end too? Not automatically. Gateway agreements are usually separate, and you may keep paying for a gateway with nothing behind it. Check the contract, and cancel or repoint it deliberately rather than assuming it lapsed.