PaaS API Docs
  • Getting Started
  • Authentication
  • Use cases
    • Remittance
      • Bonus/Discount on Remittance
    • Business Payments
    • Individual Wallet
    • Business Wallet
    • Payout
  • API References
    • Data Population
      • Spec Sheet
      • Country
      • States
      • Settlement Rates
    • User
      • User Object
        • User Verification
        • Identification Documents
        • User Verification Status
        • CIP Information Status
      • Receive User Object
      • Register a User
      • Update User
      • Business Representatives
        • Business Representatives Object
        • Add Business Representatives
        • Update Business Representatives
        • Get Business Representatives
      • Declaration
        • Declaration Object
        • Declaration
      • Initiate Verification
      • Get User by ID
      • Get Verification Status
      • Add a Receive User
      • Update a Receive User
      • Get Receive User List
    • Funds
      • User Funding Account Object
      • Funding Account Widget
        • OAuth Integration
        • Bank Verification Status
      • Wallet Object
      • Create a Wallet
      • Get Wallet Details
      • Get User Funding Account
      • Delete User Funding Account
      • Add a Receive Account
      • Update a Receive Account
      • Get Receive Accounts
    • Payout
      • Get Banks
      • Get Payers
    • Transaction (External)
      • Transaction Object
      • Create Transaction
      • Get Transaction by ID
      • Cancel Transaction
      • Transaction Delivery
      • Get Transaction Limits
    • Transaction (Wallet)
      • Wallet Transfer Object
      • Create Transfers
        • Load Wallet
        • Unload Wallet
        • Wallet to Wallet Transfer
      • Get Wallet Transfer Details
      • Get Limits
    • Transaction (Payout)
      • Payout Transaction Object
      • Create Payout Transaction
    • Webhooks
      • Subscribe
      • Integration
      • Events
    • Error Codes
  • Sandbox
    • User: Test Values
    • Funds: Test Values
    • Transaction: Test Values
  • Changelog
    • 2023
      • February 14, 2023
      • January 06, 2023
    • 2022
      • December 28, 2022
      • December 26, 2022
      • December 23, 2022
      • December 2, 2022
      • November 21, 2022
      • November 11, 2022
      • October 31, 2022
      • October 17, 2022
      • August 31, 2022
      • August 1, 2022
      • July 25, 2022
      • May 23, 2022
      • April 7, 2022
      • March 30, 2022
      • March 23, 2022
      • Feb 21, 2022
      • Feb 15, 2022
      • Jan 24, 2022
      • Jan 19, 2022
      • March 10, 2022
Powered by GitBook
On this page
  • OAuth for Web
  • Webview widget for mobile application

Was this helpful?

  1. API References
  2. Funds
  3. Funding Account Widget

OAuth Integration

Read about supporting OAuth integrations

There are two types of flows that users can be directed towards while adding a bank account.

  1. Non-OAuth: Users authenticate and permission data directly from the widget to allow us access to their financial accounts.

  2. 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.

PreviousFunding Account WidgetNextBank Verification Status

Last updated 2 years ago

Was this helpful?