OAuth Integration
Read about supporting OAuth integrations
There are two types of flows that users can be directed towards while adding a bank account.
Non-OAuth: Users authenticate and permission data directly from the widget to allow us access to their financial accounts.
OAuth: OAuth provides a more secure connection for your users as credentials are handled entirely by the OAuth provider (bank) and exchanged for a token that we can use. OAuth connections are predefined based on the bank's policies and our integrations. To connect accounts via OAuth, users will be directed to the bank's website for authentication and authorization. Once the user grants permission, the user will have to be redirected to our widget to complete the flow. The permission account will be connected and users will have to select a specific bank account (savings or checking) from the connected bank to be add to our platform.
OAuth for Web
For non-OAuth flow, all events will need to be completed in Machnet's widget.
For OAuth flow, when a user selects an OAuth supported bank and confirms in the widget, a new tab will open in their current browser. Once the user grants the required permissions, the tab will close by itself and the user will be redirected to the previous tab where they can see that the connection is being established. Once the connection is established, user will have to select the bank account they would like to use from the list of savings and checking accounts available in the connected bank.
Note: We recommend you to not use ‘appScheme’ for browsers.
Webview widget for mobile application
For non-OAuth flow, all events will need to be completed in the widget in webview.
For OAuth flow, when a user selects an OAuth supported bank and confirms in the widget, the user will be redirected to their bank’s website. Once the user grants the required permissions to link the bank with our system, the browser will redirect the user to the appScheme. You will need to make sure you set the ‘appScheme’ to the deep link of your application when you load the bank widget. If this field is not set while loading the widget, the user will not be automatically redirected to your app upon completion of the OAuth flow.
Last updated