Historically, direct deposit switches have required too much coordination—not to mention paperwork—between you, your users, and their employer or payroll providers. It can be so cumbersome that many users never complete the process.
Enable your users to authorize a direct deposit switch instantly. Argyle automates account switching so that there’s no work on your end. For your users, it’s practically as simple. With just a few clicks and without leaving your platform, they can authorize a direct deposit switch or allocate a percentage of their wages to you.
We suggest integrating Argyle in two phases:
- Scoping (this guide) - determine how you want to use Argyle and how to present the Argyle experience to your users.
- Technical implementation - a guide to get you up and running.
There are five aspects to consider when thinking about the user flow:
- Where in the process do you want to leverage Argyle?
- Which users do you want to route through Argyle?
- What proportion of the paycheck would you like to receive?
- How to on-ramp and off-ramp users?
- How can a user manage their connected direct deposits?
Typically, banks show an option to change a direct deposit upon signup and when prompting users to set up direct deposit to access gated features, like cash advance, early paycheck access, etc.
You can initiate Argyle in two ways:
- All users through Argyle (recommended)
- Argyle for covered companies only
Send all users through Argyle and leverage Argyle as a switchboard to alternative direct deposit switching 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 account. For users where Argyle does not have coverage, a Can't find your employer? button appears. When the user clicks this button, Argyle Link closes and a callback is initiated. The callback funnels the user back to your application for an alternative path. The callback function receives an object containing a search query that the user submitted.
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 Employer Search sample app to 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:
- Incentive - users need to clearly understand why they are changing their direct deposit and the benefit this will give them. This can include hard benefits (such as cash rewards), or soft benefits (FDIC insurance, interest, etc.).
- Context - provide users with context into the process they will go through. Users need to understand that they will 1) search for their employer, 2) connect their employment or payroll account, and 3) confirm a direct deposit change.
An example on-ramp screen is provided below:
If you want to receive 100% of the user's paycheck, you can drop the user directly into Argyle Link. However, if you want to be able to receive a smaller proportion as well, you will need to adjust the on-ramp screen or have an additional screen like this:
Moreover, you will need to determine if the user should be able to edit the proportion at a later time (see below: How can a user manage connected deposits?).
After a user connects their account and they are funneled back into your application, it is important to let users know where they can adjust their accounts if their work situation changes:
By default Argyle has your users grant ongoing access to their employment accounts. Provide users with an option to invoke Argyle Link (for example, from an account settings page) so that they can update direct deposit allocations (if you allow for that option) and disconnect their account:
Deposit Switch: Implementation - now that you have scoped the user flow, it's time to move on to the technical part of the implementation.
Updated about 1 month ago