Mobile banking on a new phone: what UK customers should do
Moving to a new phone can trigger fresh device registration and security checks. The safest approach is to prepare the old device and recovery details before wiping anything.
Install the bank’s official app from the recognised app store, start the provider’s device-registration process and keep your old phone available until the new one works. Do not approve unexpected registration codes or calls offering to “move” your banking. If your phone number also changed, update the bank through a trusted channel because SMS and fraud checks may still use the old number.
Keep the old phone until the banking move is finished
The easiest migration is one where the old device still works. Before trading it in or wiping it, check that you know the bank’s login details, have access to the registered email and phone number, and can receive any verification messages. Some banks let customers register a new phone from the old app; others require card details, passcodes, biometrics or a separate authentication step.
Do not assume restoring a full phone backup automatically restores banking access. Security-sensitive apps may require fresh registration even when the icon and app data appear on the new device. Finish that process and test a harmless task, such as viewing the balance, before erasing the old phone.
Download the bank app from a trusted source
Use the bank’s official website to confirm the correct app name or download it from the recognised Apple or Google store. Avoid links sent in text messages saying your banking app needs to be “reactivated” after a phone change. Fraudsters know that device upgrades create uncertainty and can imitate activation messages at exactly the right moment.
Check the developer or publisher name and do not install remote-access software because someone claiming to be bank support asks for it. A real bank may guide you through registration, but it should not need control of your screen or ask you to reveal a full PIN or one-time security code to an unsolicited caller.
A new SIM or phone number can complicate verification
Changing handset and changing number are separate events. If you keep the same SIM or eSIM, the bank may still recognise the phone number even though the device is new. If the number changes, update it using the bank’s approved process so security alerts and authentication do not continue going to the old number. Some providers impose a short security delay after sensitive details change.
If the old number is no longer under your control, treat that as an account-security task, not merely an inconvenience. Update the bank, email recovery details and other important financial services. A recycled phone number can create risks when organisations continue sending verification messages to it.
Recheck digital wallets and payment limits
Apple Pay, Google Wallet and other digital wallets may require cards to be re-added or re-verified on the new device. A card that worked in the wallet on the old phone is not automatically proof that the new wallet has been authorised. Follow the bank’s official verification flow and remove the old device from wallet or account settings when it is no longer yours.
Also check app notification permissions and any transfer-limit settings that are device-specific. A bank may temporarily restrict new-payee or high-value actions after a device change. If you know you need a large payment immediately after upgrading, plan ahead rather than discovering the extra check at the deadline.
Securely retire or sell the old device
Once the new phone is fully registered, sign out or de-register the old device where the bank provides that option. Remove payment cards from digital wallets, back up only what you need, then use the operating system’s secure erase or factory-reset process before handing the device to anyone else. Removing the banking app icon alone is not enough.
Keep the device list in your bank and major email accounts tidy. If an old phone remains shown as trusted after you no longer possess it, remove it. Good device hygiene matters because banking security increasingly depends on the phone being a trusted factor, not just a screen where you type a password.
What to do if the old phone is already gone
If the previous phone was lost, broken or traded in before registration finished, use the bank’s official recovery process. Be prepared for stronger identity checks because the provider can no longer rely on the old trusted device. Make sure you still control the registered phone number and email address, and tell the bank immediately if either was compromised with the device.
Do not search social media for an unofficial support agent who promises to bypass registration. Device trust is deliberately difficult to move without verification. A slower official recovery is safer than giving credentials or identity documents to someone who claims they can accelerate it.
Before disposing of the old handset, check not only the bank app but password managers, authenticator apps and email access used for financial recovery. Losing the old phone and discovering that your second-factor codes were stored only on it can lock you out of several services at once. Transfer or back up authentication according to each provider’s secure process before the device leaves your control.
Sources and verification
Daniel Foster — Digital Banking Editor
My rule is simple: never wipe the old phone until the new banking setup has passed a real test. Customers often transfer photos and contacts first, erase the old handset, and only then discover that the bank wants a code, device approval or access to the old number. That turns a ten-minute migration into a support call. I also treat a phone-number change as more serious than a handset change because verification messages can continue to flow to the old number. Update that through an official channel. During the migration period, ignore any unexpected message claiming to help “activate” the new device; scammers know upgrades create a perfect excuse for codes and remote access. Once the new phone works, remove cards from the old wallet, de-register the device and factory reset it before sale. The goal is not merely to make the new app open — it is to transfer trust from one device to the other without leaving a second trusted device behind. If I lose the old device before migration, I expect more friction and accept it. Those extra checks are protecting the account precisely because one trusted factor disappeared unexpectedly. The migration checklist should include authenticator apps and email recovery as well as the bank itself, because those surrounding services often become the real point of failure.
MyBankAnswers uses official provider and UK regulatory sources wherever practical. Information is general and does not constitute financial advice.