Overview

Instant Account Verification (IAV) configuration is specified by the developer in the LinkMoney Web Gateway. A developer can initiate three IAV-specific user experiences in the gateway (note that standalone aggregation is also an option, though not included here):

• Standalone IAV lets users verify their accounts and exit the Link Money Gateway. If the verification is successful, the resulting account data can be used for transfers.

<aside> ℹ️ Use standalone IAV when you only need accounts verified.

</aside>

• IAV & Aggregation lets users verify their accounts for use in transfers; following this initial verification, the user is prompted with an optional step to aggregate transaction data for their verified accounts.

<aside> ℹ️ Use IAV & Aggregation when you need account verification but would like aggregation if possible. If a provider doesn’t support verification, aggregation will not be offered to the user.

</aside>

• Aggregation & IAV lets users link their accounts for aggregation of accounts and transaction data; following the initial aggregation, the user is prompted with an optional step to verify the accounts they’ve aggregated from for use in transfers.

<aside> ℹ️ Use Aggregation & IAV when you need aggregation but would like accounts to be verified if possible.

</aside>

The Verification User Experience

1. The User Authenticates with a Third-Party Financial Institution.

Every time a user loads the Link Money Gateway, some authentication is acquired. See Authentication for information on how to get a Link Money JSON web token, and the Link Money Quickstart Guide for generic information on accessing the portal.

When the user loads the Link Money Gateway in their browser, they are prompted with an account selection screen.

The user may be prompted either with an Open Banking login (a direct connection with their banking application) or a login from that runs directly from the Link Money Gateway.

Application Selection Screen

Example of Open Banking Authentication with Wells Fargo

Example of non-open banking authentication with Discover.

2. The User Selects Which Applications They Want to Authorize for IAV.

After successfully authenticating with a third-party application, the user is able to select which accounts they would like to verify specifically.

Aggregation Account Authorization

Verification Account Authorization