My bank declined the payment although I have funds

Usually the bank's own risk checks, especially on cross-border payments or ones needing extra verification. Contact your bank to approve it, then try again.

We cannot see the bank's reason for declining: that sits with the card issuer. All we see is that the payment did not succeed.

If it still fails after the bank approves it, try another payment method offered at checkout.

Plenty of available credit, yet the payment screen still says declined. It is genuinely frustrating, especially when you are confident the funds are there. The first thing to understand is that a decline like this almost never comes from our side — it comes from the card-issuing bank's own security checks, which can reject a transaction on their own internal criteria regardless of available balance.

This page explains why this happens, walks through the most common causes, and covers what to do to get the transaction through next time — without claiming that any particular bank declines for a specific reason, since each bank's internal rules differ and are not made public.

Why a bank declines a payment despite sufficient funds

The verification system known as 3D Secure, or additional bank verification, exists to reduce the risk of unauthorised transactions. The issuing bank assesses the risk of each transaction from several factors at once — recent spending patterns, the country where the merchant is registered, the device and location used to make the transaction, and how frequently transactions are happening in a short window. If these factors together look unusual against the cardholder's normal behaviour, the bank can decline the transaction outright for safety, even with plenty of available credit.

A travel eSIM purchase tends to carry characteristics that risk-detection systems view as more worth flagging than an ordinary transaction — it is a cross-border digital purchase, the merchant may be registered in a different country from where your card is issued, and it is sometimes the first time you have transacted with this particular provider. Together these factors mean the transaction is more likely to draw extra scrutiny than a routine domestic purchase.

What the extra verification step (3DS) actually is

When paying by card, some banks pop up an extra verification screen — entering an OTP sent by SMS or a banking app, or confirming directly inside the banking app. This step is a security standard set entirely by the issuing bank, not something a merchant or provider like us controls. If this step fails, whether because the code arrives late, is entered incorrectly, or the window times out before it is entered, the transaction is declined automatically.

Common reasons for a decline

1. The bank's risk system flags the transaction as unusual against your normal behaviour
2. The OTP or in-app confirmation timed out before it was completed
3. The card has not been enabled for online or cross-border transactions
4. Several attempts were made back to back in a short time, which the system reads as suspicious
5. Card details entered, such as the expiry date or CVV, do not match what the bank has on file
6. The card is a prepaid or virtual card, and some types carry restrictions with certain merchants that the bank itself sets

What to check with your bank before trying again

Before trying to pay again, calling or chatting with the bank through its own official channel is the most worthwhile step, because only the bank can see the specific reason the transaction was declined in its own system. Worth asking: whether the card is enabled for online and cross-border transactions, whether it has been temporarily locked or restricted because of this attempt, and whether confirming the transaction through the bank's own channel will let it go through next time.

How to retry in a way more likely to succeed

1. 1Confirm with the bank first that nothing is still locked or on holdContact the bank through its own official channel to confirm nothing is still on hold from the previous attempt.
2. 2Wait a short while before trying againRetrying immediately several times in a row can make the system view it as even more suspicious. Leave a couple of minutes before the next attempt.
3. 3Be ready to confirm identity the moment it is requestedHave the banking app open or be ready for an SMS in advance, so the OTP or confirmation can be entered before the window expires.
4. 4If it still fails, try a different card or payment method available to youA different card or payment method that already has cross-border transaction rights tends to have a better chance than repeatedly retrying the same card.

Prepaid, virtual, and corporate cards carry different restrictions

Some prepaid and virtual cards are designed to work only with certain categories of merchant, or carry a lower per-transaction ceiling than an ordinary credit card. These restrictions are set by each bank or card issuer and are not obvious until a decline actually happens. If a card like this is in use, check with the issuer whether it supports cross-border transactions with digital merchants.

Corporate or company-issued cards often carry conditions set by the organisation's own finance department — restricted merchant categories, or a requirement for approval before a non-routine transaction. If a card like this is in use, contacting the organisation's finance team alongside the issuing bank tends to get to the real reason faster.

Do not retry too many times in a short window

If a couple of attempts have already failed, the better move is to pause and contact the bank as described above, rather than continuing to retry hoping one attempt eventually goes through — a pattern of frequent rapid retries is exactly the kind of thing risk-detection systems weigh heavily.

If switching to another payment method still fails

If both the original card after confirming with the bank, and another card or payment method, still fail, contact our team directly so we can check whether there is an unrelated issue on our side, such as a temporary connection glitch during the payment step. What to tell us: the time of each attempt, the exact error message shown if any, and every payment method already tried.

