Who we serve
OZAV for on-demand platforms
Settle with drivers, couriers, and workers the moment a job ends — in local currency, dollars, or stablecoins.
What you build on OZAV.
Composed from live primitives — accounts, payments, and FX — through one API.
End-of-job settlement
Pay the instant a job completes, programmatically.
Worker wallets
Each worker gets a branded account that holds and spends.
Local or stablecoin
Pay in local currency or stablecoins, their choice.
API-triggered
Fire payouts from your dispatch flow.
Capabilities you'll use
On-demand platforms move the money. Then the worker cashes out and the relationship ends.
Built for developers
Onboard your workers with one POST /customers call — idempotent, typed, and webhook-backed. Sandbox, TypeScript SDK, and docs from day one.
Read the docs# Onboard a user and open an account POST /customers { "name": "Maria Silva", "country": "BR", "currency": "USD" } → 200 OK { "id": "cus_8f2a…", "kyc_status": "verified", "wallet": "0x9e3…b21", "balance": 0 }
Security & controls
Every action on on-demand platforms runs on regulated infrastructure, with controls that satisfy compliance from day one.
Authorization required
No unilateral movement of funds — every privileged action is explicitly approved.
Expiring approval sessions
Approvals expire by default, limiting blast radius, with instant revocation.
Approval & per-transaction limits
Approval workflows plus per-transaction limits on external crypto transfers.
Tenant data isolation
Each client's data is isolated end to end with row-level security.
Compliance built in, not bolted on.
Compliance for on-demand platforms is part of the flow — KYC, KYB, AML screening, transaction monitoring, and Travel Rule support come standard, so you grow without owning the regulatory overhead.