Fiat rails & routing
Connect on- and off-ramp providers and payout rails through one routing layer, selected on cost, eligibility, availability, and observed performance, rather than hard-wiring a single provider.
Solutions / Wallets & crypto platforms
Bridge on-chain activity to regulated off-chain flows.
You're already crypto-native. The hard part is everything around the chain: fiat rails for deposits and payouts, settlement and reconciliation against off-chain accounts, and the compliance workflows a regulator expects. OVAAL connects those through one orchestration layer, so on-chain movement and regulated off-chain flows live on a single operational record, routed across eligible providers and rails.
OVAAL is a technology and orchestration platform, not a bank, EMI, or CASP. Regulated services are provided by appropriately authorised customers and third-party providers. Availability depends on jurisdiction, provider approval, and service scope.
What you connect.
Crypto is one rail beneath the control plane. The work that wraps it (fiat, settlement, compliance) is the part OVAAL orchestrates so you don't wire four vendors and own the cross-vendor liability. See how this fits across every solution segment.
Payouts
Send payouts to bank accounts and wallets across eligible rails, with one record that reconciles off-chain confirmations against on-chain movement.
Settlement & reconciliation
Track an instruction from on-chain authorisation through off-chain settlement, exception handling, and reconciliation as one operational record. Near-real-time settlement where the selected provider, destination institution, and jurisdiction support it.
Compliance workflows
Connect KYC, KYB, sanctions, wallet screening, transaction monitoring, and Travel Rule workflows through configurable integrations you operate under your own authorisation.
Policy & automation
Define who or what may initiate a payout or conversion, under which limits and approvals. Every instruction previews, logs, and can be revoked.
Developer platform
Integrate through versioned APIs, SDKs, webhooks, sandbox tooling, and implementation support. Exportable data, with a self-host path on the roadmap.
What we don't do.
- We don't hold custody. If you need a licensed custodian, that role sits with custody providers, not OVAAL. End-user funds stay non-custodial by default; custody, where applicable, is provided by the partner or an authorised provider.
- We don't issue stablecoins. Stablecoin issuers mint; we orchestrate movement and settlement, we don't issue.
- We don't run a licence for you. Crypto-as-a-service providers that hold the licence in their markets are a different model with different economics. You hold the regulated relationship; we are the technology layer.
- We don't ship a consumer brand. Your users see your brand. OVAAL is visible only if you choose to surface it.
No dead-end.
- Versioned APIs with a published deprecation window before any breaking change, so you migrate on your own timeline.
- Exportable data. Wallet addresses, transaction history, routing and policy configuration, and audit logs export on request as signed data.
- Self-host path on the roadmap for partners that need full data residency or air-gapped audit retention.
- Non-custodial by default means end-user funds aren't trapped in our infrastructure. They stay end-user-side, on-chain.
Who owns what.
OVAAL is the technology layer. Your licence owns the regulated relationship. Authorised providers execute the regulated service. We make the split explicit before the first call.
| Activity | Customer (you) | OVAAL | Authorised provider |
|---|---|---|---|
| Regulatory permissions | Primary for your business model | Technology role unless expressly authorised | Primary for the outsourced regulated service |
| KYC / KYB & Travel Rule policy | Policy owner | Workflow orchestration | Verification and screening where contracted |
| Custody of funds | Per your model; non-custodial by default | No, unless expressly authorised | Custody provider where applicable |
| Fiat-rail routing | Oversight and commercial choices | Rules engine | Execution eligibility |
| Settlement & reconciliation | Review and finance ops | Platform record and workflow | Source confirmations |
| Support & complaints | Primary | Technical escalation | Service-specific escalation |
Evaluate the bridge to off-chain.
Book an architecture review and we'll walk through fiat-rail routing, the compliance workflows, the responsibility split, and a realistic integration path. Prefer to read first? The integration brief is a one-page PDF covering modules, the responsibility model, and indicative commercials.