Payment failed. Should I try again straight away?
First check whether anything was charged. If not, retry once. If it fails again, change payment method or contact your bank rather than retrying repeatedly.
- Repeated attempts can look irregular to your bank and get the card blocked temporarily
- A pending authorisation may appear temporarily even when the payment failed
- If unsure whether you were charged, contact us before ordering again
What a failed-payment message actually tells you
A failed-payment screen tells you the outcome, not the cause. The breakdown can happen at more than one point along the same path: your connection at the moment you confirmed, the bank that declined the charge, the payment processor we use, or simply a page that timed out waiting for a response. A short message like "payment failed" does not tell you which of those it was.
That is why retrying immediately without checking anything first carries more risk than it looks. If money was already taken on the first attempt but our system never received confirmation of it, pressing retry can send a second payment instruction for the same order — which can lead to being charged twice for one purchase, or at the very least a pending entry you have to chase down afterwards.
The first step, every time: check whether anything was actually charged
Before touching anything else, open your banking app or the digital wallet you paid with and look at the most recent activity. A charge that genuinely went through does not always appear instantly — it can sit as a pending authorization before settling into a completed line item minutes or hours later. Note the merchant name shown on that entry too, since the name our payment processor passes to your bank may not exactly match the brand you expect.
If you check and find no charge at all — neither completed nor pending — that generally means the first attempt never reached the stage of actually taking money. In that case, trying again is a comparatively safe move.
How many times it is reasonable to retry, and what to wait for first
A workable rule is this: if nothing was charged, one retry with the same card or channel is reasonable. If the second attempt fails again too, do not immediately try a third time the same way — the odds of a different outcome are low, and several rapid attempts in a short window can cause some banks to read the pattern as suspicious and temporarily lock the transaction as a protective measure on your own account.
Rather than repeating the same attempt, switch method instead — move from a credit card to a digital wallet, or try a different card with sufficient available limit. Changing the channel resolves things more often than repeating the same confirmation, because most decline reasons sit with that specific channel rather than with the order itself.
Common reasons a card payment gets declined
Card declines usually come from conditions the issuing bank itself has set, not from us: insufficient available limit for the amount being charged, a card that has not been enabled for online or foreign purchases, an additional verification step like 3D Secure where the bank sent a one-time code but the confirmation window closed before you entered it, or even a card nearing its expiry date that some systems decline a few days ahead of the actual date.
Every bank runs its own policy, so we cannot tell you with certainty which of these applies in your case. What you can reliably do is ask your bank directly — they see a more specific decline code on their side than what appears on our checkout screen.
Common reasons a digital wallet or alternative method fails
A digital wallet is tied directly to the balance sitting in that account. If the balance does not cover the package price plus whatever fee the provider charges, the transaction will not clear. Some wallet apps also set a daily or per-transaction spending limit that can sit below the amount you are trying to pay, and some require you to open the app and confirm inside it within a short window — if the screen is closed before that, the approval expires and the attempt fails.
If you switch method and it still fails
Once both a primary card and a backup method have failed, stop trying on your own. That pattern starts to suggest the issue may not sit with any single channel, but with the device, the connection quality at the moment of checkout, or occasionally a temporary fault on the payment processor's side. At that point it is worth contacting us rather than working through a third, fourth, or fifth attempt.
What your bank's decline message can tell you
Many banks send an SMS or an in-app alert the moment they decline a charge, and that message can carry more detail than what appears on our end — sometimes stating plainly that a limit was exceeded or that additional verification is required. Reading that message before deciding whether to retry or call the bank saves real time compared with guessing at what happened.
What to have ready before you contact your bank
- The approximate date and time you attempted the payment
- The currency and amount the attempt was for
- The merchant name shown on the entry, if any appeared
- Any decline message your bank already sent
- Which card or method was used, and how many attempts in total
The recommended sequence when a payment fails
- 1Check your bank or wallet app firstConfirm whether a pending or completed entry exists for this order before doing anything else.
- 2If nothing was charged, retry once with the same methodLet a moment pass before confirming again, in case the first failure was a brief connection hiccup.
- 3If it fails again, switch payment methodMove to a different card or a digital wallet instead of repeating the same one.
- 4If the new method fails too, stop retrying on your ownThis pattern points to something broader than one channel — let us check it from our side.
- 5Contact us with the details you gatheredSend the screenshot, error text, and every method already tried via LINE or email.
What we can check, and what sits outside our control
| Topic | Our side | Your bank or payment provider |
|---|---|---|
| Whether the order reached our system | We can check this on our side | Not directly relevant here |
| The specific reason a charge was declined | We only see a partial picture | Sees a more detailed decline code |
| Money already charged being released back | Can issue a refund once a genuine error charge is confirmed | Decides which day it lands back in the account |
| Temporarily locking the account from repeated attempts | Not something we trigger | A protective measure the bank applies on its own |
Who owns which part of a payment problem
What to check before trying each payment method
Before moving on to the next channel, run through this table first, since each method tends to fail at a different point. Checking the right thing for that channel cuts down on how many rounds of trial and error you need.
| Payment method | What to check before trying it | Where it usually breaks down |
|---|---|---|
| Credit card | Available limit, whether online and foreign purchases are enabled, expiry date | The extra verification step that has to be completed within its time window |
| Debit card | The actual account balance, not an assumed limit | The balance falling short once any extra fee is added to the price |
| Digital wallet | Wallet balance, and that app's own daily spending limit | The in-app confirmation window expiring before you tap confirm |
| Any other method the checkout supports | Whatever specific terms that provider states in their own app or site | Varies by provider — check directly with that provider |
Pre-check points for each payment method
Reducing the odds of this happening on your next purchase
Before your next purchase, check whether the card you plan to use has already been enabled for online and foreign transactions — some banks classify an eSIM purchase as a foreign transaction even when you are sitting in your home country. Confirming the available limit covers the amount before confirming, and keeping your banking app open in case an OTP needs an instant response, both meaningfully cut the odds of a decline.
If you were accidentally charged twice
If you check and find two successful charges for the same order, do not wait for the system to quietly fix itself — contact us right away with proof of both entries. We will confirm whether they are indeed a duplicate for the same order, then start the refund process for the excess charge.
Do duplicate charges always show the exact same amount?
Most duplicate charges from a repeated payment attempt carry the exact same amount, since they trace back to one order. There are cases where the amount differs slightly because of an exchange rate your bank applied at a different moment for each attempt. If you see two close-in-time charges of a similar size, treat it as likely coming from the same order and flag it to us for a check.
The difference between a failed payment and an order stuck in status
Sometimes what looks like a failed payment is actually an order that cleared payment fine but has not finished the next processing step — for example, the eSIM's QR code taking longer than usual to be issued. That is a different situation from an outright failed payment, and should not be fixed by buying again. Watch for whether you received an order confirmation email: if you did but no QR code followed, that is a sign the money went through and the next step simply has not completed yet, so contact us instead of purchasing a second time.
How paying across currencies can factor in
If your card or wallet is denominated in one currency while the price shown on the checkout page is in another, your bank is the one converting it and may apply its own conversion fee during that step. That conversion step is sometimes exactly what makes a transaction take longer than expected, or what triggers an extra review before some banks approve it. We cannot tell you the exchange rate or fee your bank will apply, since that is set entirely by your own card-issuing bank.
When to stop trying on your own and wait for us to respond
There is no fixed count that marks "enough," but the clear signals are trying more than two channels with no success at all, or starting to see a notice from your bank that the account has been temporarily restricted. Both point to something larger than what you can fix from the user side, and that is the point at which it makes sense to let us step in and check alongside the payment processor instead.
Pros
- Retrying once, when nothing was charged at all
- Switching payment method after the same one keeps failing
- Gathering evidence before contacting us
Cons
- Repeating the same method many times in a row
- Buying a new package while unsure whether the earlier one already went through
- Waiting silently after every channel has already failed
Why we cannot always confirm the cause instantly
Many customers expect us to be able to state instantly what caused a payment problem, but in practice our system only sees the status the payment processor sends back, which is usually a short code rather than a detailed explanation. Getting to the real cause sometimes needs a joint check between us, the payment processor, and your bank, which takes longer than an instant chat reply.
That is why we ask you to send the details you already gathered up front — the more complete it is, the less back-and-forth we need before we can start checking with the payment processor from your very first message.
Întrebări frecvente
If money was charged but I never received the eSIM, how long should I wait before contacting you?+
There is no need to wait days. Contact us as soon as you see a completed charge with no confirmation email or QR code following it — the sooner you flag it, the sooner we can check and fix it.
How many times can I retry the same card before I should switch method?+
One retry is generally enough. If the second attempt with the same card fails too, move to a different card or channel rather than continuing to try the same one repeatedly.
Why does our decline message carry less detail than the one my bank sends?+
The detailed decline code returned by the card-issuing bank comes back to us in a limited form. Our system only sees whether it was declined, not the full internal reasoning the bank itself holds.
What should I do before buying if my card is close to its expiry date?+
Check the expiry date before confirming payment. If it is very close to expiring, switch to a different card or a digital wallet instead, since some bank systems decline transactions ahead of the actual expiry date.
What does it mean if no email about the decline arrives at all?+
It is possible the attempt never reached the stage that triggers a notification email at all — for instance, it dropped out during the connection to the payment processor. Check status directly through your banking app rather than waiting on an email.
Is switching to a digital wallet as safe as using a card?+
Both carry their own security measures, but the specifics depend on each provider. We recommend checking the terms and verification steps of the wallet you use directly with its provider. If the displayed price sits in a different currency than your wallet is denominated in, a conversion step can apply there too, just as it can with a card, and that is set by the wallet provider itself rather than by us.
Instagram and TikTok have no web share button, so we open your phone's share sheet or copy the link instead.