Starling Bank app login, biometrics and a new phone
A biometric or mobile-banking login failure at Starling Bank is usually a device or authentication problem, not a reason to weaken security. Before resetting everything, check whether the bank has an outage, whether the app and operating system are supported, and whether you still control the registered phone number. Preserve access to another verified route for urgent payments.
Try the ordinary passcode or security route before repeatedly re-registering biometrics. Confirm that the Starling Bank app is genuine and current, restart the device, check service status and keep the registered phone number available. If you changed phones or receive an unexpected new-device notification, treat that as a security event and contact the bank through an official channel.
Diagnose the login problem and protect the registered number
If Face ID or fingerprint fails but the Starling Bank passnumber still works, the account may be fine and only biometric login needs resetting. If every route fails, check the bank's service status and whether your device is supported before assuming the account has been blocked.
Record the exact error message. 'Biometric unavailable', 'device not registered' and 'security details locked' point to different fixes. Reinstalling the app without understanding the message can remove a working device registration and create more work. For this mobile-access case at Starling Bank, keep the final bank response with the underlying statement entry until the money and account status have fully reconciled.
Device registration and recovery may rely on the mobile number Starling Bank already holds. If you are changing SIM or phone, update details through authenticated banking before losing the old number where possible. An unexpected loss of mobile service can also be a SIM-swap warning.
If your phone suddenly shows no service and a banking login fails at the same time, contact the mobile network from another device and notify the bank. Do not accept a caller's offer to 'restore access' by reading out one-time codes. Also tell Starling Bank that the mobile signal loss and login problem happened together, because the combination is more significant than either symptom on its own.
Biometrics, urgent payments and device access
Face ID or fingerprint does not replace the bank's underlying authentication. A device software update, new fingerprint set or security change can force Starling Bank to ask for the passnumber again. That is normal; the correct response is to use the official recovery process, not to disable every security control.
Never share the fallback passnumber, security code or one-time verification code with a support caller. Bank staff may guide you through a process, but an unsolicited caller asking you to approve a new device is a strong fraud warning. If someone claims to be from Starling Bank, end the unsolicited contact and restart through the bank's app, website or number printed on your card.
If a £1,380 payment is due today and mobile login is broken, ask Starling Bank what alternative verified route is available - online banking, telephone or branch depending on the account. Do not hand the payment to a third party simply because they can log in to their own bank.
Tell the recipient if the payment may be delayed and keep any direct cost. The account-access problem and the payment obligation are separate; solving one should not create fraud or borrowing risk in the other.
What a new-device problem looks like in practice
You buy a new phone on Friday, restore the Starling Bank app from backup and biometrics fail. The old phone still works on Wi-Fi and the mobile number has not changed. Before deleting anything, confirm the bank's device-registration steps and whether the old device must approve the new one.
If an unsolicited text then says 'new device detected - click here to cancel', do not use the link. Open the bank independently. A genuine device change can coincide with phishing because criminals exploit exactly the uncertainty customers feel during migration. For this mobile-access case at Starling Bank, preserve the evidence that is specific to this provider workflow rather than relying on a generic description of what happened.
The exact fallback credentials and device-registration path vary by bank and app version, so follow the current official instructions rather than a saved screenshot.
Starling is strongly app-led: the transaction feed, card controls, in-app messages and 24/7 support record are central evidence. When a case becomes disputed, keep screenshots and the support reference rather than relying on memory of what the app showed earlier. If you need staff help, state whether the issue began after an operating-system update, device change, phone-number change or unexplained security alert; that saves time and helps separate technical support from a possible account-takeover case.
Provider recovery steps and when to complain
Starling's current help says a customer moving to a new device should download the app and log in using the mobile number linked to the account. If the mobile number is changing too, update it from the old app while you still have access where possible; if the old app is no longer available, use Starling's verified support route.
Starling Online Banking also relies on the mobile app for approval and QR-code login. That makes control of the registered phone especially important: an unexpected device-registration or approval request should be investigated before you approve anything.
A short biometric glitch is frustrating but not automatically a compensable banking failure. If Starling Bank gives incorrect recovery instructions, locks you out for an unreasonable period after identity checks or causes a documented financial loss, preserve the timeline and make a focused complaint.
For example, keep evidence of a late-payment charge directly caused by inaccessible banking. Separate that amount from general inconvenience and explain what alternative routes you tried. That gives the complaint team something concrete to investigate. For this mobile-access case at Starling Bank, preserve the evidence that is specific to this provider workflow rather than relying on a generic description of what happened.
- Record the exact error message
- Check service status before resetting everything
- Keep control of the registered phone number
- Use a verified fallback route for urgent payments
- Treat unexpected new-device alerts as suspicious
- Review devices and transactions after access returns
With Starling, a device problem can quickly become a payments problem because so much day-to-day control sits inside the app. Before wiping an old phone or changing a mobile number, make sure you can still receive security messages and have another way to cover any bill due that day. If access fails during a device change, record the exact error and time rather than repeatedly reinstalling the app, because that gives support a clearer starting point.
Sources and verification
- Starling Bank - official website
- Starling Bank - official login guidance
- Financial Ombudsman Service - banking and payments
- Financial Ombudsman Service - complaint time limits
Hannah Lewis - editorial verdict
Do not solve a biometric problem by weakening account security. Identify whether the failure is the sensor, app, device registration or account access; keep control of the registered phone number and use a verified fallback channel for urgent payments. With Starling Bank, unexpected new-device alerts or code requests should be treated as security warnings, not routine login friction.
Starling Bank: mobile-app registration and biometric options change with app versions and supported devices. Use the current official mobile-banking guidance for the device in use.