Provider directory · Use case
Income and employment verification
16 of the 24 providers assessed document income and employment verification in their own public documentation. 0 publish nothing that answers it; the rest do not offer it.
- Direction
- Read
- What it needs from payroll
- Employer, job title, start date, pay rate, and gross and net income history.
- Typical buyers
- Lenders, landlords, background screeners, public-benefit programmes.
Providers that document it
| Provider | Value | Conf | What the documentation says |
|---|---|---|---|
| Apideck Employer-permissioned unified APIs | Data — jobs + compensations | D | Employee has employment_start_date, jobs (title, start_date) and compensations (rate, payment_unit, currency). No income-verification use case is marketed. Source |
| Argyle Consumer-permissioned payroll APIs | Yes — Payroll VOIE + identities | D | The /identities resource includes employment_status, job_title, hire_date, original_hire_date, base_pay and pay_cycle; /employments links records per job. Source |
| Atomic Deposit and account switching | Yes — Verify | D | Verify lets you 'Verify a user's income, employment status, and identity'; employment data includes employmentStatus, jobTitle, startDate, payCycle, weeklyHours and employer. Source |
| Bindbee Employer-permissioned unified APIs | Data — compensation | D | Compensation has pay_rate, pay_period, pay_frequency, pay_currency, flsa_status, pay_group and start_date. No income-verification use case is marketed. Source |
| Experian Verify Verification databases | Yes — API (Plus/Premium/Core) | D | Verify Premium 'Returns the two most recent payroll records found ... within the last 90 days and the last payroll record from every employer found within the current year and two previous calendar years'; Verify Core returns the most recent employment record within 90 days. Field names are not published. Source |
| Finch Employer-permissioned unified APIs | Data — employment + income | D | The Employment endpoint ('Read individual employment and income data') returns title, start_date, income and income_history, in the unit the provider reports. No income-verification use case is marketed. Source |
| Knit Employer-permissioned unified APIs | Data — employee + compensation | D | The employee model includes employment details and an employee_compensation model with fixed, variable and stock items. No income-verification use case is marketed. Source |
| Kombo Employer-permissioned unified APIs | Data — employments | D | Employments return job_title, pay_rate, pay_period, pay_frequency, pay_currency, employment_type and effective_date. No income-verification use case is marketed. Source |
| Merge Employer-permissioned unified APIs | Data — Employment model | D | Employment includes job_title, pay_rate, pay_period, pay_frequency, pay_currency, flsa_status, effective_date and employment_type. No income-verification use case is marketed. Source |
| Pinwheel Deposit and account switching | Yes — Verify (employment, income) | D | /v1/accounts/{account_id}/employment and /income return employer_name, title, status, start_date, end_date, compensation_amount, compensation_unit and pay_frequency; Verify also produces VOE/VOIE reports. Source |
| Plaid Consumer-permissioned payroll APIs | Yes — Payroll Income | D | /credit/payroll_income/get returns income; /credit/employment/get (beta) returns status, start_date, end_date, employer.name and title. Plaid states most new customers should use Consumer Report Income instead. Source |
| SteadyIQ Income Passport Consumer-permissioned payroll APIs | Yes — JSON/PDF income report | D | The JSON schema includes employer, jobTitle, originalHireDate, mostRecentStartDate, basePay, payFrequency, employmentType and status; reports are fetched via the /income/user endpoint. Source |
| The Work Number Verification databases | Yes — VOE / VOIE | D | The product page lists Basic Employment ('Company Name, Job Title, Hire Date'), Income Details ('Base Pay, YTD Earnings, Overtime, Bonus') and 'Up to 36 months of pay history', delivered via REST API, batch SFTP or web portal. Source |
| Truework Verification databases | Yes — API (orders/reports) | D | Reports via /reports/{verification_report_id}; position objects include title, start_date, end_date and employment_type; salary includes pay_rate, pay_frequency and hours_per_week; yearly earnings break out base, overtime, bonus, commission and total. Source |
| Truv Consumer-permissioned payroll APIs | Yes — Income & Employment | D | The Employment object includes job_title, start_date, original_hire_date, end_date, income, income_unit, pay_rate and pay_frequency. Source |
| Unified.to Employer-permissioned unified APIs | Data — employee model | D | Employee has title, hired_at, employment_status, employment_type and compensation (type, amount, currency, frequency). A separate Verifications API routes to verification vendors, which is not payroll data. Source |