Direct Deposit APIs Fueling Neobanks
Pinwheel, Argyle, Atomic, and the direct deposit switching APIs funding $10T to neobanks
These APIs turned payroll login into a customer acquisition weapon for neobanks. Instead of asking a user to print a form, call HR, and wait for the next pay cycle, a bank can drop a payroll search box into onboarding, let the user log into ADP or Gusto, and rewrite where wages land. That matters because direct deposit customers are far more valuable, and the same connection can also power income verification, underwriting, and earned wage access.
-
The hard part is not just moving money, it is standardizing thousands of messy payroll systems. The employment stack is more fragmented than banking, with around 6,000 HR and payroll systems in the U.S., and many still run through CSVs, SFTP files, and custom connectors behind the scenes.
-
Pinwheel, Argyle, and Atomic sit on the consumer side of payroll connectivity. They connect one worker to one payroll account, then let a bank or lender read pay data and write changes like direct deposit routing. Finch sits one layer lower, helping software companies connect to employer systems in bulk.
-
The strategic prize is not the switching flow itself, it is owning the paycheck. Pinwheel describes direct deposit as the top of a consumer's flow of funds, and Chime and Cash App show why. Once wages land in the app, the company gets more spend, more data, and a better base for lending and other products.
Going forward, payroll connectivity will matter less as a standalone feature and more as the first rail in a broader financial stack. The winners will use that first paycheck connection to layer on lending, savings, bill pay, and other products, while payroll platforms themselves push further into wallets and banking to keep that value inside their own ecosystem.