Merchant Acquiring Explained: Acquirer vs Processor vs Acquiring Bank vs PayFac

What is merchant acquiring?

Merchant acquiring is the end-to-end process of enabling a business to accept and get paid for card transactions. The party that provides it — the merchant acquirer — does three core jobs:

1. Holds the merchant account — the account where card funds land before they're paid out to your business bank account.
2. Works with the card networks — it connects to Visa, Mastercard and other networks so your transactions can be submitted into them. (Acquirers are generally members of, or sponsored into, the card networks; the exact membership/licensing model varies by provider and region.)
3. Carries the financial risk — if a merchant issues refunds or chargebacks it can't cover, or goes out of business, the acquirer is on the hook. That's why an acquirer underwrites (vets) the businesses it onboards.

"Merchant acquirer" and "merchant acquiring services" describe the same thing from different angles — the provider vs. the service. You may also see "acquiring bank," which emphasises that the acquirer is, or works as, a bank or regulated financial institution.

What is a merchant acquirer?

A merchant acquirer is the bank or financial institution that holds your merchant account and settles card funds into it. "Acquirer", "acquiring bank" and "merchant bank" usually mean the same role. To limit that liability, acquirers and their processors run authorization-time risk checks — most commonly the Address Verification Service (AVS) — to catch fraud before it becomes a chargeback.

How merchant acquiring works

A single card payment is usually described in three stages:

1. Authorization — the customer pays; the acquirer (via a processor) asks the card network, which asks the issuer: is this card valid and are funds available? The issuer approves or declines in real time.
2. Clearing — the approved transaction details are exchanged between issuer and acquirer through the network so both sides agree on what is owed.
3. Settlement — the issuer moves funds to the acquirer, and the acquirer deposits them (minus fees) into the merchant's account.

This is the four-party model: merchant → acquirer → card network → issuer (with the cardholder at the start). A payment processor may handle the technical messaging at several of these steps, but it is not the same role as the acquirer (see next section).

Merchant acquirer vs payment processor

This is the single most common point of confusion. A common way the industry frames it: the acquirer is the "business arm" — it holds the merchant account, settles funds and carries the risk — while the payment processor is the "technical arm" that routes the transaction data between parties. In practice one company is often both — many large providers are acquirer and processor — which is exactly why the words get used interchangeably. The distinction still matters when you choose a partner: you need acquiring (someone to hold the account and carry the settlement risk) and processing (the technology). This "business arm vs technical arm" split — also framed as the financial/settlement side vs the technical/processing side — is a useful mental model, not a strict legal definition.

How to tell which one your provider is

You don't need a provider's internal licensing details to tell which role it plays for you. Ask two questions:

• Does it hold your merchant account and settle funds to your business account? If yes, it's acting as your acquirer (or has an acquirer behind it).
• Does it route your transactions and return approvals or declines? If yes, it's performing the processing function.

If the same provider does both, it's a full-stack acquirer-processor — which is common. If the marketing doesn't make it clear, ask directly: "Do you hold my merchant account and settle my funds, or do you route transactions to an acquiring partner?" The answer tells you which role they own and whether there's a separate acquirer in the chain.

When the distinction matters

For most businesses the labels don't matter day to day. They matter in three situations:

• Cross-border sales — where and how your transactions are acquired can affect approval rates and cost (the size of the effect depends on your markets, card mix, and setup). The acquirer relationship is the lever here, not just the processing technology.
• Switching or adding a processor without changing who holds your account — only possible if you know which provider owns which role.
• Running a multi-acquirer setup that routes transactions to different acquirers by market — that only makes sense once you separate the acquiring role from the processing layer.

Acquiring bank vs issuing bank

• Acquiring bank — on the merchant's side; receives the funds and holds the merchant account.
• Issuing bank — on the customer's side; issued the card, pays out on the customer's behalf, then collects from them.

