Intelligent MFA Prompt Grouping During One-Step Update

jlwilkinson

Problem

As more financial institutions require multi-factor authentication (MFA), One-Step Update often becomes a repetitive stop-and-go process. Each institution prompts separately for MFA delivery method and verification codes, interrupting the update process multiple times.

For users with many accounts, this significantly reduces the convenience that One-Step Update originally provided.

Suggested Improvement

Enhance One-Step Update to learn and optimize MFA interaction patterns for financial institutions.

Quicken already manages the MFA prompts presented to the user. It could record historical interaction patterns and use them to organize updates more efficiently.

Proposed Workflow

During One-Step Update, Quicken could organize updates into phases:

Phase 1 – Initiate MFA challenges

• Start updates for institutions known to require MFA.
• Prompt the user to select the delivery target (SMS/email/app) for each institution.

Phase 2 – Collect verification codes

• Once all institutions have initiated MFA challenges, prompt the user to enter the verification codes.

Phase 3 – Complete downloads

• Resume transaction downloads for those institutions.

Phase 4 – Update non-MFA institutions

• Update accounts that do not require MFA.

Benefits

• Reduces repetitive interruptions during One-Step Update.
• Allows the user to handle MFA prompts in batches.
• Restores the ability to start updates and step away from the computer.
• Improves efficiency for users with many financial accounts.

Optional Enhancement

Quicken could maintain a historical MFA profile per financial institution, including:

• Whether MFA is typically required
• Number of steps typically involved
• Preferred challenge methods

This information could allow the update process to dynamically group accounts requiring similar authentication workflows.