Using a UK Number for Wise SMS Codes

It receives SMS reliably, including the one-time code Wise sends to activate a number and the codes it sends at login and when you change sensitive settings. Our line is a real UK mobile carrier number delivered as an eSIM profile, so it behaves like an ordinary mobile line in the SMS system rather than like a web service.

Incoming SMS and incoming calls are unlimited and work worldwide over roaming, which is the practical benefit for anyone who moves between countries. The line carries no mobile data, so you keep your usual SIM or a travel data eSIM for internet and let the +44 profile sit alongside it as a dedicated receiving line.

It does not verify your identity. Wise runs its own checks against a government document and frequently proof of address, and neither the country of your phone number nor the fact that you own one is evidence in that process. It does not create residency. Where you live is established from documents and other signals, and claiming otherwise is a misuse we do not support.

It does not change eligibility or feature availability. Wise serves different countries under different rules, and some products including the card are limited by where you are. A +44 number will not unlock a country Wise does not serve, will not convert a non-UK account into a UK one, and will not obtain account details you are not entitled to. We never guarantee any service accepts any number and do not refund because one rejected it.

The phone step and the document step exist for different reasons, and understanding that removes most of the confusion around this topic. Identity verification is a compliance control. A regulated money service is required to establish who its customer is and, usually, where they live before it moves funds for them. It runs against documents, it happens once or on review, and its output is a legal fact about a person. A phone number contains no such fact, so it cannot feed into it.

The one-time code is a session control. Its job is to prove that whoever is holding this login right now also physically holds the device the account was tied to. It defends against a stolen or reused password, and against someone who has your email but not your handset. That is why it repeats at every login while the document check does not, and why the two are never interchangeable.

There is a third reason the code exists, specific to money movement. Confirming a change to a payee, a password or a registered device by a channel outside the browser session makes it much harder for an attacker who has taken over the session to quietly redirect funds. The code is protecting the transaction path, not proving who you are. Read that way, it is obvious why a number cannot substitute for identity verification: it was never trying to.

This is the practical failure that traps people, and it applies to more than one service. When you change a registered number, the platform may send a confirmation to the old number to check that the request is genuinely yours. If you have already thrown away the old SIM or let the line lapse, you cannot receive that confirmation, and what should have been a two minute change becomes a manual identity recovery.

So change the number while you still control the old one. Get the new line working and proven first, then perform the change, then confirm on the old line if asked, and only then retire it. If you have already lost the old number, Wise offers alternative routes on the verification screen and, failing those, a path that confirms your identity before it will move the number, but expect it to take longer.