To link external accounts, you need to use the v0 APIs.
The v0 Accounts API allows you to link a customer's Bond account to their verified external bank account. Once the external account has been linked, the customer can then transfer funds back and forth between their account and the external account. Once the link is established, we use the
linked_account_id identifier to represent the customer's external account.
An external account can only be linked once it has been verified. This verification takes place as part of the linking process. The type of verification performed depends on the institution the account is held with.
The following graphic depicts the overall linking process flow and fund transfer.
The linking process comprises the following steps:
- Start the Linking external accounts SDK and provide details of the customer's Bond card account.
- From the returned list of options, select the required institute.
- The customer enters their external account details.
The request is either approved or needs to be verified as described below. See table below for verification methods.
- Once these steps have been successfully completed, the customer's external bank account can be used for making transfers.
For examples of how to use the Linking external account SDK, see Linking external accounts SDK.
Each of the available methods for verification depends on the intuition. Each method falls into one of these categories:
- Instant—Your customer enters their bank details during the linking process.
- Automatic—The process performs a micro-deposit and automatically verifies the deposit.
- Manual—The process makes two micro-deposits which then need to be manually verified by the customer.
The following graphic depicts the verification options depending on the institution selected.
The following table describes the verification methods, their types, and how they are work.
|Instant auth||Instant||The default Auth flow during which the customer selects their banking institution and provides their login credentials. Does not require extra configuration steps if Auth is already configured in your app. Supports more than 3,800 financial institutions with credential-based logins.|
|Instant match||Instant||When using Instant Match, your user is prompted to enter their account number and routing number. The last four digits of the user-provided account number are verified against the account mask retrieved from the financial institution. Instant match is automatically provided at supported institutions as a fall-back method when Instant Auth is not available.|
|Automated micro-deposits||Automatic||Plaid makes a single micro-deposit and then automatically verifies it within one to two business days. Expires and needs to be renewed.|
|Same-day micro-deposits||Manual||Used for institutions that don't support Instant Auth, Instant Match, or Automated Micro-deposit verification. Plaid makes two deposits that post within one business day (using Same Day ACH). Users are instructed to manually verify the deposited amounts within one business day. Expires and needs to be renewed.||Does not support transaction history.|
|Unverifiable||Used in a case where a user wants to send a transfer to an external account that is not their own.||Does not support transaction history.|
To transfer funds to a third-party, external account, because you can't verify this account, you need to use the operation shown below.
To transfer funds to an unverifiable account, use the
POST v0/accounts operation (referenced here) and provide the body parameters as shown in the table below.
Updated 11 months ago