# Consumer-Permissioned Verifications: What They Are & Why They Matter

## Introduction
Income, employment, and asset verifications have long been a burden for both applicants and the organizations that serve them. Whether someone is applying for a mortgage, rental housing, or government benefits like Medicaid or SNAP, proving income, employment, and assets typically means one of two things: tracking down paystubs, W-2s, bank statements, and other documentation or relying on a verification database like The Work Number.

Consumer-permissioned data—also known as consent-based verification (CBV)—is changing that dynamic. By putting individuals in control of their own information, this approach streamlines verification, reduces costs and administrative burden, and creates a more transparent, ethical system for data sharing.

## What is consumer-permissioned (consent-based) data?
Consumer-permissioned data is information that individuals actively authorize others to access. Rather than having their data bought, sold, or shared without their knowledge, individuals decide when, how, and with whom their personal information is shared.

## How consumer-permissioned (consent-based) verifications work
The consumer-permissioned verification model follows a straightforward process:

- **Active consent:** The applicant selects their employer, payroll provider, or financial institution from a comprehensive database and logs in using their existing credentials—the same ones they use to view their paystubs.
- **Secure connection:** Once authenticated, a secure API connection is established between the employer, payroll provider, or financial institution and the service provider or government agency.
- **Direct data transfer:** Income, employment, and/or asset information flows directly from the source to the authorized service provider in real time, eliminating the need for manual document collection.
- **Ongoing control:** The applicant can monitor which service providers have access to their data and revoke permissions whenever they choose.

## Consumer-permissioned (consent-based) verifications vs. traditional database methods
Traditional verification databases work by buying and aggregating employment and income data from employers and payroll providers, and then making it available to service providers for a fee. This creates several problems:

- **Lack of transparency:** Applicants typically don't know their data has been collected, who has access to it, or how it's being used.
- **Limited coverage:** Database providers only have information from participating employers. The Work Number, for example, has significant coverage gaps—particularly for gig workers, small business employees, and federal government workers.
- **Data staleness:** Information in databases may be weeks or months old, leading to inaccurate verifications that can delay approvals or result in wrongful decisions.
- **High costs:** The buy-and-sell model makes traditional database verification reports expensive.
- **Privacy concerns:** The practice of buying and selling applicants’ personal data without their knowledge has drawn criticism from consumer advocates and regulators, including the Consumer Financial Protection Bureau (CFPB).

### The consumer-permissioned (consent-based) approach
Consumer-permissioned verifications solve these problems through direct-source connections that applicants knowingly and voluntarily consent to:

- **Transparency:** Individuals know exactly what information they're sharing, with whom, and for how long.
- **Coverage for more income types:** They can access data for a much broader range of applicants—including those who work in the gig economy.
- **Real-time accuracy:** Data comes directly from the source in real time.
- **Lower costs:** Consumer-permissioned verification is significantly more cost-effective than traditional database methods.
- **Ethical data practices:** Individuals' data is never bought, sold, or stored indefinitely.

## The benefits of consumer-permissioned, consent-based verifications
The shift to consumer-permissioned data creates advantages for everyone involved in the verification process:

- **Faster, easier process for applicants:** They can complete verification in minutes.
- **Dramatic operational improvements for service providers:** Lower costs and higher accuracy lead to faster processing times.

## Addressing common concerns
### "Do applicants even know their payroll passwords?"
Leading consumer-permissioned verification platforms like Argyle offer several solutions to ensure high conversion rates regarding password knowledge:

- **Passwordless login:** Many payroll systems now support login using personal characteristics.
- **Single sign-on (SSO) integration:** Argyle supports many SSO providers.
- **Password manager compatibility:** Argyle integrates seamlessly with password managers.
- **Built-in password reset:** Enables users to reset their password without leaving the verification experience.
- **Document upload as fallback:** For users who cannot connect digitally, options for document uploads are available.

### "What if someone doesn’t want to connect their accounts?"
Consumer-permissioned verification is always voluntary. Individuals can still submit traditional documentation if they choose not to connect their accounts.

### "What happens to an applicant’s data after verification?"
Reputable consumer-permissioned platforms have clear data retention and deletion policies. With Argyle, consumer data is made available to service providers for 30 days after the service agreement ends, and then it's permanently removed from servers.

## The future of verification
Consumer-permissioned data represents the future of income and employment verification—where transparency, accuracy, and individual control are the standard. The question isn't whether to adopt consumer-permissioned data, but when. Organizations that move early will begin reaping the benefits sooner.