Your app. Your brand. Earned wages, on demand.
OpenEWA is the API and infrastructure that lets payroll, HR, and workforce platforms embed instant access to earned pay directly in their own product. You build the experience your users already trust. We provide the capital, the banking rails, the compliance, and the deduction logic that make it work.
Why partners embed EWA
Earned wage access turns workforce platforms from a utility employees check occasionally into a tool they open every day.
A new recurring revenue line
Share in transaction-fee revenue from day one of launch. No fixed integration fees, no separate billing pipeline — revenue accrues automatically against the same volume your platform already drives.
Daily engagement, not weekly
Users check schedules weekly. They check balances daily. EWA shifts the platform from a utility into a financial tool, raising session frequency, retention, and LTV across your existing customer base.
A category-leading RFP answer
Win T&A and payroll RFPs by including financial wellness out of the box. No third-party redirect, no co-branded screen — your buyers see one product, branded their way.
A clean split of responsibilities
Each side owns what they do best. Keeper carries the financial and regulatory weight; partners own the experience their employees see.
The native experience
- • Balance and Cash Out screens, embedded in your existing app
- • Real-time shift / time data sent to OpenEWA on clock-out
- • Retroactive adjustments pushed when past shifts change
- • Above-the-fold placement of Cash Out so employees actually use it
The engine
- • REST API, webhooks, and SDKs for balance, cashout, and deductions
- • Capital, Merchant-of-Record status, and 50-state regulatory licensing
- • RTP, ACH, and instant-to-debit money movement
- • Deduction file generation, rollover logic, and L2/L3 technical support
Built for the people doing the integration
A REST API designed the way you wish more vendors did. Predictable resources, idempotent writes, signed webhooks, and a sandbox you can reset on demand.
One canonical resource model
Partner → Employer → Office → Employee → Shift, with Disbursements and Deductions as the money-movement objects. Per-office config inheritance handles multi-region employers without forking the schema.
Signed, replayable webhooks
At-least-once delivery with exponential backoff and a partner-facing event log. Replay any event with a single API call when your downstream had an outage.
Auth that fits both worlds
Bearer API keys (separate live and test prefixes) for backend-to-backend traffic. OAuth 2.1 with PKCE for agents, IDE copilots, and other interactive clients.
Live Try-It on every endpoint
Paste a test key into the docs and call the sandbox from your browser. See the full request, the response, and the equivalent curl — without leaving the page.
OpenAPI 3.1 spec, end to end
The reference, the SDK types, and the Postman collection are all generated from one specification. What you read in the docs is what your code calls.
Sandbox-first development
Test keys hit an isolated sandbox with mocked money movement and a fast clock so you can walk a deduction from scheduled to paid in seconds.
Get to your first cash out in under an hour
The quickstart walks from issuing your first key to a fully reconciled deduction — twelve steps, every one with a live Try-It panel.