Scoping

Plan your paycheck-linked lending integration.

paycheck linked lending cover imagepaycheck linked lending cover image

Automate loan repayments to prevent defaults. Users designate a portion of their paychecks to pay down their debt. Set up notifications for allocation updates so you can proactively mitigate risks.

For paycheck-linked lending:

  1. To get started, your borrower connects their payroll via Argyle Link.
  2. You determine their loan eligibility based on a complete picture of their employment data.
  3. Once approved, your borrower can seamlessly enable paycheck withholdings.

paycheck linked lending getting started imagepaycheck linked lending getting started image

Lenders usually implement this solution in a two-step flow:

  1. Verify an applicant's income and employment.
  2. After making a loan decision and having the user accept loan terms, add a regular pay allocation.

We suggest integrating Argyle in two phases:

  1. Scoping (this guide) - determine how you want to use Argyle and how to present the Argyle experience to your users.
  2. Technical implementation - a guide to get you started and running.

Scope the user flow

Scope paycheck-linked lending user flowScope paycheck-linked lending user flow

There are five aspects to consider when thinking about the user flow:

  1. Where in the process do you want to leverage Argyle?
  2. Which users do you want to route through Argyle?
  3. How to on-ramp and off-ramp users for verifying employment and income?
  4. How to on-ramp and off-ramp users for paycheck-linked lending?
  5. How can users manage their connected accounts?

Where in the process do you want to leverage Argyle?

Argyle has the ability to read all information within an employment account. This can be used at various periods in the application process:

Paycheck-linked lending user flowPaycheck-linked lending user flow

  • During pre-qualification or early application - autofill an entire application (personal information, employment information, etc).
  • Underwriting - decisioning for an applicant.
  • Verification - during verification of employment or income phase after decisioning.
  • Paycheck-linking - when setting up a regular allocation from the borrower's paycheck.
  • Ongoing servicing - ongoing monitoring of employment, income, deposit details to ensure loan repayment or for future marketing opportunities.

Argyle has persistent access to an employment account once it is connected. Therefore, wherever you insert 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 5).

From a product perspective, you can use Argyle to:

  • Verify income and employment (VOIE) to make a loan decision and link a user's paycheck (recommended).
  • Link a user's paycheck.

Paycheck-linked lending user flowPaycheck-linked lending user flow

The recommended flow looks like this:

paycheck linked lending recommended flowpaycheck linked lending recommended flow


Which users do you want to route through Argyle?

There are a few ways to initiate Argyle:

Paycheck-linked lending flowPaycheck-linked lending flow

  • All users through Argyle (recommended).
  • Argyle for covered companies only.

All users through Argyle

Send all users through Argyle and leverage Argyle as a switchboard to alternative loan funding options. Our experience with clients shows that sending all users through Argyle provides the best user experience and highest conversion rates.

For users where Argyle has coverage, they can connect their accounts. For users where Argyle does not have coverage, the user will be shown a Can't find your income source? button that closes Argyle Link and initiates a callback for you to funnel the user back to your application for an alternative path. The callback function receives an object containing a search query that was entered by the user.

Paycheck-linked lending deep linking overviewPaycheck-linked lending deep linking overview

Paycheck-linked lending document uploadPaycheck-linked lending document upload

Argyle for covered companies only

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

paycheck linked lending covered companiespaycheck linked lending covered companies

You can utilize the Employer Search sample app to power the company search field in your application.

If Argyle does not cover a particular employer, then funnel the user to an alternative flow:

Paycheck-linked lending document uploadPaycheck-linked lending document upload

Constraining the Link item list

Not all payroll platforms support direct deposit updates and not all platforms allow more than a single 100% allocation. To successfully implement the paycheck-lending solution, constrain the available Link item list based if a payroll platform supports:

  1. Direct deposit switching.
  2. Two or more pay allocations.
  3. Amount allocations (as opposed to percent allocations only).
  4. Fractional amount values (optional).

