Latest / Fintech Conversations with Fexingo: Banking, Payments, and Financial Software Companies / How Fintechs Use Real-Time Payroll Data for Instant Lending
Transcript
- Lucas: So you've worked forty hours this week, but payday is still ten days away. A fintech has partnered with your employer's payroll system, knows exactly how much you've earned in real time, and offers to let you pull a portion of that into your bank account right now — for a flat fee of a dollar fifty or three percent of the amount. Luna: That's earned wage access, and it's become one of the fastest-growing products in fintech over the last three years. Lucas: Exactly. And the key enabler is the API connection between the fintech and the employer's payroll or time-tracking software — companies like ADP, Gusto, or Workday. That real-time data feed is what makes instant lending possible without the fintech taking on credit risk the way a traditional lender would. Luna: Right, because if you're lending against wages already earned, the employer is essentially the guarantor. Default risk is much lower than an unsecured personal loan. Lucas: That's the thesis. And it's a big reason why the earned wage access market is projected to hit around thirty billion dollars in transaction volume in 2026, up from maybe twelve billion in 2023. The largest player, DailyPay, now processes more than one billion dollars in wages annually for employees across retail, healthcare, and hospitality. Luna: And they're not alone. There's also PayActiv, Earnin, and newer entrants like FlexWage. What's interesting is that they all rely on the same technical architecture: an API that pulls real-time worked-hours data from the employer's payroll provider. Lucas: Let's talk about how that API handshake actually works. A company like Gusto processes payroll for small and medium businesses. When an employee clocks out, Gusto records those hours. The fintech connects to Gusto's API, verifies the employee's identity, and requests a snapshot of earned but unpaid wages. The response comes back in seconds — a figure like seven hundred and twenty dollars earned so far this pay period. Luna: Then the fintech deducts its fee and transfers the net amount, often through the real-time payment rails like the RTP network or FedNow. The employee gets the money in minutes. Lucas: The beauty is that the fintech never touches the employer's main payroll run. The transfer is separate — the employer still pays the full amount on payday, and the fintech recoups the advanced amount from the employee's next paycheck. That's a simple mechanism, but it requires tight coordination between three parties: the employer, the payroll platform, and the fintech. Luna: Which brings up the question of who pays for this. In the employer-paid model, the company covers the fee as a benefit — they see it as a tool for employee retention and financial wellness. In the employee-paid model, the worker pays a per-transaction fee. The Consumer Financial Protection Bureau has been watching this closely. Lucas: Yeah, in 2025 the CFPB issued an advisory opinion clarifying that earned wage access products that are truly free to the user — no fees, no interest — are not subject to the Truth in Lending Act. But if a fintech charges a fee, they may need to disclose it as an APR. That's a live regulatory debate right now. Luna: And it matters because the fee structure can make a huge difference in cost. A three-dollar flat fee on a hundred-dollar advance is three percent — but if the employee pays it back in seven days, the annualised rate is over one hundred fifty percent. Lucas: Right. So the optics of earned wage access are better than a payday loan that might charge four hundred percent APR, but regulators want to make sure it doesn't become a new form of high-cost debt. Meanwhile, the technology is evolving fast. Luna: What's next on the product roadmap? We're already seeing fintechs layer on savings features, budgeting tools, and even credit-building reports linked to on-time repayments. Lucas: Exactly. Some are using the payroll data connection to offer small-dollar installment loans for larger expenses — a thousand dollars repaid over three months — using the same income-verification pipeline. The idea is to move beyond just the paycheck to paycheck gap and into broader financial inclusion. Luna: And if these conversations are useful for what you're building or running, I think a lot of listeners feel the same way we do — that this kind of independent analysis is hard to find elsewhere. Lucas: Yeah. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. It really does make a difference. Luna: Totally. So back to the regulatory piece — one of the more interesting developments is that some states are starting to license earned wage access providers as lenders, which could impose interest rate caps. Lucas: California, for example, has a bill that would cap fees on earned wage advances at the equivalent of thirty-six percent APR. That's a big deal because it would force providers to shift from per-transaction fees to a subscription model or employer-paid model. Luna: And we're already seeing that shift. DailyPay recently launched a subscription tier for employees — nine ninety-nine a month for unlimited advances. That's a different risk profile for the fintech because the heavy users become less profitable. Lucas: It's a classic fintech tension: you want to serve the underbanked, but the unit economics only work if you control usage. The payroll API gives you that control in a way that traditional lenders don't have — you can see exactly when the next paycheck is coming and schedule repayment accordingly. Luna: Let's talk about the technology stack a bit more. What does a typical API integration look like for a fintech connecting to a payroll provider? Lucas: Most payroll APIs are RESTful, using OAuth two-point-zero for authentication. The fintech registers with the payroll provider, gets client credentials, and then the employee authorizes the connection — often through a link sent by their employer. Once authorized, the fintech can call endpoints like /employees/{id}/earnings to get year-to-date wages, or /pay-periods/current to see hours worked in the current cycle. Luna: So it's essentially a read-only data pipeline, but it's very data-rich. You get not just hours and pay rates, but also deduction information, tax withholdings, even direct deposit account numbers. Lucas: Which raises data privacy questions. The fintech has to comply with privacy regulations and often signs a business associate agreement with the employer. But the employee's consent is usually broad — they agree to share data in exchange for the service. Critics argue that the consent flow is not always transparent. Luna: And there's an interesting competitive angle. Gusto and ADP have launched their own earned wage access features directly, bypassing third-party fintechs. Gusto's product, called Gusto Wallet, includes instant pay for employees on their platform. Lucas: That's the classic platform play. If you already own the payroll data, why not offer the lending product yourself? It's a natural extension — and it lets the platform capture the fee revenue that would otherwise go to a DailyPay or PayActiv. Luna: So the fintechs that survive will be the ones that offer the best user experience, the best underwriting — even if it's just verification — or the best integration with multiple payroll providers. It's a race to build the broadest network. Lucas: Exactly. And the real opportunity may be in using the payroll data connection to offer not just advances, but a full financial operating system for hourly workers. Think automated savings, bill pay, even insurance products tied to income shocks. Luna: One company I find interesting in this space is Even, which started as a budgeting app and now partners with employers to offer what they call 'instapay' alongside a planning engine that predicts low-income days. Lucas: Even uses machine learning on top of the payroll data to forecast cash flow gaps. That's a step beyond just pulling current earnings — it's proactive. They'll say, 'based on your past twelve pay periods, you're likely to be short next Tuesday, so here's a suggested advance amount.' Luna: That kind of predictive capability is possible because the payroll data is structured and consistent. Compare that to a traditional bank trying to underwrite a small loan with only a credit score and bank transaction history — the payroll API gives you a much clearer picture of income stability. Lucas: And that's why I think we'll see more partnerships between payroll platforms and fintechs that go beyond earned wage access. You could imagine a lending product that uses payroll data to offer lower rates to workers with consistent hours, or a retirement savings product that auto-escalates contributions based on pay raises detected in the data. Luna: The infrastructure is there. The API connections are standardized. The regulatory framework is still being written, but the direction is clear: real-time payroll data is becoming a core utility for fintech. Lucas: And it's a reminder that the most interesting fintech innovations are often the ones that sit underneath the user interface — the data pipes, the verification layers, the integration between systems that were never designed to talk to each other. Luna: Yeah. Ten years ago, getting a hundred-dollar advance meant a payday loan storefront. Today, it's a tap on your phone, backed by a real-time API to your employer's payroll system. That's a pretty big shift. Lucas: It really is. And I think we're only at the beginning of what that data connection can enable. Luna: For now, thanks for listening to Fintech Conversations with Fexingo.