Credit decisioning begins with the verification of income and employment. Argyle provides both of these verifications. We suggest integrating Argyle in two phases:
There are four aspects to consider when thinking about the user flow:
Argyle can read all information within an employment account. This can be used at various periods in the application process:
Argyle has persistent access to an employment account once it is connected. Therefore, wherever you put Argyle in the process, you get all of the downstream benefits (e.g. if you implement in phase 2, you automatically get the data for phases 3 and 4).
There are a few ways how Argyle can be initiated:
Send all users through Argyle and leverage Argyle as a switchboard to alternative VOIE options.
For users where Argyle has coverage, they can connect their account. For users where Argyle does not have coverage, a user will be shown a “Don’t see your company?” button, which when pressed will close Argyle Link and initiate a callback for you to funnel the user back to your application for an alternative path. The callback function will receive an object containing a search query that was entered by the user.
We advise sending all users through Argyle as this provides the best user experience and highest conversion rates.
This option requires you to know who employs the user. You can then check that employer against the Argyle system to confirm coverage. The user will be dropped straight into the login screen (without the need to show the search screen).
You can utilize the search Link items endpoint to query the Link items database and power the company search field in your application.
If Argyle does not cover a particular employer, you then funnel the user to an alternative flow:
Now that you've determined 1) where in your flow, and 2) to which users, you want to surface Argyle, it's important to frame Argyle correctly for your users. Best in class implementations provide two things:
An example on-ramp screen is provided below.
After a user connects their accounts and they are funnelled back into your application, it is important to let the users know what will happen next in the process. This will depend on your overall flow and goals but here are some examples:
By default Argyle will have your users grant ongoing access to their employment accounts. Provide users with an option to invoke Argyle Link (e.g. from an account settings page) so that they can revoke access.
Argyle has access to 120+ employment record data points. For verification of employment, you will most likely want to retrieve:
For verification of income:
Please refer to the Argyle API reference for a full list of all available data points. If you would like to do calculations and projections with income data, you can use our Calculator pre-build to get started.
Not all data is created equal. Employment information like job title or profile information like name are quite stable and usually can be retrieved very quickly. However, paystub information requires a bit more time to download and scan pdf files. Please refer to the diagram below to inform your decisions on data retrieval times: