Banking app camera identity check fails: what to try

A camera identity check can fail because the document image is unreadable, the face scan cannot establish liveness or likeness, the camera permission is blocked, or the document itself is unsupported. Repeating the same bad conditions rarely helps; change the cause before trying again.

The app is usually checking more than whether it can see a face

Digital identity processes can verify that the document is genuine, that a live person is present and that the person matches the document photo. GOV.UK’s digital identity guidance uses the same broad model, which explains why a sharp selfie alone may not be enough.

A blurred passport image can fail at the document stage even when the face scan is perfect.

Practical checkpoint for a failed camera identity check in a banking app: establish the starting position before you change anything. Use a passport scan that fails repeatedly even though the document is valid as a worked example and write down document type, expiry date, lighting, camera permission, app version and exact error message. That turns 'The app is usually checking more than whether it can see a face' into a testable sequence rather than a vague problem.

For this part of Banking app camera identity check fails: what to try, avoid acting from memory. Under “The app is usually checking more than whether it can see a face”, keep the live provider wording beside your own amount, date or account status. If the two do not match, resolve that discrepancy first instead of repeating the payment, application or support request.

Fix lighting and framing before changing anything else

Glare over a passport or driving licence can hide security features and text. Use soft, even light, keep the full document inside the frame and avoid fingers covering corners or machine-readable zones.

For the face scan, remove obstructions where appropriate, look straight at the camera and keep still while the app captures the image. GOV.UK gives similar practical guidance for digital identity checks.

Run the numbers or sequence on paper before repeating the action. In the example of a passport scan that fails repeatedly even though the document is valid, separate the amount, date, channel and decision point, then mark which part is confirmed and which part is still an assumption. For 'Fix lighting and framing before changing anything else', the useful question is not simply whether something can work, but what result you should see next and how long you are prepared to wait before changing route.

Second check for section 2, 'Fix lighting and framing before changing anything else': use a passport scan that fails repeatedly even though the document is valid and write a one-line expected result beside the actual result. Then verify document type, expiry date, lighting, camera permission, app version and exact error message. If the two do not match, pause rather than creating another transaction or application. Retry once under better capture conditions, then use the bank's stated manual or branch verification route.

Check permissions and camera selection

If camera access was denied, the app may show a generic verification failure. Open the phone’s app-permission settings and allow camera access only for the banking app you have verified as genuine.

On devices with several cameras, use the app’s intended front or rear camera rather than forcing a different camera through another application.

Use a controlled process for 'Check permissions and camera selection'. Gather document type, expiry date, lighting, camera permission, app version and exact error message, take one deliberate action, and record the result before trying a second route. Do not upload altered images or send identity documents to an unofficial support address. If the first route clearly cannot complete the job, retry once under better capture conditions, then use the bank's stated manual or branch verification route rather than improvising with an unverified workaround.

Do not keep sending documents through improvised channels

If the in-app check fails several times, use the bank’s official alternative verification route. Do not email passport scans to an address supplied in a chat or social-media message just because somebody claims to be support.

Identity documents can be valuable to fraudsters, so the recovery route deserves the same verification as the banking app itself.

Build a failure plan before the deadline matters. For a failed camera identity check in a banking app, decide what you will do if the normal route fails at the worst reasonable moment: a bill is due, a payment is time-critical, a phone is unavailable or verification will not complete. Keep enough time and money outside the process to recover. Under 'Do not keep sending documents through improvised channels', note the exact error or refusal wording because that is usually more useful to support than a general statement that it did not work.

Second check for section 4, 'Do not keep sending documents through improvised channels': use a passport scan that fails repeatedly even though the document is valid and write a one-line expected result beside the actual result. Then verify document type, expiry date, lighting, camera permission, app version and exact error message. If the two do not match, pause rather than creating another transaction or application. Retry once under better capture conditions, then use the bank's stated manual or branch verification route.

A failure is not necessarily a rejection of your account application

Automated identity checks have false rejects and technical failures. The appropriate next step may be another document, manual review or in-person verification depending on the bank.

Record the error message and stage at which it fails. “Camera failed after face scan” gives support much more to work with than “the app does not work”.

Treat evidence as part of the solution, not paperwork added afterwards. For 'A failure is not necessarily a rejection of your account application', keep document type, expiry date, lighting, camera permission, app version and exact error message in one dated folder and write a two-line chronology of each contact. Do not upload altered images or send identity documents to an unofficial support address, and use only a channel you reached independently when security or fraud is involved.

Treat “A failure is not necessarily a rejection of your account application” as a check you should be able to prove later when dealing with Banking app camera identity check fails: what to try. Keep the relevant figure or status and the date you checked it. If support is needed, lead with that evidence and the outcome you want rather than a long reconstruction.

Fix the capture conditions before repeating identity checks

Identity checks can fail because the camera cannot read the document, the lighting creates glare, the name does not match the bank record or the app cannot compare the face clearly. Before another attempt, clean the lens, use even lighting, remove document covers and make sure the whole passport or driving licence is inside the frame. Repeated rushed attempts can trigger extra review without improving the image.

Check the exact personal details the bank holds. A recent name change, middle name, old address or expired document can make an otherwise clear photograph fail. If the app offers a manual-review or branch route, use it rather than sending identity documents to an email address or messaging account supplied by an unsolicited helper.

If the camera request appears during an action you did not start, stop. Identity video and document images are highly sensitive. Open the bank independently and ask whether it genuinely requested verification. Do not share a selfie holding a document with somebody who contacts you on social media promising to unlock the account.

Finish with a decision rule for a failed camera identity check in a banking app. In the worked example of a passport scan that fails repeatedly even though the document is valid, the safer next step is the one that preserves evidence and keeps essential money or account access recoverable. If the provider cannot explain the next step clearly, retry once under better capture conditions, then use the bank's stated manual or branch verification route and keep the case reference until the outcome is reconciled.

Sources and verification

• GOV.UK - Proving your identity with the One Login app
• GOV.UK - Digital identity guidance
• FCA - Confirming your identity
• NCSC - scam-contact verification

MyBankAnswers uses official provider and UK regulatory sources wherever practical. Information is general and does not constitute financial advice.