The banking app shows pending even though the system declined

Another point that causes confusion is a banking app still showing an entry as 'pending' even though our payment screen has already reported the transaction as declined. This happens because a transaction has two separate stages. The first is a temporary hold to check that the card works and has enough available credit, which shows up as pending in the banking app immediately. The second is the extra verification step, which can fail afterward, so the transaction never actually completes as a real charge.

A pending entry like this usually disappears on its own within a few business days, since it is only a hold rather than an actual charge. How long it takes to release depends entirely on the issuing bank, not on the merchant or provider's side. If a pending entry stays unusually long, or later turns into a real charge even though our system confirmed the transaction was declined, contact the bank first to ask for the details.

A summary of the order of steps when a payment is declined

• Do not retry repeatedly right away
• Contact the bank through its own official channel to confirm the card's status
• Be ready to receive an OTP or app confirmation before the next attempt
• If it still fails, try another card or payment method available
• If every payment method still fails, contact the team with details of everything already tried

Review the eSIM plans again before retrying payment

Talk to us on LINE if every payment method has failed

Read the message on screen before you start guessing

When a payment is refused, most people press retry before reading anything. The message on screen usually did say something, though. The catch is that these messages are deliberately vague: an issuing bank does not send a detailed reason back to the merchant, because if it did, whoever is holding a stolen card would learn exactly what to change in order to get through. So the screen tells you the transaction was unsuccessful and suggests contacting your bank, which feels like it says nothing. It actually says one important thing — the refusal happened on the bank's side, not at the shop counter.

Telling those two apart changes what you should do next. If the wording mentions the card, a limit, verification, or asks you to contact the issuer, the matter sits with the bank, and hammering retry with the same card over the next few minutes will rarely change the outcome. If instead it mentions a missing field, an incomplete form, or a page that failed to load, that is a front-of-house problem you can fix yourself without calling anyone. The two cases need opposite responses, and guessing wrong at the start costs several wasted rounds.

Who actually says no: the chain behind a single card payment

A single payment does not run straight from the checkout page to your bank. It passes through several hands, and each of them may stop it for its own reasons. The checkout page validates the shape of what you typed, the payment provider applies its own risk signals, the card network carries the request onward, and at the far end the issuing bank makes the final call on whether to approve. Once you picture that chain, it stops being mysterious that a merchant cannot tell you what your bank was thinking.

The trap specific to eSIM buyers: the OTP goes to a number you cannot receive

A great many people buy an eSIM after they have already landed, because that is the moment they notice they have no connection. The result is circular: you need to pay in order to get online, but paying requires a code the bank sends by SMS to your home number — and that home number may have no roaming enabled, or the SIM may already be out of the phone, or the handset may be running a new profile with no link to the old line. The code is genuinely sent. It simply has nowhere to land.

There are only a few workable exits. The first is to switch your verification channel from SMS to the banking app, which runs over the internet — on airport or hotel Wi-Fi that still works normally. The second is to enable roaming on your home line before you leave, even if you never intend to use roaming data, because receiving an SMS still depends on voice-and-text service. The third, and by far the simplest, is to buy and install while you are still at home and every channel is intact.

Buying before departure versus buying once abroad: the risk is not the same

People treat the timing of a purchase as a convenience question, but for payments it shifts the odds meaningfully. At home you have a working phone number, your banking app, a backup card in your wallet, and the ability to phone the bank during business hours. Abroad you may have none of those. The table below sets out how the risk changes and what to arrange in advance.

Small browser conditions that break the verification window

The verification step usually opens a new window or hands you over to the bank's own system for a moment, then returns you to checkout once you pass. That makes it more sensitive to browser settings than people expect. A pop-up blocker can close the bank's window silently. Blocking cross-site cookies can leave the system unable to remember that you already verified. And the in-app browser built into some chat apps handles this back-and-forth poorly.

• Open checkout in the phone's main browser rather than the one that pops up inside a chat app
• Temporarily allow pop-ups for that page, and switch the setting back afterwards
• Disable ad-blocking extensions or the strictest privacy mode just for the payment
• Turn off any VPN during the transaction — an origin country that contradicts the card is an obvious risk signal
• Do not press back or refresh while the bank's page is loading
• Check that the phone's date and time are set automatically — a badly wrong clock disturbs encrypted connections

If the verification window times out halfway

