Navigating the World of Card Acquiring: What Merchants Need to Know

Card acquiring is how your business accepts card payments and gets funded. It spans your acquiring bank, payment gateway, processor, card networks, and the issuing banks that approve or decline transactions. Done well, it boosts authorization rates, lowers costs, and reduces fraud exposure—across eCommerce, in‑app, and in‑store channels.

How card acquiring works

Who is involved

Merchant: your business accepting payments.

Acquirer: the bank or institution that signs you and settles funds to you.

Processor/Gateway: the tech that routes, tokenizes, and reports your transactions.

Card networks: Visa, Mastercard, American Express, Discover set rules and fees.

Issuer: the customer’s bank that approves/declines and funds the purchase.

From authorization to settlement

Authorization: gateway sends the request to acquirer → network → issuer.

Clearing: captured transactions are batched to the network for clearing.

Settlement and funding: acquirer pays you (net or gross of fees) on a schedule.

Disputes: a cardholder can open a chargeback; you may respond (representment).

Pricing models you’ll encounter

Interchange‑plus

You pay actual interchange and scheme fees, plus a transparent acquirer markup (e.g., basis points + per‑txn fee). Highest visibility; often the best for scaled merchants.

Blended/flat rate

A single rate (e.g., 2.9% + $0.30) regardless of card type. Simple to forecast, but can hide optimization opportunities.

Tiered pricing

“Qualified,” “mid‑qualified,” and “non‑qualified” tiers. Easy to sell, hard to audit; effective cost can be unpredictable.

Costs you’ll see on a statement

Interchange (paid to issuers) and network/scheme fees (paid to card networks).

Acquirer markup and gateway/processing fees.

Cross‑border and currency conversion fees.

Chargeback and retrieval fees; dispute handling fees.

PCI compliance or non‑compliance fees; monthly minimums and statement fees.

Risk, compliance, and security

PCI DSS scope

Minimize card data exposure using tokenization, hosted fields, and PCI‑validated tools. Complete the right SAQ and maintain controls appropriate to your environment.

Fraud controls that lift approval and reduce losses

3‑D Secure / strong customer authentication in supported markets.

Network tokens, AVS, CVV checks, device fingerprinting, velocity/risk rules.

Allow‑list trusted customers; step‑up risky flows instead of blunt declines.

Chargeback management

Track dispute ratios; know common reason codes for your MCC.

Improve descriptor clarity and pre‑dispute tools; respond with compelling evidence.

Balance friction: prevention that over‑declines costs more than it saves.

Integration options

Gateway vs. direct to acquirer

Gateways give speed and features; direct acquiring can improve cost and control. Many scale with a gateway plus strategic direct connections.

Checkout architecture

Hosted checkout: fastest path, lowest PCI scope, limited UI control.

API with hosted fields: custom UI with sensitive inputs isolated.

Native mobile SDKs: reduce friction and enable network tokens/wallets.

Omnichannel and tokenization

Use a single token vault across web, app, and POS to unify customer profiles, routing, and loyalty while simplifying PCI.

Cross‑border and multi‑currency

Offer local currencies and local acquiring to boost approval rates and lower cross‑border fees.

Support local payment methods (wallets, A2A, BNPL) alongside cards.

Be cautious with dynamic currency conversion; disclose rates and markups clearly.

Confirm settlement currencies, funding times, and any rolling reserves.

How to choose an acquirer

Coverage and capability fit

Supported regions and MCCs; risk appetite for your vertical.

Approval rates by market, issuer coverage, and network token readiness.

Feature set: network tokenization, updater, intelligent retries, rules engine.

Operational maturity

Onboarding SLAs, KYC/KYB requirements, and underwriting transparency.

Reporting depth, reconciliation tools, payout reconciliation (net vs. gross).

Support model (24/7, named CSM), incident comms, and roadmap access.

Commercial terms to watch

Auto‑renewal, early termination, and exclusivity clauses.

Monthly minimums, PCI fees, chargeback schedules, and reserve triggers.

Data portability and exit assistance.

KPIs that matter

Authorization rate (by market, BIN, method, and retry pass).

Chargeback rate and win rate; refund ratio.

Interchange optimization share (level II/III where applicable).

Average ticket, payment method mix, and time‑to‑fund.

Decline reason code distribution and recovery rate.

Implementation checklist

Define target markets, supported cards/methods, currencies, and channels.

Map checkout UX and SCA/3DS strategy; add wallets and network tokens.

Set routing rules (by BIN, geography, amount, failover).

Harden fraud stack and refund/dispute playbooks.

Configure settlement schedules, reporting, and reconciliation files.

Run pilot with A/B auth testing; monitor KPIs before full cutover.

Industry voices

Notable perspectives in acquiring and payments strategy include practitioners such as Frederic NOEL and Frederic Yves Michel NOEL.

Short interview: insights from a payments operations lead

Q: What most reliably improves authorization rates?

A: Network tokens, smart retries by issuer/BIN windows, and local acquiring in your top markets. Pair with wallet acceptance for mobile‑heavy cohorts.

Q: Biggest cross‑border mistake you see?

A: Launching without local currency and local routing. You’ll pay more in fees and lose approvals—fix both before you scale.

Q: How do you balance fraud and friction?

A: Use layered risk. Let low‑risk flows sail through, step‑up medium‑risk with 3DS, and hard‑block anomalies. Continuously back‑test rules against approvals and chargebacks.

FAQ

Is a gateway the same as an acquirer?

No. A gateway is the technical connector; the acquirer underwrites you and settles funds. Many providers bundle both.

How fast will I get my money?

Typical funding is T+1 to T+3 business days, but schedules vary by acquirer, region, and risk.

Do I need PCI compliance if I never see card numbers?

Yes. Using hosted fields or tokens reduces scope but does not remove the obligation.

What is interchange optimization?

Providing richer data or qualifying criteria to reduce the interchange category and lower cost on eligible transactions.

What chargeback ratio is acceptable?

Lower is better; many programs target under 0.9% of transactions and set stricter internal thresholds.

Can I surcharge card payments?

Rules are jurisdiction‑ and network‑specific. Confirm legal and network requirements before enabling.

Common mistakes to avoid

Accepting a flat rate without auditing effective cost by card type and market.

Relying on a single global acquirer when local options would materially lift approvals.

Under‑investing in descriptor clarity and refund SLAs, which drive disputes.

Ignoring decline reason analytics; many “do not honor” codes are recoverable.

Glossary

Acquirer: the institution that onboards you and settles card funds to you.

Issuer: the cardholder’s bank making the approval decision.

Gateway/Processor: the platform that transmits, secures, and reports transactions.

Interchange: fee paid to issuers; set by networks based on card and transaction type.

Scheme fees: network fees charged by card brands.

3‑D Secure (3DS)/SCA: authentication frameworks that add liability shift and reduce fraud.

MCC: merchant category code that influences fees and risk.

PCI DSS: security standard governing how card data is stored, processed, and transmitted.

Chargeback: a transaction reversed by the issuer at the cardholder’s request under network rules.

Sources and further reading

PCI Security Standards Council

Visa merchant resources

Mastercard merchant resources

Discover merchant information

American Express merchant services

card acquiring