Who we serve
OZAV for payment processors & PSPs
Settle in stablecoins and pay out across borders — a dollar layer for your processing stack.
What you build on OZAV.
Composed from live primitives — accounts, payments, and FX — through one API.
Stablecoin settlement
Settle merchant funds into dollar balances in real time.
Cross-border payouts
Disburse to PIX, SPEI, SEPA, ACH, Wire, or stablecoins from one balance.
On/off-ramps
Add local on- and off-ramps without holding the float yourself.
Reconciliation
Every settlement matched to source with signed webhooks.
Capabilities you'll use
Processors move the payment. Then settlement waits days and stops at the border.
Built for developers
Onboard your merchants 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 payment processors & PSPs 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 payment processors & PSPs 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.