Blog

November 11, 20269 min readАдминистратор

Acquirer vs processor: how card acquiring works

Acquirer, processor, gateway and PSP are often used as synonyms, but they carry different roles and liabilities. How a card payment moves through the four-party model, who earns which fee and what to ask before signing.

When merchants compare payment offers, the words acquirer, processor, gateway and PSP are often used as if they meant the same thing. They do not. The acquirer vs processor question matters because the two carry different roles, contracts and liabilities: one is responsible to the card scheme for your business, the other moves the data. Knowing who is who helps you read a pricing sheet, understand where a decline or a chargeback comes from and see what actually changes when you switch providers.

This guide explains how card acquiring works step by step, what an acquirer and a processor do, how fees are split and how payment facilitators and PSPs fit into the picture. It is informational: Nominal hub is a catalog, not a payment provider or intermediary.

The four-party model

Visa and Mastercard payments follow the so-called four-party model:

  • Cardholder — the customer who pays.
  • Issuer — the bank or institution that issued the card, approves or declines each payment and bills the cardholder.
  • Merchant — the business that sells goods or services.
  • Acquirer — the scheme member that signs the merchant (directly or through intermediaries), accepts card payments on its behalf and pays it out.

The card scheme (Visa, Mastercard and others) sits in the middle: it sets the rules, routes messages between acquirers and issuers and runs clearing between its members. Three-party or closed-loop schemes, such as American Express in most markets, act as issuer and acquirer themselves, which is why acceptance of those cards is often contracted separately.

What an acquirer does

An acquirer (acquiring bank or licensed acquiring institution) is the party that holds the scheme licence to acquire. In practice it:

  • underwrites the merchant — checks the business model, ownership, licences and risk, assigns a merchant category code (MCC) and a merchant ID (MID);
  • is liable to the scheme for the merchant: if the merchant disappears with unfulfilled orders or cannot cover refunds and chargebacks, the acquirer pays;
  • receives settlement from the scheme and pays the merchant net of fees, sometimes holding a rolling reserve as security;
  • manages disputes — receives chargebacks from issuers and passes them to the merchant with a deadline to respond;
  • monitors ratios of fraud and disputes, because the schemes run monitoring programmes for acquirers whose merchants exceed thresholds.

If you are looking for direct relationships, see acquiring banks. Rolling reserves and how they affect cash flow are explained in rolling reserves and deposits.

What a processor does

A processor is the technology that moves and stores transaction data. There are two main roles:

  • Acquirer processor (merchant-side) — receives the authorization request from the merchant's gateway or terminal, formats it in the scheme's message standard, sends it to the network, returns the response and prepares clearing files. Many acquirers outsource this to a third-party processor; large acquirers run their own.
  • Issuer processor (card-side) — authorizes transactions on behalf of the issuer, manages card accounts, limits and tokenisation.

The processor does not normally carry the scheme liability for the merchant. It is a service provider to the acquirer or issuer. That is the core of acquirer vs processor: the acquirer owns the risk and the scheme relationship, the processor owns the plumbing.

Acquirer, processor, gateway and PSP compared

RoleWhat it doesHolds scheme liability for the merchantTypical contract with the merchant
AcquirerUnderwrites, settles, handles chargebacksYesMerchant agreement, MID
ProcessorRoutes authorization and clearing dataNo (service provider to the acquirer)Usually none, or technical only
GatewayCollects card data on checkout, tokenises it, sends it to the processorNoAPI or plugin agreement
PSP / payment facilitatorBundles gateway, acquiring and extra methods; onboards sub-merchantsShared: the acquirer stays liable to the scheme, the PSP to the acquirerOne contract for everything

The difference between gateways, aggregators and PSPs is covered in detail in payment aggregator vs PSP vs gateway.

How a card payment moves: authorization, clearing, settlement

1. Authorization (seconds). The customer enters card details or taps a wallet such as Apple Pay. The gateway sends the request to the acquirer processor, which passes it through the scheme network to the issuer. The issuer checks balance or credit line, fraud signals and, where required, the result of customer authentication (3-D Secure). It answers approve or decline with a reason code, and the answer travels back the same way.

2. Clearing (usually the same or next day). Approved and captured transactions are sent by the acquirer to the scheme in batches. The scheme calculates what each issuer owes each acquirer, including interchange.

3. Settlement (commonly one to a few business days). Funds move from issuers to acquirers through the scheme's settlement banks, and the acquirer pays the merchant according to the agreed schedule, minus fees and any reserve. A refund follows the same clearing path in the other direction.

This is why "approved" does not mean "money on your account": authorization reserves funds on the card, settlement moves them. The states between the two are explained in order, payment and settlement states.

