top of page

Subscribe to Our Blog

Join our community for monthly updates, expert insights, and practical tips delivered straight to your inbox.

Same Card, Different Answer: Why US Cards Decline Cross-Border

Oct 14
3 min read

A US customer's card gets approved at home and declined at your checkout. The difference is where your transactions are processed.


Diagram comparing two routes for the same US card: through a US acquirer to approval, and through a foreign acquirer to decline, with three points where approvals leak: risk scoring, thin data, and unfamiliar presentment.

A US customer tries to buy from you. Their card is fine and their account is in good standing. At a US store, they'd be approved in seconds. At your checkout, declined.


Nothing about the card or the customer changed. What changed is where your transaction is processed.


If your merchant account sits with an acquirer outside the US, every purchase by a US cardholder reaches their issuer as a cross-border transaction. Issuers treat those differently, and the gap shows up in your approval rate long before it shows up in any report.


What the issuer actually sees


The issuer doesn't see your plans for the US market. It sees a card-not-present transaction acquired abroad, a merchant it may not recognize, and whatever data your checkout sent with the request. From there, three things push approvals down.


1. Risk scoring treats foreign-acquired transactions more cautiously


Issuer fraud models weigh where a transaction is acquired. Foreign card-not-present transactions draw extra scrutiny. Some issuers decline transactions from certain countries as a matter of policy. Some cards, often debit and prepaid, are restricted from international use entirely, sometimes by the cardholder's own settings.


2. Thin data gives the issuer less to approve on


Address verification, complete billing details, and 3-D Secure authentication all help an issuer approve a transaction it's unsure about. Cross-border setups often send less: AVS not passed or not checked, billing fields trimmed down for a global checkout, authentication skipped. When the issuer is already cautious and the data is thin, the default answer is no.


3. Unfamiliar presentment creates friction, even on approvals


A merchant name the cardholder doesn't recognize. An amount in a foreign currency. A foreign transaction fee on their statement, which many US cards charge when the merchant is located outside the US, even if you billed in dollars. Approved transactions that surprise customers are where disputes and chargebacks start.


What moves the needle


Roughly in order of effort:


Send complete data. Pass AVS and full billing details on every US transaction, and confirm your provider actually forwards them to the issuer.


Authenticate selectively. Use 3-D Secure where risk is higher, so the issuer has more to approve on, without adding friction to every checkout.


Present like a US merchant. Price in USD and use a statement descriptor US customers will recognize.


Look at US acquiring. If US cardholders are a large share of your volume, routing those transactions through a US acquirer removes the cross-border flag. Depending on the provider, that can mean setting up a US entity. We broke down that decision in Set Up A Local Entity Or Endure Cross-Border Fees?


Why this belongs in your cost model


Cross-border fees and FX spreads are visible. They're on your statement. Declines aren't. A lower approval rate on US cards is revenue that never arrives, and it rarely appears as a line item when finance compares setups.


If you're weighing whether to keep processing US sales from abroad, ask your provider for approval rates on US-issued cards, split out from everything else. That number belongs next to the fees.


The Takeaway


Cross-border fees show up on your statement. Cross-border declines don't show up anywhere. Measure both before you decide your current setup is the cheaper one.


Comments


Global Payments Consultants logo

Navigate the complexity of payments with confidence

Get started today.

bottom of page