Why does my bank ask me to verify the payment?
It is the card issuer's identity check against unauthorised use, and it happens on the bank's side rather than ours. If you are abroad and cannot receive the SMS code, approve it in the bank's app instead, or use another payment method.
This question tends to come up mid-payment, when a screen suddenly asks for an extra identity check right after card details are entered, whether that's a code sent by SMS or a prompt to open the banking app for approval. Plenty of people are caught off guard by it, especially while abroad and unsure whether the verification code will even arrive. This page explains what that step actually is, who genuinely controls it, and what to do if the code can't be received while travelling.
It suits anyone paying while travelling who hits an unfamiliar verification screen, anyone who has paid successfully at home without extra verification but now finds it required from abroad, and anyone weighing whether to switch payment methods after a failed verification attempt. Everything here covers the general principle of a card issuer's identity check, not any one bank's specific policy, since each issuer sets its own rules differently.
What this verification step actually is
This step is an identity check set up by your credit or debit card's issuer, to confirm that whoever is using the card right now genuinely is its owner, rather than someone else who obtained the card details without permission. Common forms it takes are a one-time code sent by SMS, or a prompt to open the banking app and approve the transaction directly.
The system is designed primarily to protect the cardholder, not to make life harder for the buyer, but when it appears at an unexpected moment, such as mid-trip, it can feel more like an obstacle than the safeguard it was meant to be.
Who actually controls this step
Once payment is submitted on our checkout page, the request travels to a payment processor, which then coordinates with your card's issuing bank. If the bank decides that particular transaction requires extra verification, the verification screen appears directly from the bank's own side, not something we've built ourselves.
Why it happens more often with international purchases
Some card issuers apply stricter verification thresholds to transactions made from a country other than the one the card is registered in, or to a merchant the card has never paid before, as a general way of reducing the risk of unauthorised use. But each bank sets that threshold differently, and we have no way of stating exactly which criteria your own bank applies.
That means a payment might have gone through before without extra verification while at home, yet the same card at the same merchant now triggers it while abroad, because what changed is the transaction's location or context, not the merchant itself.
Can't receive the SMS code while travelling — what to do
If the phone number linked to the card is a home-country number and that original SIM isn't active while travelling, the SMS code may simply never arrive, since there's no signal reaching that number at that moment. This is a common situation once someone has switched to an eSIM for data but hasn't turned on roaming for the original line's SMS and calls.
In that situation, the approach that usually works is opening the banking app on the phone instead, since most banking apps connect over the internet rather than through the original number's phone signal, allowing approval even without any SMS signal at all, as long as the phone has an internet connection through the eSIM or Wi-Fi.
Using the bank's app instead of SMS
Many banking apps carry a push-notification feature that appears immediately when a transaction is awaiting approval, letting you open it, check the details, and approve directly inside the app without ever needing an SMS code at all — but the app needs to be installed and already logged in before departure.
If verification fails or times out
A bank's verification screen usually carries a time limit for entering the code or approving the transaction. If too much time passes because of slow signal or trouble locating the code, that screen can expire and the payment simply fails to complete. In that case, restart the checkout process from the beginning rather than trying to re-enter the same code on a screen that has already timed out.
If verification fails repeatedly within a short span, it's worth pausing before trying again, rather than resubmitting the payment immediately several times in a row, since repeated rapid attempts can look unusual to a bank's own systems and lead to further attempts being temporarily blocked.
Trying an alternative payment method
If verification keeps failing with the same card, switching to a different card or another payment method offered on our checkout page can sometimes let the transaction go through, since the verification threshold is set by each individual issuer rather than one uniform rule — a different card might not require extra verification at all for the same transaction.
Before switching payment methods, it's worth checking whether the original card still has sufficient available balance and hasn't been temporarily blocked for some other reason, since what looks like a verification problem can sometimes actually be the card being declined for an entirely different reason.
Verification succeeded but the order still shows as failed
Sometimes verification succeeds on the bank's side, yet our checkout page still shows the transaction as failed. This usually happens because the page timed out waiting for the bank's response before it actually arrived back, particularly if the internet signal at that moment was unstable, leaving both sides with mismatched information for a moment.
In that situation, check first whether a confirmation email arrived, and check the account statement or banking app for whether money was actually deducted. If money was taken but no confirmation email shows up, contact us with the date, time, and amount charged, so it can be looked into and sorted out.
What we can and cannot see during verification
| What we can see | What we cannot see |
|---|---|
| The final result of the transaction — success or failure | The specific reason a bank declines or requests extra verification |
| The time the transaction was submitted to the payment system | The live verification status while it's in progress on the bank's side |
| Whether a charge genuinely succeeded in our own system | Your bank account details or verification codes |
The boundary of what's visible to us during this step
Cards locked to domestic use only
Some cards, particularly debit cards or those issued by certain local banks, default to allowing domestic transactions only until the cardholder switches on international transactions themselves through the banking app or by contacting the bank directly. If that hasn't been switched on ahead of time, a transaction from abroad may simply be declined outright rather than merely asking for extra verification.
If a card might be locked this way, the most direct way to check is opening the banking app and looking at the card's own settings, or asking the bank before departure, since this is far easier to sort out in advance than trying to fix it while already mid-trip.
How credit cards and debit cards differ in this step
Both credit cards and debit cards can equally be subject to this extra verification, since the step is a general security standard for card payment systems overall rather than something tied specifically to one type of card. The exact app or channel used for verification can still differ between issuers.
What differs more noticeably is the consequence of repeated declines: a debit card deducts directly from a bank account, while a credit card draws against a line of credit extended by the bank. If access to funds while travelling is a concern, carrying both card types as a backup option is generally safer than relying on just one.
Turning on international use ahead of a trip
If a trip abroad is known about in advance, opening the banking app beforehand to check whether the card allows international transactions at all is a step that meaningfully cuts down on sudden declines. Many banking apps carry a direct on/off switch for international transactions right inside the app itself.
If no such switch can be found in the app, or it's unclear whether the card supports it at all, calling or messaging the bank directly before departure is a safer route than waiting to run into the problem while actually paying from abroad, which can be considerably harder to resolve since contacting the bank from another country isn't always as convenient as doing so at home.
Paying over hotel or café Wi-Fi versus over the eSIM
The bank's verification step behaves the same whether payment happens over a hotel or café's Wi-Fi, or over the eSIM's own internet connection, since the bank looks mainly at the transaction and account details themselves, not which channel is providing the internet connection at that moment.
What differs is connection stability: some public Wi-Fi networks can drop suddenly or slow down when many people are using it at once, which can leave a verification screen loading too slowly and timing out before it completes. Where possible, it's worth completing an important payment over a more stable connection, such as the eSIM's own data, rather than relying on an unpredictable public Wi-Fi network.
Does using a VPN affect the verification step
If a VPN is switched on while paying, some bank systems may see the transaction as coming from an even less familiar location than usual, since a VPN changes the connection's apparent location, which can increase the odds of extra verification being requested, even though your actual physical location hasn't changed at all. We can't confirm whether your own bank applies a policy like this.
If verification keeps failing repeatedly while a VPN is active, try switching it off temporarily and attempting the payment again to see whether that helps, before concluding the problem must lie entirely with the bank or our own payment system.
Whether to contact us or the bank first
If the problem is a code that never arrived, a blocked card, or a decline with no clear reason, contact the card-issuing bank first, since it's the only party that can see the details behind that decision and act on it directly. We have no visibility into the bank's side and cannot approve anything on its behalf.
If verification succeeded but the order still doesn't show up in our system, or money was deducted with no confirmation email, that's when to contact us directly, since it concerns the order's status in our own system rather than the bank's verification step itself.
| Situation | Who to contact first |
|---|---|
| The SMS verification code never arrives | Your card-issuing bank |
| The card is declined or blocked with no clear reason | Your card-issuing bank |
| Verification succeeded but the order isn't showing in the system | Our support team |
| Money was charged but no confirmation email arrived | Our support team |
Matching the contact to the actual problem, so nothing waits on the wrong side
- 1Check for signal and internet before assuming the code isn't comingSee whether the phone has enough signal or an internet connection at that moment, since both the SMS code and the banking app's notification depend on a connection to arrive at all.
- 2Open the banking app to see if there's a pending approvalOpen the banking app directly and check whether a pending approval already shows there, even if the SMS itself hasn't arrived.
- 3Approve the transaction from within the app if that option existsIf the banking app offers a direct approval button, use it instead of continuing to wait on the SMS code.
- 4Try again once signal returns, or switch payment methodIf verification still won't complete, wait until signal improves and try again, or switch to a different card or another payment method offered at checkout.
- 5Contact the bank if the code keeps failing to arriveIf the problem repeats several times with no clear cause, contact the card-issuing bank directly to ask why and have it resolved at the source.
- Confirm the phone has signal or an internet connection at that moment
- Check the banking app for a pending approval
- Check the card still has sufficient limit and isn't blocked for another reason
- Try a different card or payment method if verification keeps failing
- Contact the card-issuing bank directly for the exact reason
সচরাচর জিজ্ঞাসা
Can eSIMonline switch off or skip this verification step for me?+
No. This step is controlled entirely by your own card-issuing bank, not by our system.
Why does travelling abroad seem to trigger this verification more often?+
Some issuers apply stricter checks to transactions from a different country or an unfamiliar merchant, but each bank sets its own threshold. We can't state the exact criteria your bank applies.
What if I don't have the banking app installed?+
Try installing it if there's an internet connection available at that moment, or use a different card or payment method offered at checkout, and set the app up before the next trip.
Will retrying the payment many times get my card blocked?+
We can't say for certain, since that depends on each issuer's own rules, but rapid repeated attempts within a short time can look unusual, so it's safer to pause before trying again.
If verification never completes, does the order still get created?+
Generally not, since the payment itself hasn't gone through, so no completed order is created. Check for a confirmation email to be sure, or contact us if uncertain.
Is there a payment method that skips this verification step entirely?+
That depends on the card issuer and the payment method chosen, not something we control. Some cards or methods may not require extra verification for a given transaction, but that's never guaranteed.
Instagram and TikTok have no web share button, so we open your phone's share sheet or copy the link instead.