Back to JournalTravel Cards

Why Your Card Gets Declined Abroad, and What Actually Fixes It

10 min readLast updated: 2026-08-19

By the NorwegianSpark Editorial Team · Written with AI assistance.

A hand holding a fan of euro and dollar banknotes against a teal background

Disclosure: This article may contain affiliate links. If you click and make a purchase, we may earn a commission at no extra cost to you. See our full disclosure.

A card that works perfectly at home refuses a small purchase in another country, and the standard advice — ring the bank before you fly — no longer describes how the system works. Most declines abroad now come from one of two places, and only one of them can be fixed at the counter.

The travel notice is largely obsolete

For a long time, issuers ran a simple geographic rule: a transaction from a country you had not declared looked suspicious. Telling them you were going to Spain suppressed the rule.

That model has been superseded. Issuers and networks now score each authorisation in real time against a much wider set of signals — the merchant, the amount, the transaction type, the device, the sequence of your recent activity. A country flag is one weak input among many, which is why some issuers have quietly removed the travel-notice feature and others keep it mainly because customers expect it.

Set one if your issuer still offers it; it costs nothing. Just do not plan around it, because the more common failure has a different cause entirely.

Strong customer authentication, and the signal problem

The bigger cause is authentication. Under regulation 100 of the Payment Services Regulations 2017, payment service providers must apply strong customer authentication in defined circumstances — including where the payer initiates an electronic payment transaction — and for remote electronic payments the requirement is stricter still: the authentication must include "elements which dynamically link the transaction to a specific amount and a specific payee".

Dynamic linking is the important phrase. It means the authentication cannot be a generic proof that you are you; it has to be tied to this amount and this payee. In practice that arrives as an in-app approval or a one-time code.

Now put that abroad. The step needs to reach you, and reaching you depends on things travel breaks:

  • A one-time code sent by SMS to a number you cannot receive on roaming, or to a home SIM sitting in a drawer.
  • An app approval that needs data, on a phone with no roaming plan and no Wi-Fi at the point of sale.
  • A registered phone number the issuer holds that is no longer the one you carry.

None of that is visible at the till. The terminal simply says declined, and it is easy to conclude the card is blocked when in fact the authentication was never delivered.

Why in-person works and online fails

This is why a card can behave inconsistently within the same hour. A card-present payment authenticates through the chip and your PIN or a device — the elements are there in your hand. A remote or online payment is the one that attracts the dynamic-linking requirement, so it is much more likely to demand a code or an app approval.

Where it failsUsual causeFixable at the counter?
Card-present, small amountRisk scoringSometimes — retry, or use another card
Card-present, large or unusual amountRisk scoring, step-up requestedOnly if you can complete the step
Online or in-app, any amountAuthentication with dynamic linkingNo — needs the code or app approval
Recurring or subscriptionAuthentication or expiry of stored credentialsNo
Cash machineRisk scoring, daily limits, network availabilitySometimes

What to do at the counter, in the ninety seconds you have

A decline is not always final, and the useful responses depend on which of the two causes you are facing.

  • Try the chip rather than contactless. Contactless has its own cumulative limits that trigger a request for a full authentication, and inserting the card is often the step the terminal was asking for.
  • Check your phone before retrying. If an approval request is sitting unread in a banking app, approving it and asking the merchant to run the payment again resolves the transaction cleanly. Retrying blindly does not, and repeated attempts can themselves look like card testing to a risk engine.
  • Retry once, then change something. Two identical failed attempts rarely become a success on the third. Change the card, the network, or the transaction type.
  • Do not let the merchant split the amount into several smaller charges. It looks like a workaround and to a risk engine it looks like exactly the pattern fraud produces.

Cash machines fail for their own reasons

An ATM refusal is a different diagnosis from a retail decline, and it is worth separating because the fixes do not overlap.

Cash withdrawals are usually governed by their own daily limit, distinct from your spending limit and often much lower. Foreign machines may also impose their own per-transaction ceiling, which is the operator's limit rather than your issuer's, and no amount of talking to your bank will lift it — withdrawing a smaller amount will.

Two further points worth knowing before you rely on cash. A credit card withdrawal is normally a cash advance, which means no grace period and frequently a fee, so a debit card is the right instrument at a machine. And when the machine offers to dispense in your home currency, that is dynamic currency conversion in its most expensive form: decline it and take the local currency.

What actually works, in order

Make the authentication reachable. This is the single highest-value preparation. Confirm the phone number your issuer holds is one you will have with you, check that roaming or the banking app over Wi-Fi will work in the country, and test the app before you leave rather than at a petrol station at midnight.

Carry a second card from a different issuer, ideally on a different network. Two cards from the same bank share a risk engine and frequently share a phone number for authentication, so they fail together. Two issuers on two networks are genuinely independent.

Store the issuer's international number somewhere that does not depend on the card working. Written down, or in a note that syncs, not only on a card you may have just had swallowed.

Always choose the local currency. When a foreign terminal offers to charge you in your home currency, that is dynamic currency conversion and the rate is chosen by the merchant's provider, not yours. It does not improve your chances of authorisation — that decision belongs to your issuer either way — and it reliably costs more. We cover why in full.

A declined card abroad is usually not a judgement about your money. It is a message that could not be delivered, or a pattern that did not look like you. The preparation that helps is the kind that keeps the message deliverable.

For the cost side of spending abroad rather than the authorisation side, what your card really charges and no foreign transaction fee cards are the companions. If you are travelling long-term rather than on holiday, credit history does not cross borders explains a related problem people meet later.

Rules differ by jurisdiction. The regulation cited above is the UK implementation; equivalent requirements apply across the EEA under the corresponding EU framework, and neither applies to a purely domestic US transaction.

Frequently Asked Questions

Do I still need to tell my bank I am travelling?

Far less than you used to, and on many issuers not at all. Card networks and issuers now score transactions in real time using signals including the device, the merchant, the amount and your recent history, which makes a manually flagged travel window much less load-bearing than it was. Some issuers have removed the feature entirely. It costs nothing to set one where it still exists, but treating it as the fix for declines abroad is a decade out of date.

What is strong customer authentication and why does it decline my card?

Under regulation 100 of the UK Payment Services Regulations 2017, payment service providers must apply strong customer authentication for certain transactions, and for remote electronic payments the authentication must include elements which dynamically link the transaction to a specific amount and a specific payee. In practice that step often reaches you as a push notification or an SMS code. If you cannot receive it — no roaming, no data, a home-country number you left behind — the payment fails for a reason that has nothing to do with your balance.

Why does an online payment fail abroad when the card works in shops?

Because they are different transaction types with different authentication rules. A card-present payment authenticates through the chip and your PIN or device. A remote or online payment is the one that attracts the dynamic-linking requirement, so it is far more likely to require a code sent to a phone number or an app. That asymmetry is why a card can buy dinner in person and refuse the same restaurant's website ten minutes later.

Does choosing to pay in my home currency help a declining card?

No, and it costs you money. Being offered payment in your own currency at a foreign terminal is dynamic currency conversion, where the merchant's provider does the conversion at a rate it chooses. It does not make the authorisation more likely to succeed, because the authorisation is decided by your issuer either way. Always choose the local currency and let your own card do the conversion.

What should I actually do before travelling?

Make sure you can receive your issuer's authentication step in the country you are going to — that usually means checking roaming or having the banking app working over Wi-Fi, and confirming the phone number the issuer holds is one you will still have. Carry a second card from a different issuer and, ideally, a different network. Know your issuer's international contact number and store it somewhere that does not require the card to work. Those three things fix far more real-world declines than a travel notice ever did.

Related Journal Entries