The verification window has a time limit. If you switch to the messages app to copy the code and come back too slowly, the window may already have expired. Sometimes the system says so plainly; sometimes it presents as an ordinary decline, which leads people to conclude the card is faulty when in truth they were a few seconds late.

To reduce the odds, get everything ready before you press confirm: silence distracting notifications, leave the messages app or banking app already open in the background, and do not wander off while waiting. If it has expired, start a fresh transaction rather than refreshing the old page, since the old page may still be holding a dead attempt.

Amount, currency, and cross-border fees

Sometimes a payment succeeds but the amount showing in your banking app differs from the figure at checkout, which reads like an error. The usual explanation is the exchange rate and the issuer's own fees — a matter between you and your bank rather than something the merchant sets. Exactly how it is calculated, and how much, depends on the individual issuer, so the card's own terms are the place to check.

You may also be offered a choice between paying in the local currency or your own. That option does not cause a decline, but it does change the final figure. If the screen appears and you are unsure, read it fully before tapping — choosing wrongly is not damaging, but it makes the statement line differ from what you expected.

Cardholder details that do not line up

Some banks compare what you typed against what is on file for the card — the cardholder name, or elements of the billing address — and may refuse when they do not agree, even with the full limit available. How strict this is varies enormously by issuer and by country: some check closely, some barely at all. There is no single rule that holds for every card.

What you can do is enter what the bank actually holds, not the address where you happen to be staying. If you have recently moved or changed your surname without telling the bank, this is worth checking — and it explains why the same card sails through at one shop and stalls at another, since each merchant checks differently.

Several pending holds appear after several attempts

After several attempts you may see multiple pending lines in the banking app, each for the same amount, which looks alarmingly like being charged repeatedly. In practice an attempt that was not approved does not become a real charge, and the holds release on their own. How long that takes is entirely down to the individual bank, and not something a merchant can speed up.

The right move is to stop attempting for a while and first establish whether a successful order exists at all. If none does, there is no legitimate charge. If one order succeeded and other holds are still sitting there, screenshot them and take the holds up with your bank, while the successful order is something we can help with from our side.

1. 1Stop attempting and check the order statusOpen the inbox you ordered with and look for an order confirmation. If one arrived, the payment went through and there is no need to pay again.
2. 2Switch verification from SMS to the banking appIf you are abroad and codes are not arriving, change the verification channel inside the banking app, or ask the bank whether it supports one.
3. 3Contact the bank and say it is an overseas online merchantGive the date, time and amount attempted so staff can find it quickly, and ask directly which condition blocked it.
4. 4Leave a gap before retryingGive any temporary lock from the earlier attempts time to clear, then try again on a stable connection.
5. 5If it still fails, change to another card or method shown at checkoutThe supported options appear on the checkout page at the time. If every one of them fails, message us with a note of what you have already tried.

When you need connectivity right now and the card keeps failing

The most stressful version is standing in an arrivals hall with no connection while the card is refused again and again. At that moment, change the order of operations: stop trying to force the payment through and get any temporary connection first. Airport, hotel or café Wi-Fi restores access to your banking app, your email and our contact channels, which reopens every other route.

If a travelling companion has a working connection, borrow a hotspot long enough to finish the transaction. That is straightforward and carries no special restriction. Guard one thing only: do not let anyone else type your card details, and never send a full card number to anybody, whatever office they claim to be calling from.

What to keep before you message us

If you do come to us, what shortens the exchange is enough detail for us to find the matching activity: the email address used at checkout, the approximate date and time of the attempts, which plan you were buying, and a screenshot of the refusal message. A screenshot beats a typed description, because there is sometimes a small reference code in a corner you would not think to mention.

What you should not send is a full card number, a photo of the whole card, or any code from the bank. We do not need them and sending them only creates risk for you. If a card has to be identified at all, its last four digits are enough to describe which ones you have already tried.

What our team can and cannot do about a decline

We can help with everything on the order side: confirming whether a successful order exists, checking where the confirmation email went, and advising what to try next based on what we can see. What we cannot do is instruct your bank to approve a payment, unlock your card, view your remaining limit, or make a pending hold release sooner. Those powers sit entirely with the issuer.

Knowing where that line falls saves your own time. When the symptoms point at the bank, start with the bank, and come back to us if the problem turns out to lie elsewhere. We take messages around the clock, and every one that arrives on LINE or by email is answered in turn.

Look at the plans again and start a fresh order on a stable connection

Message the team with a screenshot once you have tried everything