Product updates

We have introduced increased validation when a company submits EINs and account numbers. An employer will now be unable to submit a string containing a single repeated alphanumeric character into these fields, such as '11111' and 'aaaaa.' This validation helps to reduce failed tax filings due to invalid EINs and account numbers.

We have started automatically sending companies through the enrollment process in sandbox. When the /start_implementation endpoint is hit, or you “confirm and submit” in Console, assuming all other validations are complete, the company will automatically have their implementation status set to “complete." This change enables you to build automated testing and QA against our sandbox environment for the Enrollment process.

When you confirm and submit in Console, or hit the /start_implementation endpoint, we will now start requiring the company’s start date to be in the future of the current date. Read our docs for more information on validations around submitting to Check.

We have now released deterministic sandbox testing for the bank account API. By sending specific values in the routing number, your system can simulate different bank account verification statuses including validated, disabled_recoverable and disabled_irrecoverable. Testing bank account statuses enables you to build integration testing and QA testing around bank accounts. Learn more in our docs.