OAuth Migration Overview

  • Updated

Open authentication or OAuth is an increasingly common, secure method of data sharing where an end user gives permission to one application or website to access their data that is stored on another application or website. OAuth is a token-based solution, meaning credentials are handled entirely by the OAuth provider (usually a financial institution in this case) and exchanged for a token that MX can use.

Migrating your connection with MX to OAuth provides a faster, more secure connection for both you and your customers, however, it does require some lift upfront. Your developers will need to implement the necessary code changes, if applicable to your integration. After that, your OAuth connection will go live at which point end users will need to re-authenticate their accounts with MX.

Explore the articles below to get a clearer picture of what transitioning to OAuth looks like for both you and your end users.

What you can expect:

Code Changes & Developer Documentation

  • Overview of what developer support you can expect to plan for, as well as step-by-step developer instructions to share with your team.

Call Center Impact

  • Overview of what call center impact you can expect and what notifications the end user will see.

Instant Account Verification & Identity Verification

  • Overview on availability and changes.

What your end users can expect:

Changes to User Experience

  • Overview of what your users’ new experience will be and what benefits they will see.

Supporting Multiple Accounts

  • Overview of connecting multiple accounts from one institution.

Was this article helpful?

0 out of 0 found this helpful