Self Service Embedded Setup guide

With Self Service Embedded Setup, your customers are empowered to complete the Setup process themselves by submitting all of the required information about their company, workers, and pay history directly from your product. Our suite of pre-built components and APIs provide all of the building blocks you need to create an end-to-end Service Service Embedded Setup flow for your customers.

If you’re interested in Check handling the Setup process on behalf of your customers, check out our Guide to Full Service Embedded Setup.

Please note, implementation of a switcher company using Self Service Embedded Setup (usage of the pay history component) is a billable event.

The most important factor dictating when Self Service Embedded Setup should be used is whether the customer is an inception company or a switcher company.

Inception companies are those that have never run payroll before, switchers are everyone else. While switchers have the option of choosing Full Service Embedded Setup to help navigate migrating historical payroll information, inception companies are required to leverage Self Service Embedded Setup.

Switchers are not required to go through Full Service Embedded Setup. While it is recommended for larger, more complex companies, it is entirely possible to empower your smaller, simpler switchers to self-serve.

The more complex a company is, the more difficult self-serving will be. Generally speaking, companies that may be good candidates for Self Service are those with:

We recommend sending all companies that do not fit these criteria to Full Service Embedded Setup to optimize conversion.

With the above in mind, there are two approaches you can take to productizing Self Service:

The first option is the most simple: send all incoming switcher companies through Full Service Embedded Setup. This is the most straightforward option for a couple reasons.

While all switcher companies are eligible for Full Service Embedded Setup, you may want to route a subset of these companies through a Self Service flow.

This approach reduces costs, but comes with the risk of lower conversion due to the added burden placed on the customer. We recommend only sending switchers with 10 or less workers through Self Service Embedded Setup.

Information about a company’s authorized signatory is needed by Check for filing purposes. A signatory can be created by making an API request to the /signatories endpoint. Once created, the signatory ID will be passed as a parameter to certain components including the Full Service Setup Submission Component.

For a company to run payroll on Check, they must agree to Check’s Terms of Service and provide both debit and filing authorization to Check. This can be done through a combination of two components.

Once the signatory has been created, the customer is routed through either the Full Service Setup Submission Component or the Business Details Component, depending on which approach you’ve chosen.

Full Service Submission

If all switchers will be sent through Full Service Embedded Setup, start by routing all customers through the Full Service Setup Submission Component.

This component gathers all of the information required to determine whether to submit a company for Full Service Embedded Setup, including whether or not the company has paid people before.

As soon as the customer indicates they are an inception company, which is not eligible for Full Service, the component will emit the check-component-new-to-payroll-indicated SDK event, display a loading screen, and rely on your system to respond to the event. At this point, you should close the Full Service Submission Component and render the Self Service Embedded Setup flow described in the following step.

Explore our documentation for more information on working with components and SDK events.

Business Details

If a subset of smaller, simpler switchers will be sent through Self Service Embedded Setup, start by routing customers through the Business Details Component. This component guides the customer through providing basic information about their company.

As the customer goes through the component, key fields will be updated on the company enrollment profile which can be used to determine whether a company should be sent through Full Service or Self Service Embedded Setup. These key fields include:

Once the customer has finished providing their basic information, the Business Details Component will emit the check-component-business-details-complete SDK event. This is your cue to check the enrollment profile, determine the right Setup method, close the Business Details Component, and route the customer either to the Full Service Setup Submission Component or the Self Service Embedded Setup flow described in the following step.

As mentioned, a good rule of thumb is to send any switcher with more than 10 workers through Full Service Embedded Setup.

At this point, the company will have already provided basic business details and signed the necessary signatory agreements via the Full Service Setup Submission or Business Details Component.

The following components can be rendered sequentially to walk a company through the rest of the Self Service Embedded Setup process.

Note: Given that inception companies have no pay history to migrate, the Pay History Component should only be rendered for switcher companies.

At this point, the company has provided all required information, and can submit themselves for final review by Check.

A company going through Self Service Embedded Setup can submit themselves to Check via the /start_implementation endpoint. This will allow Check to review the information submitted before confirming the company is ready to run their first payroll.

After the company submits, Check may request specific documentation if there is additional information needed from the company to complete the review. The Verification Documents Component can be used to surface these requests and allow the company to provide the necessary documents. To generate the component, make an API request to the /components/verification_documents endpoint.