An acquirer—formally called an acquiring bank or merchant bank—is the licensed financial institution that accepts card payment risk on behalf of a merchant and settles transaction funds into the merchant's account. Every card payment you accept flows through an acquirer, whether you see it explicitly or not. Understanding how acquirers work is foundational to optimizing costs, improving authorization rates, and building resilient payment infrastructure.
How Acquirer Works
The acquiring relationship sits at the center of the four-party card payment model. Here is the exact sequence from tap to settlement.
Merchant submits transaction
When a customer pays by card, the merchant's point-of-sale or payment gateway sends an authorization request containing the card number, amount, and merchant details to the acquirer.
Acquirer routes to the card network
The acquirer forwards the authorization request to the appropriate card network (Visa, Mastercard, Amex) based on the card BIN. The network acts as the messaging rail between the acquirer and the issuer.
Issuer approves or declines
The card-issuing bank checks the cardholder's available balance, fraud rules, and 3DS verification status, then sends an approve or decline response back through the network to the acquirer.
Acquirer returns the authorization response
The acquirer relays the approval or decline code to the merchant's terminal or gateway, typically within 1–3 seconds. An authorization places a hold on the cardholder's funds but does not yet move money.
Batch settlement
At the end of the business day (or on a configurable schedule), the merchant sends a batch of authorized transactions to the acquirer. The acquirer submits these to the card network for clearing.
Funds deposited into merchant account
After deducting the merchant discount rate (interchange + network fees + acquirer margin), the acquirer deposits net funds into the merchant account. Standard timing is T+1 to T+3 business days.
Why Acquirer Matters
Choosing and configuring your acquiring relationship is one of the highest-leverage decisions in your payments stack. The acquirer you use—and how you use it—directly affects revenue, costs, and operational risk.
Authorization rates vary significantly across acquirers for the same card portfolio. According to industry benchmarks published by the Payments Risk Council, acquirer-side optimizations (BIN routing, retry logic, local acquiring) can lift authorization rates by 3–8 percentage points on cross-border transactions, directly translating to recovered revenue. For a merchant processing $10M per month, a 5-point lift equals $500,000 in recovered sales annually.
The interchange fee is set by the card networks and is non-negotiable, but the acquirer's margin on top of interchange is fully negotiable. The Nilson Report (2024) estimates global acquiring revenue exceeded $42 billion, reflecting how much margin acquirers capture beyond pass-through costs. Enterprise merchants routinely negotiate margins below 0.10% on high-volume interchange-plus contracts.
Local vs. Cross-Border Acquiring
When your acquirer is located in the same country as the cardholder's issuing bank, the transaction is treated as "domestic" by the card network. Domestic transactions carry lower interchange rates and higher approval rates. A UK merchant acquiring through a US bank for UK cardholders pays cross-border fees and sees lower approvals — local acquiring solves both.
Acquirer vs. Payment Processor
These terms are often used interchangeably, but they describe distinct functions. Many vendors bundle both, which creates confusion.
| Dimension | Acquirer | Payment Processor |
|---|---|---|
| Legal entity | Licensed bank (or bank-sponsored) | Technology company (usually) |
| Holds funds | Yes — settles into merchant account | No — routes data only |
| Bears chargeback risk | Yes — primary liability | No (unless also acquiring) |
| Issues merchant ID (MID) | Yes | No |
| Examples | Worldpay (FIS), JPMorgan, Barclaycard | Stripe (also acquirer), Adyen (also acquirer), Braintree |
| Regulated by | Central banks, card network membership rules | Varies — MSB licensing, PCI DSS |
| Revenue source | Merchant discount rate | Processing fees, gateway fees |
Note: Adyen and Stripe are both processor AND acquirer. Legacy setups (e.g., a Shopify merchant using Chase Paymentech) often separate the two roles.
Types of Acquirer
Not all acquiring relationships are structured the same way. Merchants should understand which model they are operating under and its trade-offs.
Direct Acquirer — A licensed bank that onboards merchants individually, issues each merchant a dedicated MID, and underwrites them separately. Offers the best rates at scale but requires more rigorous onboarding (weeks, not minutes).
Payment Facilitator (PayFac) — A company that becomes a registered master merchant and sponsors sub-merchants under its own MID. Sub-merchants get instant onboarding. Examples: Square, Stripe (for small merchants), PayPal. Trade-off: the PayFac sets the terms, can hold funds, and may terminate accounts with limited notice.
Aggregator — Similar to a PayFac; technically, all PayFacs aggregate but the term "aggregator" is often used for marketplace models where multiple sellers transact under one umbrella.
International / Regional Acquirer — Acquirers with licenses in specific geographies who provide local acquiring, enabling domestic interchange rates for merchants selling into those markets. Examples: Adyen (global licenses), Elavon (EU-focused), Payu (emerging markets).
Sponsor Bank — A bank that does not directly interact with merchants but sponsors a payment facilitator's membership in card networks, providing regulatory coverage. Invisible to most merchants.
Best Practices
For Merchants
- Negotiate interchange-plus pricing rather than blended rates once you exceed ~$100K/month in card volume. Blended rates hide your actual cost structure.
- Request local acquiring in your top markets (EU, UK, Australia) if your primary acquirer is US-based. The authorization rate and interchange savings typically outweigh setup costs above $500K/month per region.
- Understand your reserve requirements before signing. Rolling reserves (e.g., 10% held for 180 days) tie up working capital. Negotiate release schedules tied to chargeback performance.
- Monitor your chargeback ratio by MID. Card networks mandate below 1% (Visa) or 1.5% (Mastercard) or you risk losing your merchant account entirely.
- Diversify acquiring relationships if you process over $1M/month. Single-acquirer dependency creates settlement and uptime risk.
For Developers
- Implement acquirer response code handling beyond the binary approve/decline. Soft declines (insufficient funds, do-not-honor) often respond well to smart retries with adjusted parameters.
- Use network tokenization (Visa Token Service, Mastercard MDES) where your acquirer supports it — token-based transactions see 2–4% higher approval rates and reduced fraud.
- Expose the acquirer response code in your internal logging. When debugging authorization failures, raw acquirer codes (not gateway-abstracted messages) are essential for routing decisions.
- Build acquirer failover into your payment orchestration logic. If an acquirer returns a system error, automatic retry through a secondary acquirer should happen within the same checkout session.
- Test with your acquirer's sandbox before launching new payment methods — not just the gateway sandbox. Some payment method behaviors (e.g., 3DS2 flows, local wallets) differ at the acquirer level.
Common Mistakes
Confusing the gateway with the acquirer. The payment gateway is the data pipe; the acquirer is the bank. When you have a dispute or a hold on funds, you need to contact the acquirer, not just the gateway support team.
Accepting blended pricing long-term. Blended rates bundle interchange, network fees, and acquirer margin into one number. This prevents you from seeing where costs actually come from and makes it impossible to negotiate intelligently or optimize routing.
Ignoring chargeback ratios until it's too late. Acquirers can place merchants in monitoring programs (Visa VDMP, Mastercard MATCH) or terminate accounts if chargeback thresholds are breached. These programs can result in being blacklisted from card acceptance industry-wide. Monitor weekly, not monthly.
Assuming all acquirers support all payment methods. Not every acquirer supports every local payment method, card scheme, or 3DS version. Verify compatibility before launching in a new market rather than discovering failures in production.
Neglecting acquirer redundancy. Acquirers experience outages, issuer rejections, and connection failures. Merchants with a single acquirer have no fallback. Any extended downtime translates directly to lost sales with no recovery path.
Acquirer and Tagada
Tagada is a payment orchestration platform, which means it sits above the acquirer layer and connects merchants to multiple acquirers simultaneously. Rather than locking into a single bank's capabilities, Tagada routes each transaction to the optimal acquirer based on card BIN, geography, transaction amount, and real-time authorization performance.
Multi-Acquirer Routing with Tagada
Tagada's routing engine evaluates authorization rate history per acquirer per BIN in real time. When one acquirer is underperforming on a specific card range (e.g., UK debit cards), Tagada shifts volume automatically to the next-best acquirer without any merchant-side intervention. This typically recovers 2–6% of revenue that would otherwise be lost to soft declines.
Merchants using Tagada can add or remove acquirer connections without re-engineering their integration. Acquirer credentials are managed at the platform level, and settlement reporting is unified across all acquirers into a single dashboard — eliminating the operational overhead of reconciling multiple acquirer statements manually.