Both are banks or regulated institutions that operate within the card-network system, but they sit on opposite ends of the transaction. If you accept payments, you work with an acquirer; the issuer is your customer's bank, not yours.

Merchant acquirer vs payment facilitator (PayFac)

A payment facilitator (PayFac) is not a fourth party in the transaction — it's a business model on top of acquiring:

• A merchant acquirer gives your own merchant account (more setup, more control, typically suited to larger volumes).
• A payment facilitator holds one master merchant account and lets many smaller businesses ("sub-merchants") accept payments under it — faster onboarding, less paperwork, but you operate within the PayFac's account and rules.

The trade-off is control & cost at scale (acquirer) vs speed & simplicity of onboarding (PayFac). A closely related bundled model is the payment service provider (PSP) — the provider that packages the checkout gateway, processing and an aggregated merchant account into one signup: see what is a payment service provider.If you are weighing the PayFac route specifically, see the payment facilitator model for sub-merchant onboarding, liability and compliance responsibilities in depth. 

At a glance — acquirer vs acquiring bank vs processor vs PayFac(acquirer ≈ acquiring bank when the acquirer is a bank):

Merchant account and payment gateway — where they fit

• A merchant account is the holding account the acquirer provides for your card funds. ("Do I need a merchant account?" — if you accept cards directly through an acquirer, yes; if you use a PayFac/PSP, you may operate under theirs.)
• A payment gateway is the software that captures card details at checkout and passes them to the processor/acquirer. A gateway is not a merchant account — they're complementary, and the provider of one is often a separate company from the provider of the other.

Full comparison: for the difference between a merchant account and a payment gateway — and whether you need both — see merchant account vs payment gateway. For how the gateway differs from the payment processor, see payment gateway vs payment processor.

Card acquiring and local acquiring

"Card acquiring" is simply acquiring focused on card transactions (as opposed to other payment methods). Where it gets strategically important is local vs cross-border acquiring:

• Local acquiring — your transaction is acquired inside the customer's country or region, through an acquirer with local card-network connections. This is often associated with better authorization (approval) rates, because the issuer sees a familiar, domestic transaction.
• Cross-border acquiring — your transaction is acquired outside the customer's country. It can be faster to launch (it may not require a local entity or bank account) but is often associated with higher fees, more intermediaries, and more declines.

(These local-vs-cross-border trade-offs are described qualitatively; the actual effect depends on your markets, card mix and setup.)For a side-by-side breakdown of the routing, settlement and authorization-rate trade-offs, see how local and cross-border acquiring differ. 

Why merchant acquiring matters for cross-border businesses

If you sell into multiple countries, your acquiring setup affects how much of your revenue you actually capture. The same card payment can be approved in one market and declined in another partly because of how and where it's acquired. Businesses expanding internationally often move from a single cross-border acquirer toward local acquiring in their key markets, sometimes via a multi-acquirer setup that routes each transaction to the most relevant acquirer. The aim is usually to improve approval rates and reduce cost — though the size of any benefit depends on your markets, card mix and volumes.

This is the layer where an acquiring partner with genuine cross-border and local reach can affect your economics — which is where HaiPay focuses.

That's exactly the problem payment orchestration is built to solve — it decides which acquirer handles each transaction automatically.

How HaiPay acquiring fits

HaiPay offers acquiring and cross-border payment services for businesses that sell into multiple markets. The aim is to help you accept payments where your customers are and route them in a way that supports approval rates and cost.

To see whether HaiPay acquiring fits your markets and volumes, explore HaiPay acquiring or get in touch with the team.

Sources

• Wikipedia — Acquiring bank and Merchant account: definitions of the acquirer and merchant account, the acquirer's role in settlement, and its solvency/chargeback risk.
• Office of the Comptroller of the Currency (OCC), Comptroller's Handbook — Merchant Processing: U.S. bank-regulator guidance stating that "banks offering merchant processing are called 'acquiring' banks," that merchant processing is "separate and distinct" from card issuing, and that acquiring banks carry chargeback/credit risk.