Who we serve
OZAV for neobanks & digital banks
Add multi-currency named accounts, FX, and global payments to your bank — no new license, no core migration.
What you build on OZAV.
Composed from live primitives — accounts, payments, and FX — through one API.
Named accounts
Give every customer branded account details in USD, EUR, BRL, and GBP.
Cross-border & FX
Move between USD, BRL, MXN, and EUR on instant rails, with transparent FX.
Cards & spend
Issue branded debit cards tied to dollar balances.
Embedded compliance
KYC/KYB, AML screening, and monitoring run inside your flow.
Capabilities you'll use
Neobanks win the everyday account. Then the dollar, the cross-border, and the card program go to someone else.
Built for developers
Onboard your customers 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 neobanks & digital banks 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 neobanks & digital banks 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.