What payment acquirers do across borders and currencies
A payment acquirer is the bank or service that sits between you (the merchant) and the customer's bank when a card payment happens. When your customer is in another country or paying in a different currency, the acquirer has to solve three problems at once: convert the money, route it through the right banking networks, and make sure both banks accept the transaction.
The acquirer doesn't just pass the payment straight through. It holds the transaction, checks it against fraud rules that vary by country, converts currency if needed, and sends it to the customer's bank through the correct network for that region. If the customer is in Brazil paying in Brazilian real but your business is in the US, the acquirer figures out the exchange rate, finds the right Brazilian bank connection, and makes sure the transaction follows Brazilian payment rules.
Most acquirers handle this by partnering with local banks in each region they operate in, rather than trying to connect to every bank in the world themselves. A US acquirer might own or partner with a bank in Mexico, another in Canada, and another in the UK. Each partnership lets them accept cards issued in that country and route them correctly.
Key Takeaways
- Payment acquirers use local bank partnerships in each region so they can accept cards issued there and route transactions through the correct networks.
- Currency conversion happens at the acquirer level, and the exchange rate you see depends on when the acquirer converts the money, not when the customer's bank does.
- Different regions use different card networks and fraud rules—Visa and Mastercard work almost everywhere, but some countries have their own networks or require extra verification steps.
- The acquirer holds the transaction for a moment to check it against fraud rules specific to that country before sending it to the customer's bank.
- Settlement (when money actually lands in your account) can take longer for cross-border payments because multiple banks have to confirm the transaction.
How acquirers route transactions through regional networks
Every country has a card network—the system that moves money from one bank to another. Visa and Mastercard operate globally, but they don't own the banks. Instead, they set the rules and let local banks join their network. When a customer in Japan uses a Visa card, that transaction goes through Japan's banking system first, then to the Visa network, then to your acquirer's bank.
Some regions have their own networks that work alongside or instead of Visa and Mastercard. China has UnionPay, Russia has Mir, India has RuPay. An acquirer that wants to accept cards from those countries has to connect to those networks too. If you're a global merchant and your acquirer doesn't support UnionPay, you'll reject every customer paying with a Chinese bank card—even if they have a Visa card from that bank, because the card might route through UnionPay first.
The acquirer maintains these connections by having staff or partners in each region who understand local banking rules and can troubleshoot when a transaction gets stuck. A payment might fail because the customer's bank doesn't recognize the merchant category code your acquirer assigned you, or because the transaction amount triggers a rule specific to that country. The acquirer's local team knows which rule it is and how to fix it.
Currency conversion and exchange rates
When a customer in euros pays your US business, someone has to convert euros to dollars. The acquirer does this conversion, not the customer's bank and not your bank. The acquirer buys the euros from the customer's bank at one rate and sells the dollars to your bank at another rate—and keeps the difference as part of their fee.
The exchange rate the acquirer uses is usually close to the mid-market rate (the real rate banks trade at), but not exactly. Most acquirers add 1 to 3 percent on top of the mid-market rate. Some acquirers let you choose when the conversion happens: immediately when the transaction is authorized, or later when it settles. If you wait to convert, you might get a better rate if the currency moves in your favor, or a worse one if it moves against you.
The customer never sees this conversion. They see the price in their own currency on your website, their bank charges them in their currency, and your bank deposits dollars in your account. The acquirer handles all the conversion silently in the middle. If you want to know what rate was used, you have to ask your acquirer—it should be in your settlement report, but many acquirers bury it.
Fraud checks that differ by country and region
Before the acquirer sends a transaction to the customer's bank, it runs the transaction against fraud rules. These rules are not the same everywhere. A transaction amount that's normal in one country might be flagged as suspicious in another. A customer in the US buying from a merchant in India might trigger extra checks because the geographic mismatch looks unusual to the fraud system.
Some countries require 3D Secure (also called Strong Customer Authentication or SCA)—a second verification step where the customer has to confirm the payment in their bank's app or with a code sent to their phone. The European Union requires this for most online card payments. Some Asian countries require it for cross-border payments. If your acquirer doesn't support 3D Secure in a region where it's required, the transaction will be declined.
The acquirer also checks whether the customer's bank allows the transaction. Some banks block certain merchant categories (like gambling or adult content) or certain countries. If a customer's bank has a rule against transactions in your country, the acquirer can't override it—the transaction fails at the customer's bank, not at the acquirer.
Settlement timing for cross-border payments
When a customer in your own country pays you, the money usually lands in your account in 1 to 2 business days. Cross-border payments take longer because multiple banks have to confirm the transaction. A payment from Japan to the US might take 3 to 5 business days to settle because the Japanese bank has to confirm it, the Visa network has to confirm it, and your US bank has to confirm it.
During this time, the money is in limbo. The customer's bank has deducted it from their account, but your bank hasn't added it to yours yet. If something goes wrong—the customer disputes the charge, their bank rejects it, or a fraud check fails—the acquirer can still reverse the transaction even after a day or two. This is why cross-border refunds can take longer too.
Some acquirers offer faster settlement for an extra fee, usually by borrowing you the money immediately and collecting it from the customer's bank later. This is called early settlement or advance funding. It costs more but gets money into your account in 24 hours instead of 3 to 5 days.
How acquirers handle currency mismatch and local payment methods
Not every customer in every country uses a card. In some regions, customers prefer bank transfers, digital wallets, or local payment methods. An acquirer that only accepts cards will lose sales in those markets. Larger acquirers solve this by adding local payment methods: iDEAL in the Netherlands, Alipay in China, Pix in Brazil, Giropay in Germany.
When a customer uses a local payment method, the acquirer routes the transaction through that method's network instead of the card networks. The customer's experience is different (they might see their bank's app instead of a card form), but the acquirer handles the conversion and settlement the same way. The money still takes 1 to 5 days to reach your account, and the acquirer still takes a fee.
Some acquirers also let you set prices in multiple currencies. Instead of showing one price in dollars and converting it for every customer, you can show the price in the customer's local currency. The acquirer still converts it behind the scenes, but the customer sees a price that looks local to them. This reduces cart abandonment because customers don't have to do the math themselves.
What happens when a cross-border transaction fails
A cross-border transaction can fail for reasons that don't happen in domestic payments. The customer's bank might not recognize the merchant category code your acquirer assigned you. The transaction amount might exceed the customer's daily limit for international payments. The customer's country might have capital controls that block outgoing payments. The acquirer's connection to that region might be temporarily down.
When a transaction fails, the acquirer sends back an error code. Common codes include "card not permitted for this transaction" (the customer's bank blocked it), "amount exceeds limit" (the customer's bank has a daily cap), and "issuer not available" (the customer's bank is temporarily offline). Your acquirer should tell you which code was returned so you can tell the customer what went wrong.
Some acquirers offer retry logic—they automatically try the transaction again a few hours later if it fails the first time. This helps when the failure is temporary (the customer's bank was offline, or the customer hit their daily limit and it reset). Retry logic doesn't help if the failure is permanent (the customer's bank doesn't allow that merchant category, or the customer doesn't have enough money).
Compliance and regulatory differences across regions
Each country has its own rules about how payments can be processed. The European Union requires strong customer authentication for most online payments. India requires acquirers to store certain data locally. Brazil requires acquirers to report transaction data to the central bank. An acquirer that operates globally has to follow all these rules at once.
This is why global acquirers are expensive and complex. They need lawyers in multiple countries, compliance teams that understand local regulations, and technical infrastructure that can enforce different rules in different regions. A small acquirer that only operates in one country can be much cheaper because it only has to follow one set of rules.
If your acquirer doesn't follow local rules in a region, transactions from that region might be declined, or your acquirer might face fines. This is why some acquirers suddenly stop accepting payments from certain countries—they've decided the regulatory burden is too high.
Frequently Asked Questions
Why does my acquirer charge different fees for different countries?
Acquirers charge more for regions where fraud is higher, where settlement takes longer, or where they have to maintain expensive local partnerships. A payment from the US might cost 2.9 percent, but a payment from a higher-risk country might cost 4 to 5 percent. The acquirer is passing along the cost of their local infrastructure and fraud risk.
Can I see what exchange rate my acquirer used?
Yes, but you have to ask. The exchange rate should be in your settlement report or transaction history. If your acquirer doesn't show it, contact them and ask for a breakdown of the conversion fee. Some acquirers hide it because the markup is high.
What happens if a customer disputes a cross-border payment?
The dispute process is the same as a domestic dispute, but it takes longer because multiple banks are involved. The customer's bank has to contact your acquirer, your acquirer has to contact your bank, and evidence has to travel through multiple systems. Cross-border disputes can take 60 to 90 days instead of 30 to 45 days.
Do I need a different acquirer for each country I sell in?
No. A global acquirer can accept payments from most countries. But if you want to accept local payment methods (like Pix in Brazil or iDEAL in the Netherlands), you might need a local acquirer or a global acquirer that supports those methods. Check your acquirer's documentation for which countries and payment methods they support.
Why was a customer's payment declined if they have enough money?
The customer's bank might have declined it, not your acquirer. Common reasons include: the customer hit their daily limit for international payments, their bank doesn't allow transactions in your country, 3D Secure authentication failed, or the transaction looked fraudulent to their bank's system. Ask your acquirer for the error code, then tell the customer to contact their bank.