Why local acquiring lifts approval rates

When a shopper in Germany pays a merchant in the United States with a German card, the issuing bank sees a cross-border transaction. When the same shopper pays the same merchant through an acquirer licensed in Germany, the issuer sees a domestic one. The card, the shopper and the basket are identical. The approval decision often is not.

This post explains why that happens, how large the effect tends to be, and where local acquiring does not help.

Figures in this post are illustrative placeholders drawn from a prototype dataset, not measured results.

What the issuer sees

An authorisation request carries more than an amount and a card number. It includes the acquirer's country, the merchant's location, the merchant category code and a set of data elements that vary by network and region. Issuers feed these into risk models that were largely trained on domestic spending.

A cross-border request arrives with three things working against it:

• Unfamiliar acquirer country. Many issuer models apply a higher baseline risk score to any transaction acquired abroad, regardless of the merchant.
• Thinner data. Some domestic schemes pass extra fields, such as local address verification results or scheme-specific identifiers, that a foreign acquirer cannot send.
• Different routing. A cross-border transaction may travel through an international network even where a domestic scheme exists, which adds a hop and, in some markets, a different rule set.

None of this is a judgement about your business. It is a statistical prior the issuer applies before it has looked at the shopper's history.

How large the effect is

In our illustrative dataset, moving card volume from a cross-border acquirer to a domestic one changed approval rates by market as follows:

All figures are illustrative.

The pattern is more useful than the numbers. Markets with a strong domestic scheme or strict rules on cross-border card use, such as Brazil, tend to show the largest gap. Markets where cards are already widely used across borders, such as the United Kingdom, show a smaller one.

The cost side

Local acquiring often lowers cost as well as raising approvals. Cross-border transactions can carry an extra scheme assessment and a higher interchange rate. Acquiring domestically removes the cross-border assessment in many cases and may qualify for domestic interchange.

That said, you should not assume savings. Check the breakdown line by line. Our post on reading an Interchange++ statement walks through how to do that.

What you need to acquire locally

To acquire in a market, a payment provider needs a licensed entity or a regulated partner there, connections to the local schemes and a settlement path into that country's currency. You, as the merchant, usually need:

1. A merchant account set up in that market, which your provider can often open on your behalf.
2. Accurate business details, including a registered address and a description of what you sell.
3. A decision on settlement currency: settle locally and convert later, or convert at settlement.

With Local Acquiring, International Orders routes each card transaction to the acquiring entity in the shopper's country where one is available, and falls back to cross-border acquiring where it is not. You see which path each payment took in the dashboard and in the payment object.

Where local acquiring does not help

Local acquiring is not a fix for every decline. It does little for:

• Insufficient funds. No routing change makes money appear in the shopper's account.
• Genuine fraud signals. If the issuer has seen this card used fraudulently, the acquirer's location will not change its mind.
• Expired or closed cards. These need card updates, not routing. See Account Updater and Network Tokens.
• Markets where the shopper does not use cards. In some countries most online spending runs through local methods. There the answer is to offer the method, not to acquire cards differently. The payment methods catalogue shows which methods lead in each market.

How to measure it

If you are evaluating local acquiring, run a controlled comparison rather than a before-and-after. Route a share of eligible traffic locally and keep the rest cross-border for a few weeks. Compare approval rates by card type and issuer, not just in aggregate, because a shift in your traffic mix can hide or exaggerate the effect.

Things to hold constant during the test:

• 3-D Secure policy and exemption strategy.
• Retry logic for soft declines.
• The descriptor shown on the shopper's statement.

Acceptance Insights shows approval rates split by acquiring path, so you can read the result without exporting data.

A short checklist

• List your top markets by card volume and note whether you acquire locally in each.
• For each market without local acquiring, estimate the approval gap using your own decline data.
• Check the cost lines for cross-border assessments you could remove.
• Run a split test before moving all traffic.

If you want to see which markets support local acquiring today, the coverage page lists them, or you can talk to our team.