Who we serve
OZAV for social & messaging apps
Turn conversations and feeds into money movement — embedded wallets and P2P your users actually keep.
What you build on OZAV.
Composed from live primitives — accounts, payments, and FX — through one API.
Native wallets
Branded dollar wallets inside the feed or the chat.
In-app P2P
Send and receive value in a post or a message, instantly.
Branded balances
Balances and activity shown under your brand.
Compliant P2P
KYC, AML screening, and Travel Rule run on every transfer.
Capabilities you'll use
Social and messaging apps own the audience. Then the payments leave for banks and processors.
Built for developers
Onboard your users 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 social & messaging apps 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 social & messaging apps 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.