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 — also called an acquiring bank or, in the OCC's wording, an acquiring bank that "contracts with merchants for the settlement of card transactions" — is the regulated institution that holds your merchant account, settles card funds into it and carries the chargeback and default risk on your account.

That last part is why acquirers underwrite the businesses they onboard, and why they and their processors run checks at authorization time to catch fraud before it becomes a chargeback. Which checks apply depends on your market, card scheme and provider: the Address Verification Service (AVS) is widely supported on US and UK card issuers but is not available on most non-card local payment methods, so it is not a universal control.

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. On card rails this is also where an acquirer reference number (ARN) typically becomes available — the tracking number used to trace a payment or refund between banks. Whether you can see an ARN, and when, depends on the card scheme and on your acquirer's or PSP's implementation.
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. The four parties are the cardholder, the merchant, the acquirer and the issuer. The card network (Visa, Mastercard) is not one of the four — it sits in the middle as the infrastructure and the rulebook both banks operate under. 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).

The four parties are the cardholder, the merchant, the acquirer and the issuer.

How merchant acquirers make money

What you pay an acquirer is not one fee. It is a stack, and only the top layer is actually the acquirer's:

Interchange — paid by the acquirer to the issuing bank on each transaction. Set by the card network as published schedules, not negotiable by you, and it varies by card type, channel and region.

Scheme fees — paid to the card network itself (Visa, Mastercard) for using the rails. Also set by the network.

Acquirer markup — the acquirer's own margin. This is the only layer your provider actually sets, and the only one a negotiation can move.

How that stack is presented to you is the pricing model:

Interchange++ shows you all three layers separately, so you can see the markup. It rewards volume and card-mix transparency, and it makes month-to-month comparison harder.

Blended or flat-rate gives you one number covering all three. It is easier to forecast and it hides where your money goes — including when interchange falls and the saving is not passed on.

Neither model is inherently cheaper. The question to ask is which layer moved when your effective rate changed last quarter. For a line-by-line breakdown of what each fee covers, see payment gateway fees.

HaiPay's published pricing starts at 2.5% + US$0.30 for eligible card transactions and from 0.8% for local payment methods, priced by market, with no setup or monthly fees; interchange++ pricing carries a US$1,000 minimum monthly processing volume. These are published list figures; the rates, fees and minimums that apply to your account are confirmed in your quote.

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). "Payment service provider" (PSP) is a broader, looser term: some PSPs bundle the gateway, processing and an aggregated account into one signup (the PayFac-style model above); others give you your own merchant account and act as, or sit in front of, an acquirer. Which one you are getting is a contract question, not something the label tells you — 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 — the typical functional role of each party. One company often plays several of these at once, and the legal split is set by your contract and your market, not by the label:

Reserves, holds and when an acquirer keeps your money

Because the acquirer carries the loss if you cannot cover your own refunds and chargebacks, it protects itself by holding some of your money back. This is the part of acquiring that surprises merchants most, and it is a contract term, not a fixed industry rule.

The three common shapes:

Rolling reserve — a set percentage of each settlement is withheld and released on a rolling schedule. The most common form.

Upfront reserve — a fixed sum held from the start, typically where there is no processing history to underwrite against.

Capped reserve — withholding continues only until a ceiling is reached, then stops.

What usually triggers a reserve or a tightening of one: a new account with no history, a chargeback ratio moving toward scheme monitoring thresholds, a sudden change in volume or average ticket, a shift in what you sell or which markets you sell into, or a delivery model where the customer pays long before the goods or service arrive.

Reserve terms are a contract question: ask for the trigger, duration, release condition and notice period in writing.

Under a payment facilitator you sit inside someone else's master account, so a hold or a termination decision can reach you faster and with less notice than under your own merchant account — that is the practical cost of faster onboarding.

Ask any provider, in writing, before you sign: what triggers a reserve, at what percentage, for how long, what releases it, how much notice you get before terms change, and who you contact when funds are held.

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.

One distinction worth keeping straight: cross-border and foreign exchange are not the same event. A transaction can be cross-border (the merchant and the cardholder are in different countries) without any currency conversion happening, if presentment and settlement are in the same currency. Cross-border assessments and FX markup are separate line items, and you can be charged one without the other.

(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.

What to ask a merchant acquirer before you sign

1 · Whose account is it? Do you hold my merchant account, or do I operate as a sub-merchant under yours? Get the answer in the contract, not the sales deck.

2 · Who is the acquirer of record in each market I sell into? One provider often uses different acquiring partners by region.

3 · Which pricing model, and what is the markup? Interchange++ or blended — and if blended, what happens to my rate when interchange changes.

4 · What is the full fee list? Setup, monthly, per-transaction, refund, chargeback, cross-border, FX markup, minimum monthly volume, early termination.

5 · Which currencies can I settle in, and where does FX get applied? A cross-border transaction does not automatically involve a currency conversion — presentment currency, settlement currency and cross-border assessment are three separate things.

6 · When do funds arrive? Ask for the tier in calendar days and the arrival rule — what happens when the settlement date lands on a weekend or a public holiday.

7 · What are the reserve terms? Trigger, percentage, duration, release condition, and notice period before any change.

8 · Can I onboard my entity and my industry? Ask about your specific registration country and business model before you invest in integration.

9 · What happens when I want to leave? Who owns the tokenised card data, can it be migrated, and how long does account closure take.

Take the answers to all nine in writing. A provider that will not answer 1, 7 or 8 in writing is telling you something.

How HaiPay acquiring fits

Run the nine questions above at HaiPay and here is where we land. HaiPay supports local pay-ins across 30 markets that have local payment methods, plus 4 markets served by international cards only (Macau, Europe, the United States and Canada) — 34 markets in total — with 150+ local payment methods across key markets and 140+ settlement currencies. International card payments typically settle in T+5 (calendar days): the tier is counted in calendar days and funds land on the first working day at or after that count, so transactions captured over a weekend or public holiday settle together on the next working day. Method availability by market is confirmed in your quote.

Local payment methods settle faster in several markets — as fast as T+1 (calendar days) in Indonesia, Vietnam, Thailand, the Philippines, India, Brazil, Mexico (SPEI) and Bangladesh. Method availability by market, your settlement tier and your rates are confirmed in your quote.

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. Accessed 8 September 2026.
• Office of the Comptroller of the Currency (OCC), Comptroller's Handbook — Merchant Processing (Version 1.0, August 2014), accessed 8 September 2026. U.S. bank-regulator guidance: "A bank that contracts with merchants for the settlement of card transactions is an acquiring bank." The handbook also states that card payment-related processing "is separate and distinct from a bank's business of issuing payment cards," and that "an acquiring bank is potentially liable for losses caused by merchant fraud."
• Visa, Visa Core Rules and Visa Product and Service Rules, 18 April 2026, accessed 8 September 2026: "An Acquirer that contracts with a Payment Facilitator is liable for all acts, omissions, and other adverse conditions caused by the Payment Facilitator and its Sponsored Merchants.