FLOWCHART

Mobile banking password reset user journey

This mobile banking password-reset flowchart shows the customer-facing recovery path from opening the app to restored account access. It separates the normal self-service route from the path that needs bank support, so product, fraud, and service teams can agree on what a failed passcode should do.

UPDATED 2026-09-23
EXAMPLEMobile banking password reset user journey
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

A digital banking team documents a customer password-reset path that combines self-service recovery with a safe route to assisted recovery.

Key decisions

  • Passcode validation: A failed one-time passcode does not continue to password creation and instead enters recovery review.
  • Customer identification: The customer ID step anchors the reset request before the passcode is delivered.
  • Biometric choice: Biometric enrolment is optional, so customers can complete the reset with a password alone.
  • Security alert: A notification after sign-in gives the customer a visible record of the credential change.

When to reuse this

Use this for a consumer financial app that supports one-time-passcode recovery. Replace the identity and escalation steps with the controls required by your bank's risk policy.

FAQ

Frequently asked questions

Why does an invalid passcode go to support?01
The diagram treats an invalid code as a point for assisted account recovery rather than permitting a reset.
Is biometric sign-in required?02
No. It is an optional branch after the new password is created.
Why send a security alert after sign-in?03
It notifies the customer that credentials changed and can help reveal an unexpected reset.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.