Branch announced on October 14 that it is selling a white-label earned wage access product to banks and credit unions. I read the announcement next to the CFPB’s December 2025 advisory opinion, and my view is that any bank adding this product should test it against the four criteria in that opinion before it puts its own name on the screen.
What the announcement says
According to the Branch release, Flex EWA for financial institutions lets a bank or credit union embed earned wage access in its own app, under its own brand, while Branch funds the advances and oversees compliance. The release says institutions take on no balance-sheet risk and need no new underwriting, and that a launch runs through a 60-day sprint covering integration, testing, certification and go-live. Depositors choose instant delivery to a debit card for a small fee or standard delivery at no cost.
Atif Siddiqi, founder and CEO of Branch, said in the release: “Earned wage access has become a baseline expectation for today’s workforce, and increasingly people expect it from the institutions they already bank with.” The release also says Branch is not a bank and acts as a technology service provider and program manager for Lead Bank, Member FDIC.
Advertisement
Those are sales points about risk and speed. Banks also need an answer on legal classification, and that answer sits in a different document.
What the CFPB opinion requires
On December 23, 2025, the CFPB issued an advisory opinion on Regulation Z and earned wage access. It treats a defined category it calls “Covered EWA” as outside the definition of credit, and it says fees tied to Covered EWA cannot be finance charges. A product qualifies only if it has all of the following characteristics:
- Transactions do not exceed the accrued cash value of the wages the worker has earned, determined from payroll data.
- The provider recovers the amount through a payroll process deduction at the worker’s next payroll event.
- Before providing the advance, the provider explains to the worker, and warrants in the contract, that it has no legal or contractual claim against the worker if the deduction falls short, and that it will not engage in debt collection or credit reporting.
- The provider does not assess the credit risk of individual workers, including through credit reports or credit scores.
The opinion also describes what falls outside the category. A provider that debits a worker’s regular transaction account after wages arrive is not using a payroll process deduction. The CFPB says it continues to seek feedback on whether other EWA products are credit, so the status of products outside Covered EWA is still open.
The strongest objection
A bank’s compliance officer could reasonably answer that none of this is the bank’s problem. Branch funds every advance, the bank carries no credit exposure, and the CFPB’s current position is friendly to earned wage access. The market is large enough that regulators have paid attention: the CFPB’s opinion cites a 2024 agency estimate that employer-partnered EWA grew from $3.2 billion across 18.6 million transactions in 2018 to $22.8 billion across 214 million transactions in 2022.
That objection covers credit risk and leaves classification untouched. The product appears inside the bank’s app, under the bank’s name, and depositors will judge the bank by how it treats their pay. The Branch release mentions employer payroll connections but does not say how advances are repaid or what happens when a paycheck comes up short. Those facts decide whether the criteria above are met. They are also facts a vendor can state in one paragraph of a contract.
States add a second layer. A Washington Senate bill report on SSB 5328 describes a licensing framework that defines consumer-directed services as loans and limits fees from employer-integrated services to $10 a month. I cannot tell from the bill report whether that text became law. A bank buying a nationwide product should ask the same question state by state.
What I would ask before signing
A bank that wants earned wage access to hold deposits, which is the case the release makes, can start with a short list of written answers from the vendor:
- How each advance is recovered, and whether recovery runs through the employer’s payroll or through a debit of the depositor’s account.
- Which of the four Covered EWA criteria the vendor says the bank-branded product meets, and in which contract clause it warrants them.
- What happens to a depositor whose paycheck is short, and who is allowed to contact them.
- Which states the vendor’s legal analysis covers, and what changes if a state treats the product as a loan.
For the wider pattern of compliance claims arriving before the rulebook, see our opinion piece AI Lending’s Compliance Pitch Is Missing Its Rulebook. For banks buying capability to win deposits, see Banks Now Buy Fintechs for Deposits and Engineers.
A 60-day launch is attractive. A bank can match it by spending the first week on the four questions above and recording the answers before the integration work starts.
Source: Branch via PR Newswire
