Provider directory · Use case
Earned wage access
14 of the 24 providers assessed document earned wage access in their own public documentation. 1 publishes nothing that answers it; the rest do not offer it.
- Direction
- Read
- What it needs from payroll
- Hours and earnings to date, pay schedule, and how fresh the data is before pay date.
- Typical buyers
- EWA providers, employers offering on-demand pay.
Providers that document it
| Provider | Value | Conf | What the documentation says |
|---|---|---|---|
| Apideck Employer-permissioned unified APIs | Data only | D | Employee Schedules and Employee Payrolls are available; no EWA use case is marketed. Source |
| Argyle Consumer-permissioned payroll APIs | Yes — EWA Link flow | D | 'Earned wage access' is listed among Link solution flows; the gig and workforce data covers shifts and pay, and paystubs include hours and hours_ytd. Source |
| Atomic Deposit and account switching | Pay-period fields | D | Income data includes nextExpectedPayDate, currentPayPeriodStart/End and unpaidHoursInPayPeriod ('hours the employee has worked in the current pay period which are to be paid out in the next pay cycle'), plus timesheets. Source |
| Bindbee Employer-permissioned unified APIs | Data only | D | Timesheet Entry, Payroll Run Calendar and Pay Group models; no EWA use case is marketed. Source |
| DailyPay Earned wage access providers | From timekeeping reports | D | Earnings come from 'automated earnings reports from your timekeeping system'; the remainder is paid on payday as 'Remainder Pay'. Source |
| EarnIn Earned wage access providers | From bank deposit history | D | 'Your daily earnings amount is your average direct deposit amount divided by the number of days in the pay period', up to a Pay Period Max; repaid by debit from the linked bank account. Source |
| Finch Employer-permissioned unified APIs | Yes — marketed | D | The Financial Wellness page lists 'Earned Wage Access: Use payroll data to calculate available wages and deliver responsible cash advances to employees.' Source |
| Knit Employer-permissioned unified APIs | Yes — marketed | D | 'HRIS Integrations for Earned Wage Access (EWA) Platforms': 'Calculate available wages in real time, initiate instant payouts, automate deductions'. Source |
| Kombo Employer-permissioned unified APIs | Data only | D | GET /hris/timesheets returns payable_hours, breaks and approval_status for a listed subset of systems; no EWA use case is marketed. Source |
| Merge Employer-permissioned unified APIs | Data only | D | TimesheetEntry has hours_worked, start_time and end_time; PayGroup and pay_frequency are available. No EWA use case is marketed. Source |
| Payactiv Earned wage access providers | T&A data; repaid by deduction | D | 'Accessible balance is generally 50% of estimated net wages, which Payactiv calculates as 80%-90% of gross pay', repaid through payroll deduction. Source |
| Pinwheel Deposit and account switching | Yes — marketed EWA solution | D | Provides EWA providers 'employment status, current income, accrued earnings to date, and direct deposit allocation', plus pay frequency, next pay date and change alerts; a Shifts endpoint is documented. Source |
| Plaid Consumer-permissioned payroll APIs | Marketed — bank data | D | The EWA use-case page markets viewing 'income, pay cycles, and balances instantly' from bank-account data (Transactions, Balance, Auth), not payroll hours or earnings to date. Source |
| Unified.to Employer-permissioned unified APIs | Data only | D | Timeshift has hours, start_at, end_at, is_approved and compensation; no EWA use case is marketed. Source |
Providers where it is unverified
We looked and the provider publishes nothing that answers it. That is not the same as the capability being absent.
| Provider | What a correct answer needed |
|---|---|
| Truv | Pay statements carry hours and employment carries pay_frequency, but no EWA use case is documented and the former EWA product URL redirects to a public-sector wage verification page. |