Who earns which fee

The merchant discount rate (MDR) you pay is made of three layers:

  • Interchange — paid by the acquirer to the issuer. Set by the schemes and, in some regions, capped by law. In the European Economic Area, Regulation (EU) 2015/751 caps interchange for consumer cards at 0.2% of the transaction value for debit and 0.3% for credit.
  • Scheme fees — charged by Visa, Mastercard and others to both acquirers and issuers for network services.
  • Acquirer markup — the acquirer's (and, if present, the PSP's) margin, often combined with a fixed per-transaction fee and fees for chargebacks, refunds or currency conversion.

With blended pricing you see one rate per transaction type. With interchange++ (IC++) you see interchange and scheme fees passed through at cost plus a stated markup. IC++ is more transparent but harder to forecast; blended is simpler but can hide expensive card mixes. How to compare offers in practice is covered in how to calculate the effective payment cost.

Chargebacks and liability

A chargeback starts at the issuer, when the cardholder disputes a payment. The issuer sends it through the scheme to the acquirer, the acquirer debits the merchant and asks for evidence. If the merchant cannot pay, the acquirer still owes the money to the scheme — which is why acquirers are strict about high-risk business models and ask for reserves.

Customer authentication changes who bears fraud losses: when a transaction is authenticated with 3-D Secure, liability for most fraud-related chargebacks generally shifts from the merchant to the issuer. Disputes about goods not received or not as described stay with the merchant. The difference between refunds, reversals, disputes and chargebacks is explained in refund vs reversal vs chargeback; tools that help are listed under chargeback management.

Where PSPs and payment facilitators fit

Most small and mid-sized merchants never sign with an acquirer directly. They use a PSP that operates as a payment facilitator (PayFac) or a registered agent of one or more acquirers:

  • the PSP has a master merchant agreement with the acquirer and onboards sub-merchants under it;
  • onboarding is faster, because the PSP runs KYB itself under the acquirer's rules;
  • the acquirer remains liable to the scheme, and the PSP is liable to the acquirer for its sub-merchants;
  • pricing includes the PSP's margin, and the PSP can move you between acquirers behind the scenes.

PSPs that connect several acquirers and route between them are listed in aggregators and cascading; card-focused providers are in card acquiring and gateways. Companies that want to issue cards rather than accept them need a different partner: a BIN sponsor or BaaS provider.

Direct acquirer or PSP?

A direct acquiring contract usually makes sense when volume is large and stable, the business model is simple to underwrite and you have a team to run integration, reconciliation and disputes. A PSP makes sense when you need to launch quickly, accept many local methods besides cards or sell in several countries. Many merchants end up with both: a direct acquirer in the main market and a PSP for the rest.

Before signing, ask:

  • Who is the acquirer of record, in which country, and which MCC will be used?
  • Domestic or cross-border acquiring for your main customer countries (it affects approval rates and interchange)?
  • Pricing model (blended or IC++), fixed fees, chargeback and refund fees, FX margin.
  • Settlement schedule, currency and rolling reserve terms.
  • 3-D Secure set-up, tokenisation and wallet support.
  • Dispute process: deadlines, evidence format, alerts.
  • What documents underwriting requires — see merchant onboarding: KYB and KYC evidence.

To compare providers, browse card acquiring and acquiring banks by country, or post a request describing your business, volume and GEO.

FAQ

What is the difference between an acquirer and a processor? The acquirer is the scheme member that signs the merchant, settles funds and is liable for chargebacks and fraud. The processor is the technology that routes authorization and clearing messages on the acquirer's behalf and normally carries no scheme liability for the merchant.

Is a PSP an acquirer? Sometimes. Some PSPs hold their own acquiring licence and scheme membership; many others work as payment facilitators or agents on top of one or more acquiring banks. Ask who the acquirer of record is.

Who sets interchange fees? The card schemes set interchange rates, and regulators cap them in some regions — for example, in the EEA consumer debit interchange is capped at 0.2% and credit at 0.3%.

Why can a payment be approved but not settled? Authorization only reserves funds on the card. Money moves after capture, clearing and settlement, which take from one to several business days; an authorization that is never captured expires.

Who pays when a chargeback is lost? The merchant, through the acquirer. If the merchant cannot pay, the acquirer covers the loss to the scheme, which is why acquirers apply reserves and monitor dispute ratios.

Sources

  1. 1.Regulation (EU) 2015/751 on interchange fees for card-based payment transactions
  2. 2.Visa — Rules and policy
  3. 3.Mastercard — Rules

Comments · 0

No comments yet — be the first.

Log in · log in to leave a comment.