Mobile banking on a new phone: safe setup checklist
Moving mobile banking to a new phone is easiest when the old phone, registered number and security details still work. The safest approach is to prepare before wiping or selling the old device.
Install the bank’s app only from the official app store, complete the bank’s device-registration process and keep the old phone available until the new one can log in, approve payments and receive security prompts. Remove banking data from the old device only after the move is confirmed.
Do the move before erasing the old phone
Some banks use the old device to approve the new one, while others rely on SMS, card details, passcodes or identity checks. If you factory-reset the old phone first, you can turn a five-minute migration into a manual recovery process.
Keep both devices on hand until you have tested login, a balance refresh and whatever approval method the bank uses for new payees or high-risk payments.
Practical check: You replace your phone on Friday and need to make a £1,400 rent payment before Monday. Write down the amount, date, deadline and channel before you act, then compare the registered mobile number, old-device access, app-store source, bank re-registration steps and any backup web or telephone route. Keep the old device secure until the new registration works where possible, and use only the bank's official app and support routes. Keep registration messages, device-change confirmation, support reference and any failed-payment or authentication message together so a later conversation with the bank starts from a verified record rather than memory.
The phone number can matter as much as the handset
If the new phone also has a new mobile number, update that carefully. Security codes and fraud calls may still go to the registered number. Losing access to both the old phone and old SIM at the same time makes identity recovery harder.
When changing network or number, do not trust an inbound call that claims the bank must “synchronise” the new SIM. Call the bank back using its official number if any security request feels unusual.
Use a small decision table for this situation. Start with You replace your phone on Friday and need to make a £1,400 rent payment before Monday. Verify the registered mobile number, old-device access, app-store source, bank re-registration steps and any backup web or telephone route before choosing. That prevents one unclear detail from driving the whole decision. Keep the old device secure until the new registration works where possible, and use only the bank's official app and support routes.
Rebuild digital wallets and payment approvals deliberately
Apple Pay, Google Pay or another wallet can require cards to be added and verified again. Some bank apps also treat the new device as untrusted for a period or require stronger checks for the first payment.
Do not discover this at a checkout or house-completion deadline. Test wallet setup and payment approval while you still have another working payment method.
For You replace your phone on Friday and need to make a £1,400 rent payment before Monday., preserve registration messages, device-change confirmation, support reference and any failed-payment or authentication message. Put the items in date order and add a short note explaining what each item proves. Do not bury the key fact inside dozens of screenshots. Keep the old device secure until the new registration works where possible, and use only the bank's official app and support routes.
Remove access from the old device when the new one works
Log out where possible, remove cards from digital wallets and use the bank’s device-management screen to revoke the old device. Then wipe the phone using the manufacturer’s reset process before sale, trade-in or recycling.
A broken phone that cannot be wiped should not simply be handed to a repair shop with banking apps logged in. Use remote device controls and contact the bank about deregistering the device if necessary.
Worked decision point: You replace your phone on Friday and need to make a £1,400 rent payment before Monday. Before taking an irreversible step, verify the registered mobile number, old-device access, app-store source, bank re-registration steps and any backup web or telephone route through a channel you chose yourself. Keep the old device secure until the new registration works where possible, and use only the bank's official app and support routes. If the device change blocks an urgent payment, separate the payment deadline from the phone-recovery problem and ask the bank which alternative channel is available.
Check the account after migration
Review recent logins, devices and transactions. A clean migration ends with one expected new device and no unexplained security changes. If you receive a registration alert you did not trigger, contact the bank immediately.
Also update password-manager or recovery records if the old phone stored them. Mobile banking security depends on the whole account-recovery chain, not only the bank app icon.
A useful migration checklist is: old phone charged, registered SIM working, app-store account available, bank credentials to hand, new phone secured with a strong device passcode, then banking app registration. Afterward test a low-risk function before relying on the phone for an urgent transfer. If the bank has a cooling-off period for new payees or new devices, discovering it during a house purchase or airport trip is far more disruptive than discovering it at home with the old device still available.
If the old phone was lost or stolen rather than deliberately replaced, the order changes: tell the bank and mobile network first, secure the old device remotely if possible, then register the new one. A SIM-swap or stolen unlocked phone can expose more than the banking app, including email used for password recovery. Change critical passwords from a trusted device and review account alerts. Treat a forced phone migration as a security incident until you have confirmed that only your new device and SIM remain authorised.
Sources and verification
Daniel Foster
The key mistake is wiping the old phone too early. I would not erase it until the new device can log in, approve a payment and receive the bank’s security messages. Then I would revoke the old device and wipe it. That order keeps the migration boring - which is exactly what you want with banking security.
MyBankAnswers uses official provider and UK regulatory sources wherever practical. Information is general and does not constitute financial advice.