Merchant Acquiring for Ecommerce: How the Acquiring Layer Actually Works

Merchant acquiring is the licensed financial service that holds your merchant contract, routes card transactions through Visa and Mastercard, and settles money into your account. The acquirer is the entity that actually carries the risk and determines your cost structure. This article covers how acquirers earn, what drives fees inside the discount rate, and how to choose between a direct acquirer, PSP, PayFac, and multi-acquirer setup.

Which model fits your business?

The full breakdown with decision criteria is at the end of this article.

What Is Merchant Acquiring?

The acquirer does three things most people assume someone else handles:

Onboarding and underwriting. The acquirer evaluates your business model and chargeback history, along with industry category and risk classification, before granting a merchant account. This is why high-risk verticals (travel, online gaming, digital goods, subscription businesses) face stricter scrutiny and higher initial deposit requirements.

Transaction routing and settlement. The acquirer submits authorization requests to card networks, receives approval responses, batches cleared transactions, and deposits net proceeds into your account, typically within T+1 to T+3 of the transaction date.

Risk and liability. The acquirer carries the chargeback liability for every transaction processed through your account. If a merchant can’t cover chargebacks or goes out of business mid-dispute, the acquirer is financially responsible.

For teams who want to understand how to accept payments on your website before going deeper into the acquiring layer, the setup decisions start earlier, but the acquiring relationship is what determines the economics and risk profile of the entire stack once you’re processing volume.

Merchant Acquirer vs Payment Processor vs Payment Gateway vs PayFac

These four entities are routinely conflated in technical discussions, even by developers who’ve built on top of them. The payment processor vs payment gateway distinction is one layer of the confusion; the acquirer and PayFac add two more. Understanding who holds what in each model is the prerequisite for every other acquiring decision.

The practical implication: if you’re a merchant who signed with a PSP, you’re a sub-merchant on the PSP’s master merchant account. That’s a reasonable trade at low volume. At scale, it limits your pricing model, dispute control, and ability to optimize approval rates.

How Does a Card Transaction Actually Flow?

Most teams have an approximate mental model of card transactions. The details matter because each step is where fees accumulate and where authorization rates can be influenced. Understanding the flow is the prerequisite for designing any custom acquiring or payment orchestration layer.

Here’s the full sequence for a card-not-present ecommerce transaction:

1. Customer submits payment. The payment gateway tokenizes the card data and forwards an authorization request downstream to the acquirer. Teams who need to understand the full technical scope can read DashDevs’ guide on how to build a payment gateway from scratch.
2. Acquirer submits to the card network. The merchant acquiring platform sends the authorization request to Visa, Mastercard, or Amex, including the merchant category code (MCC), transaction amount, and card BIN data.
3. Card network routes to the issuing bank. Visa or Mastercard routes the request to the bank that issued the customer’s card.
4. Issuing bank makes the authorization decision. The issuer checks available funds, applies fraud scoring, evaluates the 3DS2 authentication result, and returns an approval or decline. Hard declines (e.g., insufficient funds, stolen card) are issuer-level rejections that retrying will not fix. Soft declines (where the issuer or network is temporarily unavailable) can be recovered with retry or failover logic.
5. Response returns downstream. Authorization response passes back through the card network, acquirer, gateway, and merchant. The round-trip typically completes in under two seconds.
6. Clearing. At the end of the day, the merchant (or acquirer on its behalf) batches all approved transactions and submits them for clearing through the card network.
7. Settlement. The issuing bank transfers funds to the acquirer. The acquirer deducts its fees, then credits the net amount to the merchant’s account.

This is how the transaction processing system layer connects to the acquiring relationship. For merchants scaling e-commerce payment processing across borders, steps 2–4 are where routing decisions most affect approval rates, covered in the cross-border section below.

What Does Merchant Acquiring Actually Cost?

Every acquiring fee is built from three layers. Most merchants only see a single blended rate, which hides the structure. Understanding what drives credit card processing costs is how you evaluate whether a rate is actually competitive and where negotiation is possible.

Layer 1: Interchange. Set by the card networks (Visa, Mastercard, Amex) and non-negotiable. Interchange varies by card type (consumer debit vs commercial credit), market (EU interchange is capped by regulation; US rates are substantially higher), and channel (card-present vs card-not-present). Interchange is collected by the issuing bank on each transaction.

Layer 2: Scheme fees. Charged by the card networks for access to their infrastructure. Smaller than interchange but present on every transaction, and published annually in Visa and Mastercard’s fee schedules. Includes authorization fees, service fees, and network access fees.

Layer 3: Acquirer markup. The acquirer’s commercial margin, applied on top of interchange and scheme fees. This is the negotiable component, where pricing models diverge significantly.

Pricing models:

Blended pricing looks simple. At scale, it just means you’re funding someone else’s margin without knowing it.

Most PSPs default to blended pricing, which is appropriate when simplicity is the priority. As monthly card volume grows into seven figures, the delta between blended and IC+ pricing becomes worth quantifying seriously.

Which Acquiring Model Is Right for Your Business?

This is the decision most teams get wrong because they default to the fastest path at launch without modeling what they’ll need at scale. Each model trades control for simplicity differently.

Direct acquirer. A bilateral relationship between the merchant and a licensed acquiring bank. The merchant goes through full underwriting, signs a merchant service agreement, and gets access to IC+ or IC++ pricing and direct settlement. Control is maximum; setup time runs four to twelve weeks (more for high-risk categories). Best for established merchants with consistent transaction volume and the operational capacity to manage the relationship directly.

