Checkr acquired a company most people haven’t heard of.
Quick context.
Checkr runs background checks – the same type an employer runs on a job applicant, or a landlord runs on a prospective tenant.
Truv, the company they just acquired, solves a different problem: it verifies your income and employment by connecting directly to your payroll provider. No individual, pdf format pay stubs., Truv checks your actual payroll data via API and confirms your income directly..
Apparent Strategic Thesis
Checkr wants a faster, frictionless and more accurate verification process for its mortgage applications.. That wouldn’t be wrong, Fannie Mae says income misrepresentation accounts for roughly half of the fraud it catches.
Combine Truv with Checkr, and a lender can verify income in seconds instead of trusting slower and less accurate PDF ingestion and lackluster OCR reliability – more reliable, faster, and now handled within a single platform.
My Thesis.
After reading more about Truv, I noticed they already work with state governments. State agencies use Truv to check whether someone applying for Medicaid or food stamps is telling the truth about their income.
So now there are two very different customers for the same product: financial institutions, who want to avoid lending money to people who misrepresent their income on mortgage applications, and state governments, who want to prevent sending benefit checks to people who falsify their income on a form.
Same verification. Same technology. Two completely different end markets.
$186 Billion.
That’s what the GAO estimates the federal government made in improper payments last year, before counting what states lost on top of it. Not fraud, exactly. Just money sent to the wrong place because nobody checked properly.
So the mortgage story isn’t wrong. It’s just one part of a much larger one.
Checkr didn’t buy Truv just to make mortgages faster. That’s the surface story. The real strategy is bigger. It’s positioning the new combined entity as the verification layer for any organization that approves a payout based on claimed income (a bank underwriting a mortgage, a state agency approving benefits) and absorbs the loss when that claim turns out to be false/misrepresented.
The Significance of the Data Sharing Mechanism.
All of this runs on what the industry calls “consumer-permissioned data.” You, the individual, log into your own payroll account through Truv and authorize the release. Legally, that’s real… it’s not scraping, and Truv is FCRA-compliant, which comes with actual consumer rights – you can request your file, dispute it, flag fraud on it, etc…
You can call that a free choice but if you don’t authorize the share, you might not get the mortgage. You don’t get the apartment. You don’t get the benefit. Nobody’s forcing your hands onto the keyboard, but “consent or don’t get what you need ” isn’t really a choice. This isn’t new either. You handed over a pay stub before Truv existed. What is new is how deep the access goes once you say “approve”. A pay stub is a one time verification step with limited information. Providing perpetual API access to a payroll platform is rolling permission for them to access your entire income history in perpetuity
The consent you provided didn’t get more voluntary…what you consented to got much bigger
Written by Camila Cimirro, Associate
