ChatDiagram
Flowchart · User Journey · Banking

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.

Typ FlussdiagrammStandard Sugiyama layered DAG + orthogonal routingEngine schematex-flowchartAktualisiert 22.9.2026
Mobile banking password reset
Drawing preview
Die Anfrage

“Create a top-down mobile banking password-reset user journey: open the app, select Forgot password, enter a customer ID, and receive a one-time passcode. If the passcode is invalid, route to bank support and account recovery review. If valid, create a new password, optionally enroll Face ID or fingerprint, sign in, receive a security alert, and restore account access.”

Dann probieren SieAdd a device-recognition check before sending the passcode.Change the failed-passcode path to lock the account after three attempts.
Was diese Zeichnung zeigt

Die dahinterstehenden Entscheidungen verstehen.

01Passcode validation

A failed one-time passcode does not continue to password creation and instead enters recovery review.

02Customer identification

The customer ID step anchors the reset request before the passcode is delivered.

03Biometric choice

Biometric enrolment is optional, so customers can complete the reset with a password alone.

04Security alert

A notification after sign-in gives the customer a visible record of the credential change.

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.

Alle Flussdiagramm-Vorlagen durchsuchen →

FAQ

Häufige Fragen

Why does an invalid passcode go to support?

The diagram treats an invalid code as a point for assisted account recovery rather than permitting a reset.

Is biometric sign-in required?

No. It is an optional branch after the new password is created.

Why send a security alert after sign-in?

It notifies the customer that credentials changed and can help reveal an unexpected reset.