PSP / aggregator. The PSP holds a master merchant account, and sub-merchants operate under it. Onboarding is fast, sometimes instant for low-risk merchants. Pricing is typically blended. If the PSP freezes or terminates the account, the merchant has limited recourse. Best for early-stage or lower-volume merchants where simplicity outweighs control.

PayFac (payment facilitator). Platforms that need to onboard and pay out sub-merchants register as PayFacs to control the full onboarding and settlement flow. The platform takes on KYC/AML responsibility for its sub-merchants. Our article on how the payment facilitator (PayFac) model works covers the licensing and liability structure in detail, including why it’s not appropriate for merchants who simply want better pricing.

Multi-acquirer orchestration. A routing layer that distributes transactions across multiple direct acquirer relationships in real time, based on geography, card type, transaction cost, and historical approval rates by acquirer. Highest setup complexity; highest potential return on authorization rate and fee optimization. Not a first-move option, but the right architecture for enterprise and multi-regional merchants above a certain volume threshold.

The segment-to-option map at the end of this article translates these models into specific starting recommendations by business type.

Does Your Acquiring Setup Affect Authorization Rates?

Yes, directly. Authorization rate is one of the most consequential metrics in a payment stack and one of the most underoptimized. Three mechanisms in the acquiring setup determine how much headroom you have:

Local acquiring. A card issued in Germany, processed through a local German acquirer, will typically see a higher approval rate than the same card processed cross-border through a UK acquirer. Issuing banks apply stricter fraud rules to foreign-acquirer transactions, particularly for card-not-present ecommerce flows where local issuer behavior patterns are harder to model cross-border. For merchants selling into multiple markets, local acquiring relationships in key geographies improve authorization rates more than most other optimization levers.

Smart routing. Multi-acquirer routing sends each transaction to the acquirer most likely to approve it based on card BIN, card network, currency, transaction amount, and historical approval data by the acquirer. For high-volume merchants with a multi-regional customer base, routing optimization can move authorization rates by several percentage points. The routing logic needs to be dynamic, not a static rule set, because issuer behavior and acquirer performance change over time.

Failover. When the primary acquirer returns a system-unavailable decline rather than a hard decline, a fallback route to a secondary acquirer can recover the transaction without the customer knowing. For cross-border payment processing at an enterprise scale, failover is close to non-negotiable; scheduled maintenance windows and unexpected acquirer downtime costs real revenue.

For the iOL Pay platform, our payment acceptance solution for global hospitality, we designed a multi-method acquiring infrastructure supporting 250+ payment methods across 23,000+ hotels worldwide. The routing logic handles significant diversity in card type, currency, and geographic origin within a single transaction flow, with failover built into the core architecture rather than layered on afterward.

What Should You Verify Before Signing With an Acquirer?

The evaluation criteria for a direct merchant acquiring relationship are different from those for a PSP integration. A merchant service provider selection is partly a commercial decision and partly an engineering one. The criteria missed in diligence are usually the ones that cause operational problems six months after launch.

Watch-outs: acquirers who can’t provide named client references in your vertical are a material risk when entering new markets or high-risk categories. Rolling reserve terms are rarely negotiated proactively, and they should be, before the contract is signed rather than at renewal.

Rolling reserves are always negotiable before signing. Almost never after.

For card-not-present environments, also confirm whether the acquirer supports address verification service (AVS) as part of their fraud tooling stack.

What Does a Production Acquiring Infrastructure Look Like?

We treat acquiring as a product architecture decision, not a vendor selection. The model, fee structure, and routing logic get designed into the system early because refactoring the acquiring layer at scale is significantly more expensive than getting it right in the initial build.

iOL Pay: a global hospitality payment platform

Illusions Online’s payment subsidiary serves 23,000+ hotels worldwide. The client needed global payments, virtual cards, merchant wallets, remittances, and FX consolidated into one platform. We built a multi-method payment acceptance layer supporting 250+ payment methods, with iOL Pay operating as the merchant of record. One-click booking with card tokenization improved conversion directly. Global acquiring integrations eliminated the manual processing overhead hotels had previously absorbed.

Licensed PSP: payment orchestration at scale

One of our PSP clients runs a payment orchestration platform handling 10,000+ payment requests per second. The architecture uses real-time BIN-level routing across multiple acquiring relationships, with automatic failover built into the core layer rather than added on afterward.

MuchBetter: multicurrency e-wallet

An award-winning e-wallet available in 180+ countries, serving 400K+ users and 300+ merchants. The infrastructure handles multi-currency settlement complexity at significant cross-border volume. Different operational profile from hospitality, same underlying principle: the acquiring layer determines what’s possible.

We’ve integrated with 70+ fintech vendors across 15+ years in regulated fintech delivery, including direct acquirer relationships, PSP-layer implementations, and payment orchestration builds. Our fintech integration services cover the full acquiring integration scope: acquirer API integration, reconciliation, dispute workflow, settlement reporting, and ongoing operational support.

For teams building inside a licensed PSP, EMI, or payment institution, this is also where infrastructure for licensed PSPs and EMIs becomes relevant. We’ve used Fintech Core by DashDevs modules to compress the standard acquiring integration timeline for licensed institutions that need to go live without rebuilding the settlement and reconciliation stack from scratch.

Where should you start?

The fastest way to narrow the options is to decide whether you need to own your merchant contract directly or whether aggregated pricing still works at your volume. Everything else follows from that answer.

If you’re evaluating payment processing companies for the first time or reassessing an existing stack, that 18-month question is the right frame.