Acquiring Bank

An acquiring bank contracts for merchant card acceptance and settlement while managing processing, funding, and chargeback exposure.

An acquiring bank, or acquirer, is the merchant-side institution that enables card acceptance and provides or sponsors settlement for the merchant’s card transactions. It connects the merchant and its processor to payment networks and issuers, while assuming contractual and operational responsibilities that differ from those of the cardholder’s bank.

Key Takeaways

  • The acquirer serves the merchant side; the issuer serves the cardholder side.
  • An acquirer can perform processing itself or use processors and other service providers.
  • Authorization, clearing, settlement, merchant funding, refunds, and chargebacks are separate activities.
  • The merchant’s deposit bank is not necessarily its card acquirer.
  • Acquirers underwrite merchants and can use reserves, delayed funding, monitoring, or termination to manage risk.
  • An approved sale can still create refund, fraud, chargeback, compliance, and settlement exposure.

Acquirer vs. Other Payment Participants

ParticipantPrimary relationshipMain role
MerchantCustomer making the saleAccepts the card and provides goods or services
AcquirerMerchant-side payment relationshipSupports acceptance and merchant settlement
Payment ProcessorAcquirer, merchant, issuer, or other participantRoutes messages and processes transaction files
Payment networkIssuers, acquirers, and participantsProvides network rules, routing, clearing, and settlement framework
Card IssuerCardholder-side relationshipIssues or approves the card and makes authorization decisions
Payment GatewayMerchant technology connectionCollects and transmits payment data to processing services

Commercial models vary. A payment facilitator or bundled provider may give a merchant one interface while several legal entities perform the underlying roles.

How a Card Transaction Reaches the Acquirer

  1. The merchant submits transaction data through a terminal, gateway, or processor.
  2. The acquirer or its processor routes an authorization request through the card network.
  3. The issuer approves or declines the transaction.
  4. The merchant captures approved transactions and submits a batch or transaction record.
  5. Clearing calculates obligations among participants.
  6. Settlement occurs under the network and banking arrangements.
  7. The acquirer funds the merchant under the merchant agreement, less fees, reserves, adjustments, or other permitted amounts.
  8. Refunds and disputes can create later debits or credits.

Merchant funding may occur before or after interparty settlement and can be provisional or adjusted under the agreement. Do not use the merchant’s bank credit alone as proof that dispute exposure has ended.

Worked Example: Merchant Settlement and Reserve

Suppose a merchant captures $10,000 of card sales in a daily batch. Under a hypothetical agreement:

  • stated processing and acquiring charges for the batch are $250
  • $300 is placed in a rolling or risk reserve
  • $9,450 is credited to the merchant’s designated bank account

The funding calculation is:

$10,000 gross sales - $250 fees - $300 reserve = $9,450 net funding

Reconciliation itemAmountTreatment
Gross captured sales$10,000Starting transaction total
Processing and acquiring charges-$250Cost under the hypothetical pricing agreement
Reserve movement-$300Restricted or withheld amount, not automatically a fee
Merchant bank credit$9,450Net cash funded for the batch

The merchant should reconcile all four amounts to the processor and acquirer statements. A later $120 refund or chargeback would be a separate adjustment rather than a correction to the original gross-sales figure. Reserve releases should also be tracked separately from new sales and fee refunds.

The example is not a standard price or reserve structure. Actual deductions, funding timing, and accounting presentation depend on the agreement and facts.

What an Acquirer Does

An acquiring relationship can include:

  • merchant due diligence and underwriting
  • payment-network sponsorship or access
  • transaction routing and processing oversight
  • merchant identification and category assignment
  • settlement and merchant funding
  • fee billing and statement production
  • fraud, return, and chargeback monitoring
  • reserves, collateral, delayed funding, or exposure limits
  • data-security and payment-rule oversight
  • reconciliation and exception management

The acquirer does not necessarily operate every technical component. Responsibility should be mapped through contracts rather than inferred from a brand shown on a statement.

Merchant Underwriting and Ongoing Monitoring

An acquirer can face losses if a merchant fails to deliver goods, generates excessive disputes, commits fraud, becomes insolvent, or cannot fund refunds and chargebacks. Initial review can therefore consider ownership, business model, expected volume, average transaction size, fulfillment timing, financial condition, complaint history, and third-party dependencies.

Ongoing monitoring can compare actual activity with the approved profile. Sudden volume increases, unusual refund patterns, high chargebacks, transaction laundering, or delayed delivery can warrant investigation or risk controls.

Fees, Reserves, and Funding

Merchant economics may include:

  • interchange and network charges passed through under the pricing model
  • acquirer or processor markup
  • gateway, terminal, statement, or minimum fees
  • cross-border and currency-conversion charges
  • chargeback, retrieval, or exception fees
  • rolling, fixed, or event-driven reserves
  • delayed settlement or funding holds

Terms such as discount rate or blended rate do not by themselves reveal total cost. Merchants should compare the complete statement and contract, including volume assumptions and exception charges.

Risks and Controls

Acquirer Risks

  • merchant credit and contingent chargeback exposure
  • fraud and transaction-laundering risk
  • operational and reconciliation failures
  • data-security incidents
  • third-party processor or service-provider failure
  • compliance and contractual breaches
  • liquidity demands from settlement timing and merchant funding

Merchant Risks

  • delayed or withheld funding
  • unexpected reserve increases
  • unclear pricing or statement deductions
  • account termination or processing interruption
  • weak dispute support
  • dependence on a gateway, processor, or payment facilitator

How to Evaluate an Acquiring Relationship

  1. Identify the legal acquirer, processor, payment facilitator, and settlement bank.
  2. Map authorization, capture, clearing, funding, refund, and chargeback responsibilities.
  3. Compare gross sales to fees, reserves, adjustments, and net deposits.
  4. Review funding timing, reserve triggers, termination rights, and liability allocation.
  5. Examine security, incident, subcontractor, and business-continuity obligations.
  6. Monitor chargebacks, refunds, fraud, volume changes, and unresolved exceptions.
  7. Confirm who owns merchant support and transaction-level evidence.

Official Resources

This article provides general financial education, not personalized merchant-services, banking, accounting, legal, or compliance advice. Roles and liabilities depend on contracts, network rules, payment structure, facts, and jurisdiction.

FAQs

Is the acquiring bank the merchant's ordinary bank?

Not necessarily. The merchant may receive card settlement into an account at another institution. The acquirer is identified by the card-acceptance and settlement relationship, not merely by where the merchant keeps deposits.

Is an acquiring bank the same as a payment processor?

No. A processor handles transaction messages or files, while an acquirer provides the merchant-side acquiring and settlement relationship. One organization can perform both roles, but the functions remain distinct.
Browse Banking