Earn - Plan Your UX
Your introductory screen is your chance to introduce the concept of earned wage access to the user. Items you may want to consider adding: explaining the benefits of earned wage access to the user, minimum requirements, context on how repayment will be set up, the necessary steps to complete enrollment, and a clear call to action.
Depending on how you design your screen, you may want to skip our welcome screen and deeplink the user directly to the search experience.
Use Atomic's search (default)
Our search experience has been battle tested with millions of users and is regularly optimized based on our behavioral analytics. We've seen that customers who opt to use our search UI experience a smoother launch and higher conversion rates from the top of the funnel.
In the case where a user is unable to find their employer or payroll provider, we return them to your application with an event indicating that they were unable to find a suitable search result. Upon receiving this event, our customers typically initiate a backup flow.
Or, build your own search
There are use cases where you may want to build your own search, or provide the user with a narrow list of search options to choose from. You may even know where the user is employed. If this describes your use case, or you have something else in mind, we’ve got you covered.By combining our company search endpoint with Transact’s deeplink parameter, you can completely customize your search experience.
Our Deposit product allows us to allocate the proper amount of money into the correct account for a user. This information will be returned in the
task-workflow-finished webhook, which may be a completed or failed response.
We'll check the accounts on file and if the account and amount are already set this step will be skipped and marked as complete.
After the user's account has been updated with the correct allocation for their direct deposit account they will be shown success screen. From that point it is up to you on where the user will be routed. Some options include a generic Atomic success screen, a custom success screen, or simply route them back into the app.
Linked Account Disconnected
If we cannot run tasks on a user's linked account it will no longer work for continuous access tasks. We will then send a
linked-account-disconnected webhook, which will allow you to prompt your user to reauthenticate. Once the user is authenticated again, we will send out the
linked-account-connected webhook and be able to provide continuous access to the users' data.