Getting blocked by Wise because you can’t access your old number is one of those cool, cool, cool so I can’t access my money moments. It usually happens after a SIM swap, a lost phone, travel, or your carrier randomly deciding OTP texts are suspicious today.
This guide covers verify Wise without a phone number, the safe, non-weird way: first, you figure out what Wise is actually asking for (identity vs 2-step vs recovery), then you use Wise’s own Try another way options, and only then do you worry about SMS delivery and a reliable number setup.
fastest path if you’re locked out
If Wise is blocking you, don’t guess. Figure out whether its identity (KYC), 2-step verification, or account recovery, then take the matching path. Wise supports alternative methods when one isn’t working, so switching methods is usually faster than hammering resend code until you get rate-limited.
Helpful reference: Wise’s didn’t receive the 2-step code or notification guide; it explains to try another way, and I don’t have any of these recovery routes. (Wise help article)
Here’s the quick playbook:
- Name the screen first: identity banner, 2-step prompt, or recovery steps.
- Use a two-tries-max rule for resends: resend once, wait a minute, resend once, then stop.
- If you’re on a new device, follow Wise’s new-device/2-step troubleshooting flow. (Wise 2-step help flow)
- Lost SIM or no access to the number? Go straight to Try another way → I don’t have any of these.
- Traveling? Prefer internet-based approvals (app notifications/passkeys) over SMS when available.
Mini example: If you request 6 codes in a row, you’ll often get them out of order (or delayed). Then you enter the wrong one, and suddenly you’re locked out longer than you needed to be. Ask me how I know.
First, figure out what Wise is asking for: identity, 2-step, or recovery.
Verification is a messy word. In Wise-land, it usually means one of three things, and each one needs a different fix. Wise’s help content separates 2-step issues, phone number changes, and identity confirmation routes. (Wise 2-step troubleshooting, Wise phone number change)
KYC or identity checks vs login security checks
Identity (KYC) is about proving who you are (ID, selfie, sometimes address). Login security is about proving it’s really you logging in (2-step code, app approval, passkey).
A quick spot the difference cheat sheet:
- Identity/KYC: asks for documents, selfies, or steps to verify your identity.
- Login security (2-step): asks for a code/approval to sign in or approve a risky login.
- Recovery: shows up when you can’t use your usual 2-step method and need a fallback.
If you’re stuck at login, you’re probably in the 2-step/recovery lane, not the “upload your documents again” lane.
The two-tries-max-resend rule avoids code chaos.
Resending is fine once. Twice. Then you stop.
Why? Because carriers and devices can delay OTP messages. You end up with a little pile of codes, enter the wrong one, and it feels like Wise is broken, when it’s really just a timing issue.
Use this instead:
- Request the code
- Wait 60 seconds
- Request once more
- If it still doesn’t arrive → switch method (Try another way) or go recovery
Verify Wise without a phone number, what’s possible vs not.
You can sometimes get into Wise without SMS, but not always. Wise supports alternative verification methods and recovery steps, but if you have no usable method at all, you’ll likely need to confirm identity through the official recovery flow. (Wise 2-step not received)
When a number or identity check is required
If Wise detects a new device, an unusual location, or you can’t access any verification method, you’ll be prompted to enter recovery mode. Wise’s flow explicitly includes “I don’t have any of these,” followed by identity confirmation (often selfie-based). (Wise 2-step flow)
And yes, sometimes SMS isn’t optional. But if you’re forced into SMS, don’t treat it as spam resend until it works. Treat it as I need a method that reliably receives OTPs.
Wise account recovery without a phone number
If you can’t access your phone number, Wise gives you a recovery route. The key moment is choosing to try another way → I don’t have any of these and then confirming it’s you (often via selfie). Wise documents this exact path. (Wise recovery guidance)
Here’s how it usually plays out:
- You try to log in
- You hit 2-step verification
- You can’t receive SMS
- You pick. Try another way
- You pick, I don’t have any of these
- Wise asks you to confirm your identity
I don’t have any of these identity or selfie confirmations.
This is the OK, prove you’re you step. Take it seriously and do it cleanly. Rushing selfies in terrible lighting is where people lose time.
What helps:
- Bright, even light (face clearly visible, no harsh shadows)
- A steady phone (rest elbows on something)
- Follow the on-screen framing rules (don’t fight the box)
What to prepare before you start
Before you press go, have:
- Your ID ready
- A stable internet connection
- A phone camera that isn’t smudged
- 5–10 minutes where you won’t be interrupted
Change phone number on Wise Safe methods.
If you still have access, changing your number is straightforward. If you don’t, Wise ties the change to verification steps so they can confirm it’s really you. Wise’s phone-number change article walks through both logged-in and locked-out cases. (Wise: change phone number)
If you can still log in
Best-case scenario: you’re logged in and simply updating details.
Typical steps (high level):
- Go to your profile/personal details
- Update mobile number
- Verify the new number
Pro tip: Do this before you cancel the old SIM if you can. It’s boring advice, but it saves pain.
If you can’t access the old SIM
This is where people get stuck. If you can’t receive a SMS verification on the old number, you’ll likely need to use the official route:
- Login → 2-step page → Try another way
- If needed: I don’t have any of these
- Confirm identity → then update number
Wise explicitly notes that steps can differ, and sometimes they’ll request more info to verify you. (Wise: change phone number)
Wise verification code not received, fix delivery before retrying.
If your Wise code isn’t arriving, treat it as a deliverability issue, not as a Wise issue. Fix one variable, retry once, and stop. Wise’s own troubleshooting covers switching methods and recovery when codes/notifications don’t arrive. (Wise: code not received)
Why do standard texts work, but OTP doesn’t filter?
Standard texts are person-to-person. OTPs often come through automated routes, and carriers filter those aggressively.
In the US, especially, A2P (application-to-person) messaging rules exist to reduce spam, which can also affect automated verification traffic. Twilio’s overview of US A2P 10DLC explains the carrier ecosystem and the rationale for filtering. (Twilio: A2P 10DLC overview)
Wise 2-step verification options make future logins easier.
Once you’re back in, do yourself a favor: set up a method that doesn’t collapse the second you change SIMs.
Wise explains how to add/change/remove 2-step verification methods, including authenticator app pairing. (Wise: 2-step settings)
App notifications vs SMS
SMS: convenient, but vulnerable to roaming delays, filtering, SIM swaps, and why is my carrier doing this today? moments.
App notifications: generally more reliable when traveling because they need data/Wi-Fi.
If you travel a lot, app-based approvals are usually the calmer choice. Less friction, fewer surprises.
Free vs low-cost virtual numbers: Which should you use for Wise verification?
If Wise truly requires SMS, your goal is reliable OTP delivery. Use free options only to test deliverability, then move to a stable setup for real access: one-time activations for a single code, rentals for ongoing access.
Using a temp number can be a practical way to keep your personal life private for low-risk testing just make sure you follow Revolut’s terms and local regulations
Compliance note: PVAPins is not affiliated with Wise. Please follow each app’s terms and local regulations.
Testing deliverability free numbers vs rentals
Here’s the honest take:
- Free/public-style numbers can help you quickly see if OTPs arrive at all, but they’re inconsistent and not great for privacy.
- Rentals are for repeat access (logins, security prompts, account stability).
If this is a fintech account, shared inbox-style numbers are not where you want to live long-term.
One-time activations vs rentals, what fits your situation
Use this rule:
- One-time activation: I need one code once, right now.
- Rental: I’m going to need this again next week / next login / during travel.
Private or non-VoIP options, where available, and why they matter
Some platforms are picky about number type and routing. Where available, private/non-VoIP options can improve deliverability compared to shared/public numbers, especially when OTP delivery is the whole point.
PVAPins is built around practical verification use:
- 200+ countries
- fast OTP delivery
- API-ready stability (functional if you’re automating workflows)
- privacy-friendly setup choices
Payments (if you need flexibility): Crypto, Binance Pay, Payeer, GCash, AmanPay, QIWI Wallet, DOKU, Nigeria & South Africa cards, Skrill, Payoneer.
United States carrier filtering & delayed OTPs
In the US, carrier filtering for automated/A2P messaging is standard, so OTP delivery can fail even when standard texts work. If SMS is unreliable, try app/passkey approvals first or use a more dependable receiving method. (Twilio: A2P 10DLC)
Quick US checklist:
- Check Unknown senders and spam/filtered SMS folders
- Confirm you’re not in a dead zone (low signal causes delays)
- Avoid rapid resends (you’ll get delayed codes out of order)
- Prefer app notification/passkey when offered
- If SMS is required, use a stable number method (avoid shared inbox numbers)
Mini example: You’re on hotel Wi-Fi, your phone has 1 bar, and an SMS arrives 6 minutes late. That’s not a Wise bug. That’s the network being the network.
India DLT rules & OTP delivery quirks, what to do
India’s SMS ecosystem is heavily regulated and filtered, so OTP delays and template-based filtering can happen, especially during peak times. If SMS is flaky, use internet-based approvals when available or switch to a more reliable receiving setup.
For official regulatory context, TRAI publishes telecom regulations and related materials here: (TRAI regulations)
Quick India checklist:
- Test if SMS is failing broadly (request another OTP from a different service)
- Check filtered/spam SMS folders
- Space attempts (avoid cooldowns + code confusion)
- Prefer app notification/passkey when available
- If you must use SMS, prioritize reliability and compliance
When to contact Wise support and what to include
If recovery fails, you’re stuck in a loop, or you can’t change your number, contact Wise support with a clean support packet. It prevents the endless “Please try restarting your phone” message.
The support packet checklist
Send this:
- Screenshot of the exact step + error message
- Two timestamps (attempt #1 and attempt #2)
- Device + OS version + app/browser version
- Country + carrier (if SMS-related)
- Which option did you select (Try another way / I don’t have any of these)
Wise’s Help Centre is the best starting point for official flows: (Wise Help Centre)
Prevent duplicate entries in your less-dramatic verification setup.
Once you’re back in, fix the root cause: add a backup method, keep a trusted device healthy, and don’t rely on a single SIM as your only key to the account.
Backup methods, trusted device hygiene, travel checklist
A setup that reduces future headaches:
- Turn on app approvals or passkeys when available
- Keep your email inbox healthy (storage, spam filters, recovery access)
- Don’t change phone + email + 2-step methods all at once
- Travel checklist: roaming plan, notifications enabled, power saver not blocking background activity
- If you rely on SMS sometimes, choose one-time activations for quick access,
If PVAPins is part of your setup:
- Start with free numbers to test
- Move to rentals for repeat access
- Keep FAQs handy for rules + troubleshooting
- Prefer mobile workflow? Android app
Compliance reminder: PVAPins is not affiliated with Wise. Please follow each app’s terms and local regulations.
If you want a reliable SMS setup across 200+ countries, start here.
FAQ
1) Can I verify Wise without a phone number?
Sometimes. If Wise offers an alternative, such as app approval or a passkey, you may not need SMS. If you can’t use any method, you’ll usually need to use the official recovery flow to confirm your identity.
2) What if I didn’t receive the Wise 2-step verification code?
Start with deliverability: check signal/roaming, spam/filtered SMS folders, and blocked senders. Then use Try another way instead of repeatedly resending codes. (Wise: code not received)
3) How do I recover my Wise account if I lost my phone number?
On the 2-step screen, select Try another way, then I don’t have any of these, and follow the identity confirmation steps. Wise documents this path for account recovery. (Wise recovery flow)
4) How do I change my phone number on Wise?
If you’re logged in, you can update it in your personal details. If you can’t access the old SIM, Wise may require extra verification to confirm it’s you before changing the number. (Wise: change phone number)
5) Are virtual numbers allowed for Wise verification?
That depends on Wise’s terms and your local regulations. If you use a number service, prioritize reliability and compliance, especially for sensitive financial accounts.
6) Why do normal texts arrive, but Wise OTP doesn’t?
OTP messages often travel via automated routes that carriers filter more than person-to-person texts. This is common in markets like the US, where A2P policies are in place. (Twilio A2P overview)
7) Are passkeys safer than SMS codes?
In general, yes. Passkeys are designed to be phishing-resistant and don’t rely on phone networks.
Conclusion
If Wise is asking for verification and you don’t have your old number, the trick isn’t resend until it works. The better move is to identify the type of verification you’re facing, use Try another way, and, if needed, follow the official “I don’t have any of these recovery routes.”
And if SMS is genuinely required, don’t roll the dice on flaky delivery. Use a clear ladder: test deliverability first, then pick one-time activation for a single login, or rentals when you need repeat access.