Merchant Rails What happens to a card payment between the tap and the deposit.

Merchant Rails

WHO DOES WHAT

Gateway versus Processor versus Acquirer: Who Does What

By Baruch Mackliff · · 5 min read

Three different companies stand between your customer's card and your bank account, and knowing which one owns a problem is what gets it fixed quickly.

A card sale looks instant and involves at least four companies, none of which is the one whose logo is on your terminal. That is why support calls bounce. You describe a funding problem to a company that has never touched your money, or a decline to a company that has no view of the authorization.

The short version. A gateway carries the request out of your business. A processor moves it across the card networks and settles the money afterward. An acquirer is the bank that holds your merchant account and carries the risk. Everything else in this business is one of those three wearing a different name, or a reseller sitting in front of them.

The four parties on any card sale

Your customer's card was issued by a bank, and that issuing bank holds the money and decides whether to approve the request. The card network moves messages between banks and writes the rules everyone follows. The acquiring bank stands behind your merchant account and is liable to the network for your sales. And you are the fourth, selling something.

Interchange flows from the acquirer to the issuer. Assessments flow to the network. Money flows back the other way, from the issuer through network settlement to the acquirer, and then into your bank account. No gateway appears in that sentence, because the gateway is not in the money path at all.

What each one actually does

The gateway

The gateway is software. It takes card details from your checkout page, your virtual terminal or your phone order screen, encrypts them, and sends an authorization request onward. The approval or decline comes back through the same pipe.

It also does the things you touch daily. The vault that stores customer cards as tokens so you are not holding numbers. Recurring billing schedules. Transaction search. Refunds from a browser. Address verification and security code checks. The reporting screen you actually log into.

If your business takes payments online or over the phone, the gateway is the part you interact with most and the part most likely to be a separate company with a separate bill.

The processor

The processor connects to the card networks. Its front end routes your authorization request to the right network and back. Its back end takes your batch once you close it, clears the transactions, works out which interchange category each one qualified for, and builds the funding file that sends your money.

Your statement is a processor product. So is the timing of your deposit, the batch cutoff that decides whether today's sales fund tomorrow, and the category detail that tells you what your volume actually cost.

The acquirer

The acquirer is a bank and a member of the card networks. It holds your merchant account, it underwrote you, and it is liable to the network if you take money and fail to deliver.

Which means the acquirer holds every decision that actually hurts. Whether to stop a batch. Whether to impose a reserve. Whether to close the account. Whether to file a termination record that follows you to the next bank. The reseller who sold you the account cannot overturn any of that, and neither can the gateway.

The reseller and the aggregator

Two more roles sit in front of that structure, and most small merchants are dealing with one of them.

An ISO, sometimes called an MSP, is a reseller registered with the card networks under an acquiring bank's sponsorship. It sells the account, sets your pricing inside the program the bank allows, and handles your service calls. It is not the bank. When your agreement refers to a Bank and a Servicer as separate parties, the Servicer is usually this company, and the Bank is the one whose name you had to hunt for.

An aggregator, or payment facilitator, works differently. It holds one master merchant account and places you underneath it as a sub-merchant. That is why the signup took ten minutes and nobody asked for two years of financials. You did not get your own merchant account, and you are sharing a risk profile with everyone else on the platform.

Both models work. They fail differently. An ISO relationship gives you a merchant account of your own, an underwriting conversation, and usually someone who answers the phone, in exchange for more paperwork at the start. An aggregator gives you speed and a flat price, in exchange for the platform's ability to switch you off with an automated message when its own risk model decides it should.

One company wearing three hats

Most providers now sell all of this as a single product, and there is nothing dishonest about that. A company can own its gateway, run its own processing platform and hold a sponsorship arrangement with a bank, so one brand covers every layer and one app shows you everything.

What it costs you is visibility. When every function answers to the same support queue, nobody has to tell you which layer made a decision, and a sentence about the risk team reviewing your account could mean an automated model at a technology company or an underwriter at a bank whose name you have never seen. Ask which one anyway. Even inside a single company, the function that owns your problem determines who is able to change the outcome and how long that will take.

When something breaks, this is the map

Two questions before you sign anything

First, who is the acquiring bank, and is that name written in the agreement. You want it before you need it, because the day you need it is the day somebody is holding your money.

Second, what happens to your stored cards if you leave. If your customers' cards live as tokens in a gateway vault, those tokens belong to that gateway, and a business with recurring billing that cannot move them is a business that cannot change providers without asking every customer to enter a card again. Ask in writing whether a vault migration to another provider is supported. Ask before you load ten thousand tokens into it, rather than after. And ask what a migration actually produces, because a transfer that hands you a spreadsheet of card numbers is not a migration at all. It is a security problem with your name on it.

Common questions

what is the difference between a payment gateway and a processor

The gateway is software that captures the card details and carries the authorization request out of your business, while the processor is the platform connected to the card networks that moves that request to the issuing bank and later settles the money. One is the door, the other is the road. Many companies sell both together under a single brand, which is why the terms get used as though they meant the same thing.

do i need a gateway if i have a card terminal

Not usually, because a modern terminal carries its own secure connection to the processor and performs the gateway's job internally. You would add one if you also take payments online or by phone and want those transactions, stored cards and reporting in the same place as the counter sales. Adding a gateway means an additional monthly charge and an additional account to maintain.

who actually holds my merchant account

An acquiring bank holds it, and that bank is a member of the card networks and carries the liability for your chargebacks. The company you talk to may be a reseller or a technology provider rather than the bank itself, which is why the bank's name usually appears in the small print of your merchant agreement rather than on the front of it. Find that name before you need it.

More on this