End User Experience After Migrating to OAuth

When you migrate your existing customers over to Open Banking/OAuth authentication, they will need to authenticate their accounts and select their data sharing permissions.

The first time a user tries to log in after migrating:

The end user will need to authenticate
- If they log in via Web Browser:
  1. The user will be routed to the financial institution that holds their account in the same window, to then provide their credentials to authenticate.
  2. The user will enter their current financial institutions credentials.
  3. After successful authentication, they will be granted access for their data to connect to your online banking and the window will redirect to bring them back into your online banking UI.
- If they log in via Mobile App
  1. The user will be routed to the financial institution that holds their account in a new window from their default browser.
  2. The user will then provide their credentials to authenticate. This will be their current financial institutions credentials that they will enter.
  3. After successful authentication, they will need to close the authentication window.
  4. They will be granted access for their data to connect to your online banking and they will need to manually return your mobile app.
End User will select permissions and data sharing consent

Once the user has authenticated, they will be prompted to select their permissions on what data they consent to share with you, generally from a pop up window. The UI of the window and options they receive will vary depending on what the financial institution has set up.

They may see a general "grant access to all data" button, or they may be able to select specifics such as accounts, or types of data to share.

When a user returns after initial authentication:

New Benefits To The User

Everything will behave the relatively the same, however there will be some new benefits to the user:

Aggregation (account connection) speed is will be improved.
OAuth connections greatly reduce MFA occurrences.
Accounts will stay connected even if they change their financial institution password because the connection is token-based rather than credential-based.
Reduces incorrect password errors.
The user can see where they have shared their data when they log into their online banking.

mceclip3 (1).png

Examples of what the end user will see:

1. The user will be brought to the redirect landing page.
  
  New Experience
  
  Old Experience
2. The user will select a 2-Step Verification method if they are on an unrecognized device.
3. The user will be sent a temporary code via the method they selected in the previous step.
4. The user will enter the code they received.
5. The user will select what data they want to share.
6. The user will receive confirmation they have successfully connected.
  
  When a user logs into the financial institution online banking, they will be able to see where they have shared their data.
1. The user will be brought to the redirect landing page.
2. The user will select a 2-Step Verification method if they are on an unrecognized device.
3. The user will be sent a temporary code via the method they selected in the previous step.
4. The user will enter the code they received.
5. The user will select what data they want to share.
6. The user will receive confirmation they have successfully connected.
  
  When a user logs into the financial institution online banking, they will be able to see where they have shared their data.
1. The user will be brought to the redirect landing page.
2. The user will select what data they want to share.
  
  When a user logs into the financial institution online banking, they will be able to see where they have shared their data.