Move money like infrastructure.
Client charged. Worker paid same-day. Your cut taken. Books exact — automatically.
Taking the payment is easy. Everything after it is the mess.
Charging a card is a solved problem. What happens next — splitting the money, paying people, keeping the books straight — is still held together by hand.
Your payout stack is a spreadsheet.
Transfers stitched together by hand, no retries, no paper trail. Every edge case becomes a Slack thread and a manual fix.
Splits break on reality.
Cancellations, no-shows, shorter visits, tips, mileage. Checkout systems weren't built for jobs that change after they're booked.
Bookkeeping surprises find you late.
The bank's numbers and your books disagree — and you find out weeks later, usually from your accountant.
Everything after the client pays.
Card hold → job done → final amount → split → same-day payout → tax slip → balanced books. One flow, handled end to end.
Instant payouts
POST /v1/payoutsWorkers see the money minutes after the job is done — not Friday. Faster pay is the cheapest way to keep your best contractors on your platform.
Splits that handle real life
POST /v1/splits/previewJob cancelled? Client tipped? Visit ran short? The math updates itself — the right people get the right amounts, every time, per your policy.
Tax slips, handled
GET /v1/tax_documentsYear-end slips generated automatically for every worker, taxes withheld correctly all year. January stops being a spreadsheet marathon.
Books that balance themselves
GET /v1/recon/breaksEvery dollar tracked to the penny. If the bank and your books ever disagree, you find out the next morning — not at month-end close.
What would Lezra move for you?
Two numbers. No sales call.
Not technical? This part is for your developers — send it to them.
Idempotent by default. Every event signed, retried, replayable.
Balances derived from entries — never stored, never drifted. Money movement runs on durable workflows; nothing depends on a cron finishing.
Idempotency-Key required on every mutating endpoint1$ curl https://api.lezra.com/v1/payouts \2-H "Idempotency-Key: visit_01J9ZQ8B_payout" \3-d amount=14981 -d currency=cad \4-d destination=acct_ctr_9f2 -d rail=interac56{7"id": "payout_01J9ZR4QK",8"status": "settled",9"settled_in_seconds": 114,10"ledger_entries": ["le_8821", "le_8822"]11}
“The first payments vendor whose ledger our controller didn’t have to shadow in a spreadsheet.”
Simple, usage-based pricing.
A small percentage of the money we move, a small fee per payout, and a monthly platform fee. No setup fees, no minimums for the first ninety days.
Ready to build?
Tell us about your platform. An engineer replies within one business day.
Questions owners actually ask.
No jargon. If something's missing, ask us — a founder answers.
No. Payments run under your brand — workers see your platform’s name on their e-Transfer, clients see your name on their statement.