The Implementation part of this solution covers how the Link item list can be constrained based on the above criteria.


Verify income and employment (VOIE)

📘

This section is relevant to you if you are using Argyle's Employment data. Otherwise, you can skip to paycheck linking.

On-ramp users

Now that you have determined 1) where in your flow, and 2) to which users, you want to surface Argyle, it is important to frame Argyle correctly for your users. Best in class implementations provide two things:

  1. Incentive - users need to clearly understand why they are verifying their income & employment and the benefit of this. Making it clear that it allows them to complete their application faster and get the best rates, the ideal.
  2. Context - provide users with context into the process they will go through. Users need to understand that they will 1) search for their employer, and 2) connect their employment or payroll account.

An example on-ramp screen is provided below:

alt namealt name

Off-ramp users

After the users connect their accounts and are funneled back into your application, it is important to inform the users what will happen next in the process. This depends on your overall flow and goals but here are some examples:

alt namealt name


Make a loan decision

When users connect their accounts, you can retrieve their employment and income information via the Argyle API to inform your loan decisioning process.

Scope the required data

Argyle has access to 140+ employment record data points. For verification of employment, you are most likely to want to retrieve:

  • employment status
  • job title
  • hire date

For verification of income:

  • net pay
  • gross pay
  • taxes
  • deductions

You can also retrieve full documents:

  • W-2 forms
  • Paystubs

Please refer to the Argyle API reference for a full list of all available data points.

Data retrieval times

Not all data is created equally. Employment information as job title or profile information as name are quite stable and usually can be retrieved very quickly. However, paystub information requires more time to download and scan pdf files. Please refer to the diagram below to inform your decisions on data retrieval times:

data scan timesdata scan times


Paycheck linking

On-ramp users

After making a loan decision and having the users accepted loan terms, drop the users back into Argyle to link their paychecks to the payback of the loan. Users have to confirm a regular and automated pay allocation to the financial institution of your choice.

If you are using the recommended flow, the users do not need to re-authenticate with their payroll platform to link their paychecks. Argyle maintains an active session and can drop the users directly into the direct deposit switching screen:

paycheck linked lending on ramp userspaycheck linked lending on ramp users

To initiate this process, we advise to provide:

  1. Incentive - users need to clearly understand why they are setting up paycheck-linked payments and the benefits of this. It can include hard benefits (i.e. cash rewards), or soft benefits (FDIC insurance, interest, etc).
  2. Context - provide users with context into the process they will go through. Users need to understand that they will 1) see their overall deposit settings with a new allocation to your bank account and 2) have to confirm the new allocation.

On-ramp screen example:

alt namealt name

Off-ramp users

Updating direct deposits is a process that happens within the payroll platforms themselves and is beyond Argyle's direct control. Some platforms confirm deposit switches almost instantly, while a few others can take 24 hours or more to have a pay allocation's status change from pending to active. The most frequently experienced scenario is that it takes a few seconds to confirm a new pay allocation.

To check that changes to a pay allocation have been confirmed within the payroll platform, you should subscribe to the accounts.pay_distribution_updated webhook. Please, find more information about webhooks subscription in the Implementation part of this solution.

After the users re-direct their paychecks, they are funneled back into your application. If the allocation is confirmed instantly, you can surface an off-ramp screen like this:

alt namealt name

Otherwise, inform the users that the direct deposit update is pending and that they will be notified once it is confirmed by the payroll platform.


Help users manage their paycheck-linked allocations

By default, Argyle has your users grant ongoing access to their employment accounts. You should provide them with a way to manage and disconnect their accounts and pay allocations. Provide users with an option to invoke Argyle Link (for example, from an account settings page) to allow users to manage their connected accounts:

paycheck linked lending managing allocationspaycheck linked lending managing allocations


Next Steps

Paycheck-linked Loans: Implementation - now that you have scoped the user flow, let's move to the technical part of the implementation.