You enter the card details, press the button, and get a single unhelpful line back: payment declined. The money is in the account. The card is not expired. Nothing is wrong with it.
This is one of the most common friction points in buying anything digital from a seller in another country, and it is almost never a fault. It is a risk model reaching a decision, in about forty milliseconds, based on inputs that have little to do with you and everything to do with what the payment looks like from the outside. Once you know which inputs those are, clearing it takes a few minutes rather than an afternoon.
Who actually says no
Three parties can stop a card payment, and they are worth keeping separate because only one of them is usually responsible.
The issuer — the bank that gave you the card — makes the final call and issues the vast majority of declines. It holds your history, your balance, your spending pattern and its own fraud rules, and its answer is the one that counts.
The merchant's payment company can block a payment before it ever reaches your bank, using its own screening. This is less common and usually produces a different kind of message.
The seller cannot decline anything and cannot see why anyone else did. What arrives at their end is a response code: approved, or not, with a reason field that is frequently the maddeningly generic "do not honour". That phrase means the issuer said no and declined to say more. Asking the seller to look into it is asking them to read a page they were never sent.
The five things the model is reacting to
Put an annual subscription payment to a foreign digital seller through a fraud model and it lights up on five separate axes at once. Individually, none is alarming. Together they describe a pattern that genuinely does correlate with card fraud, which is why the model exists.
| Input | What your payment looks like | Why it raises the score |
|---|---|---|
| Merchant country | Not your own | Cross-border fraud rates run higher than domestic |
| Merchant history | You have never paid them before | No pattern to compare against |
| Card presence | Card not present, entered online | The weakest form of proof it was you |
| Category | Digital service, delivered instantly | Nothing to recover if the payment was stolen |
| Amount shape | One larger charge, unlike your usual spend | Annual sums sit outside a monthly habit |
Nothing about your payment is unusual to you. All five things about it are unusual to the model. That gap is the entire problem, and every fix below is really a way of closing it.
Worth noting: paying annually rather than monthly makes the fifth input worse on its own. That is not a reason to pay monthly, but it does explain why the once-a-year charge is the one that trips and the small recurring ones never did.
Soft declines and hard declines
This distinction decides whether trying again is sensible or actively counterproductive, and almost nobody outside payments knows it exists.
A soft decline is temporary and conditional. The issuer is saying "not like this" rather than "not at all" — additional authentication is wanted, a limit was momentarily hit, or the model wants a second look. Soft declines are meant to be retried once something changes, and the great majority of foreign digital declines are of this type.
A hard decline is a settled answer. The card is reported lost or stolen, the account is closed, the card is blocked for online use, or an international block is switched on. Nothing about the attempt can change that answer, and no number of retries will.
You cannot see which one you got from the seller's error message, but you can infer it. If your banking app pinged you about the attempt, or a limit or verification message appeared, treat it as soft. If the app is silent and every attempt fails identically and instantly, assume hard and go straight to the bank.
The app prompt you must not dismiss
The most common single cause of a failed foreign purchase is an authentication step that was offered and never completed.
Modern card rules push a lot of online payments through a verification step: the checkout hands you to your bank for a moment, and you approve the payment in the banking app, by biometric or by a code. If that step is not completed, the payment fails, and the message the checkout shows you is often just "declined" with no mention of the step at all.
Three things break it routinely. Notifications are switched off for the banking app, so the prompt never surfaces. The app is not installed on the phone you are holding. Or a pop-up blocker or an over-eager privacy extension kills the verification window before it renders.
So before anything else: unlock your phone, open the banking app manually rather than waiting for a notification, and look for a pending approval. On a good number of failed payments it is sitting right there, waiting, and approving it is the whole fix.
Address checks across borders
Some checkouts verify your billing address against what your bank holds. The check was designed around a single country's address format, and it degrades badly the moment two countries are involved.
In practice, what usually gets compared is the numeric part of your street address and your postcode. Formats that a human reads without difficulty — spaces in a postcode, a county line, an apartment number written before rather than after the street — can produce a partial match, and a strict merchant treats a partial match as a fail.
The fix is unglamorous: enter the address exactly as your bank has it, character for character, including the spacing of the postcode. Not the address you would write on a letter. The one on your statement. If you have moved recently and never updated the bank, that mismatch alone will fail every payment you make until you fix it at the bank's end.
Why retrying makes it worse
The instinct after a decline is to press the button again, and then again with a different card, and then again with the first card. This is the worst possible sequence.
Repeated attempts against the same merchant in a short window is itself a classic fraud signature — it is exactly what someone testing stolen card numbers does. The model sees a pattern it is specifically trained to stop, and the score climbs with each attempt. Meanwhile each failed try can leave its own temporary hold, so your available balance quietly shrinks while you work.
The rule: never retry without changing something first. Approve the prompt, correct the address, notify the bank, switch to a wallet, or wait. One attempt per change, and no more than two changes in a sitting. If you are three attempts deep with nothing altered, stop and go to the bank.
The order to work through it
- Check the banking app for a pending approval. Thirty seconds, and it resolves a large share of cases on its own.
- Re-enter the billing address as the bank holds it. Postcode spacing included, and check the expiry and security code while you are there.
- Tell the bank the charge is expected. Most apps now have a button for exactly this. Where they do not, a two-minute call gets the next attempt whitelisted. Say the amount, the currency and that it is an international online purchase you are making on purpose.
- Wait half an hour, then try once. Some blocks lift on a timer rather than instantly, and an immediate retry after a call often fails for that reason alone.
- Switch to a wallet. The same card presented through Apple Pay or Google Pay carries device-level proof that the cardholder authorised it, which clears a whole category of soft declines. The difference is set out in paying by card versus paying by wallet.
- Try a different card, once. A second issuer is a genuinely different decision-maker. If the first card is hard-blocked this is faster than arguing with it.
- Consider a route with no issuer in it. PayPal moves the decision to a different set of rules, and cryptocurrency removes the issuer from the payment entirely. Both are described on the payment methods page, and the crypto trade-off — no decline problem, and no way back either — is weighed in the piece on paying in crypto.
Holds that look like double charges
After a run of failed attempts, people frequently open their banking app and find two or three copies of the same amount sitting there. It looks like the payment went through repeatedly. It almost never did.
An authorisation reserves an amount without taking it. If the payment then fails or is abandoned, the reservation is not always released immediately — it simply expires, and until it does it shows on your balance looking identical to a real charge. Three to seven days is the usual range, and it can stretch further on some issuers.
The distinguishing detail is the word pending, or the fact that the line has not yet reached your statement proper. A real charge settles and stays. A hold disappears without anyone doing anything.
If a week has passed and both lines have settled, then you have a genuine duplicate and it needs to be raised — with the payment reference for each, not a description of them. What to include is set out in what to send support so a payment problem is solved in one message, and the routes back are compared in refund, chargeback or goodwill credit.
One last thing worth saying plainly: a decline costs you nothing and delays you by minutes. Our plans are $69, $97 and $137 for twelve months, and the price does not move because a first attempt failed. If you get stuck on any of the steps above, the desk on the contact page will tell you which route tends to clear from your country — and once it does clear, what should arrive is described in what happens in the ten minutes after you pay.
