How Local Acquiring Works
When a customer completes a card payment, the transaction flows from the merchant through an acquirer to the card network and then to the cardholder's issuing bank. In a standard cross-border setup, the acquirer is located in the merchant's home market while the cardholder's issuing bank is abroad. Local acquiring reverses this dynamic: the merchant routes each transaction through an acquirer that is licensed and domiciled in the same country as the cardholder's issuing bank, or at minimum in the merchant's country of sale.
The card network sees the transaction as domestic, applies domestic interchange rates, and the issuing bank scores it under its domestic fraud rules — all of which are more permissive than cross-border rules.
Customer initiates payment
The cardholder enters payment details at checkout. The merchant's payment system captures the card's BIN (Bank Identification Number) and detects the issuing country.
Routing decision
The payment system — either a PSP, orchestrator, or the merchant's own logic — evaluates available acquirers and selects the local acquirer best matched to the cardholder's market and card type. This is where payment routing logic plays a critical role.
Authorization request sent to local acquirer
The transaction is forwarded to the locally licensed acquirer. The acquirer packages the authorization request and submits it to the card network (Visa, Mastercard, etc.).
Card network classifies transaction as domestic
Because both the acquirer and the issuer are in the same scheme region, the network applies domestic interchange rates and domestic processing rules — not cross-border surcharges.
Issuer approves with domestic scoring
The issuing bank receives the authorization request and scores it under its domestic fraud model, which has a lower false-decline rate. Approval is returned to the acquirer, then to the merchant, typically within 1–2 seconds.
Settlement in local currency
Funds settle in the local currency through the acquirer's domestic banking rails. The merchant receives a consolidated payout, often converted to their home currency if needed, without cross-border network surcharges applied during settlement.
Why Local Acquiring Matters
Authorization rate is one of the highest-leverage metrics in payments — a 1 percentage point improvement in approval rate can translate directly to millions in recovered revenue for a mid-sized merchant. Local acquiring is the single most reliable lever for improving authorization rates in international markets.
Research published by Adyen in its Global Revenue Report found that merchants switching from cross-border to local acquiring in markets like Brazil, Mexico, and India saw authorization rate improvements of 5 to 12 percentage points. At scale, even a 3-point improvement on a market processing $50M annually recovers $1.5M in gross revenue that would otherwise be lost to false declines.
On the cost side, cross-border interchange premiums applied by Visa and Mastercard typically range from 0.4% to 1.2% per transaction on top of standard interchange, depending on the card type and region. Local acquiring eliminates these surcharges entirely. For merchants with thin margins in consumer electronics, travel, or subscription businesses, this alone justifies the integration complexity.
A 2024 study by the Merchant Payments Ecosystem (MPE) found that 68% of European merchants processing in Asia-Pacific reported cross-border decline rates exceeding 15%, while merchants with local acquiring in those same markets reported decline rates below 5%. This gap illustrates why large global merchants like Booking.com, Spotify, and Amazon have invested heavily in local acquiring infrastructure.
Authorization Rate Baseline
Industry benchmarks suggest a healthy domestic authorization rate is 85–95% depending on vertical. Cross-border rates for the same merchant typically sit 5–15 points lower. The gap narrows in markets with strong 3DS2 adoption but never fully closes without local acquiring.
Local Acquiring vs. Cross-Border Acquiring
Local and cross-border acquiring represent two different approaches to processing international card transactions. Neither is universally superior — the right choice depends on transaction volume, target markets, and margin sensitivity. Understanding the trade-offs helps merchants prioritize which markets warrant local acquiring investment.
| Dimension | Local Acquiring | Cross-Border Acquiring |
|---|---|---|
| Acquirer location | Same country as cardholder or sale | Merchant's home country |
| Transaction classification | Domestic | International / cross-border |
| Authorization rate | Higher (domestic fraud scoring) | Lower (stricter cross-border rules) |
| Interchange fees | Domestic rates (lower) | International rates + surcharges |
| Setup complexity | Higher (licensing, local entity may be needed) | Lower (single acquirer relationship) |
| Currency settlement | Local currency at domestic rates | FX conversion, often at a premium |
| Regulatory compliance | Must meet local acquiring regulations | Governed by merchant's home market |
| Best for | High-volume markets, thin margins, subscriptions | Low-volume markets, testing new geographies |
For merchants evaluating cross-border payments strategy, a common approach is to use cross-border acquiring as the default and layer local acquiring on top of markets that exceed a volume threshold where the investment pays off within 12 months.
Types of Local Acquiring
Local acquiring is not a single, uniform setup. Merchants access it through several distinct models, each with different cost, control, and complexity profiles.
Direct local acquiring means the merchant holds a direct contract with an acquirer licensed in each target market. This offers the most control over pricing and SLA but requires legal entities, local compliance, and dedicated integrations per market. Only large enterprises with significant volume in each market typically pursue this path.
PSP-facilitated local acquiring is the most common model for growth-stage and mid-market merchants. A payment service provider maintains local acquiring licenses across multiple markets and routes the merchant's transactions through the appropriate local acquirer automatically. The merchant integrates once with the PSP and inherits its local footprint.
Payment orchestration with local acquiring routing allows merchants to connect to multiple acquirers via a single orchestration layer. The orchestrator uses real-time authorization rate data to route each transaction to the best-performing local acquirer for that card type, currency, and market. This model maximises approval rates by introducing competition among acquirers.
PayFac (Payment Facilitator) model lets sub-merchants inherit local acquiring coverage from a PayFac that holds the acquiring relationships. Common in marketplace and platform businesses, this model offloads compliance complexity entirely but reduces pricing transparency.
Best Practices
Deploying local acquiring effectively requires coordination across commercial, technical, and compliance functions. The following practices apply specifically to the roles most involved in implementation.
For Merchants
- Prioritize markets by volume and decline rate. Run a baseline analysis of your current cross-border decline rates by country. Markets with decline rates above 10% and monthly processing above $200K are typically strong candidates for local acquiring investment.
- Negotiate pricing before going live. Local acquiring contracts often include blended rates, minimum volume commitments, or per-transaction floor fees. Request an itemized fee schedule that separates interchange, scheme fees, and acquirer margin.
- Align local acquiring with multi-currency support. Presenting prices in local currency at checkout and settling through a local acquirer in that currency delivers the full conversion benefit. Doing one without the other leaves value on the table.
- Monitor authorization rates post-migration. Set up dashboards that track authorization rates by acquirer, card type, and country from day one. Unexplained drops often signal acquirer-side issues, BIN routing misconfigurations, or fraud rule changes.
- Understand local regulatory obligations. Some markets require merchants to file transaction reports with local tax authorities when using a local acquirer. Engage local legal counsel before going live in regulated markets like Brazil (NFS-e), India (ODR), or Mexico (CFDI).
For Developers
- Build country-to-acquirer routing logic with fallback. Never hard-code a single acquirer per market. Implement a routing table with primary and fallback acquirers, and trigger fallback automatically when the primary returns a network error or a soft decline.
- Handle local acquirer response codes correctly. Response code mappings differ between acquirers even for Visa and Mastercard transactions. Map each acquirer's proprietary codes to your internal decline taxonomy to avoid misclassifying retriable declines as hard declines.
- Test in staging with real BIN ranges. Use acquirer-provided test BIN ranges that reflect the target market's issuing banks. Generic test cards rarely replicate the decline patterns you will encounter with real domestic issuers.
- Log acquirer IDs on every transaction. When you later need to diagnose an authorization rate drop or a settlement discrepancy, the acquirer ID is the most critical field. Ensure it is captured in your transaction ledger and surfaced in your analytics layer.
- Version your routing configuration. Routing rules change — new acquirers go live, existing ones degrade, volume thresholds trigger renegotiated rates. Treat routing config as code: version it, review changes before deployment, and document the business rationale for each rule.
Common Mistakes
Even well-resourced payment teams make avoidable errors when implementing local acquiring. These are the most common failure modes.
Conflating local acquiring with local payment methods. Local acquiring improves card network transaction performance. Local payment methods — iDEAL, PIX, UPI — are entirely separate rails. Merchants sometimes add local payment methods and expect card authorization rates to improve; they will not without local acquiring.
Assuming a single global acquirer provides true local acquiring everywhere. Large global PSPs market "local acquiring" coverage, but the quality varies significantly by market. In some markets, they route through a local banking partner with pass-through economics; in others, they use cross-border acquiring with local currency presentment. Scrutinize the specific acquirer entity and its licensing status in each critical market.
Ignoring the interchange differential during ROI modeling. Merchants often model local acquiring ROI based on authorization rate uplift alone and undercount the interchange savings. In markets like Brazil or Mexico, domestic card interchange rates can be 60–80 basis points lower than international rates. Including this in the model often makes the investment case materially stronger.
Going live without a fallback route. Local acquirers experience outages, card network connectivity issues, and periodic fraud rule changes that temporarily spike decline rates. Without a cross-border fallback, a local acquirer outage blocks all transactions in that market. Always configure at least one fallback path.
Neglecting 3DS2 integration with local acquiring. In markets where 3DS2 is mandatory or strongly preferred by local issuers — most of Europe, Brazil, and parts of APAC — failing to pass enriched 3DS2 authentication data alongside the local acquiring authorization request can negate much of the authorization rate benefit. Local acquiring and 3DS2 are complementary, not mutually exclusive.
Local Acquiring and Tagada
Tagada is a payment orchestration platform that connects merchants to a network of acquirers and routes each transaction to the best-performing option in real time. Local acquiring is one of the core routing strategies the platform supports.
Maximize Local Acquiring with Tagada
Tagada's routing engine uses live authorization rate data, BIN intelligence, and configurable rules to automatically direct transactions to local acquirers in markets where they are available. Merchants gain local acquiring coverage across multiple geographies through a single integration — without managing individual acquirer contracts. When a primary local acquirer declines or returns an error, Tagada automatically retries through the configured fallback acquirer, protecting revenue without any manual intervention.
For merchants scaling internationally, Tagada removes the integration complexity that typically slows local acquiring rollouts. Rather than building and maintaining per-acquirer integrations, engineering teams integrate once and configure routing rules through Tagada's dashboard. New local acquirers are added to the network centrally and become immediately available to all connected merchants.