Financial infrastructure for the AI era

Launch programmable accounts. Move money. Govern every transaction.

OVAAL is a neutral control plane for programmable financial products. One modular layer runs accounts and wallets, money movement and routing, settlement, reconciliation, and the policies that govern every transaction. Brokers, EMIs, wallets, marketplaces, and AI-native platforms build on it under their own license.

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.

Human Business Agent · roadmap Identity · Permissions · Policy · Approvals OVAAL CONTROL PLANE Accounts Wallets Routing Ledger Reconciliation Audit instruction → execution → settlement → receipt Banks · Payment rails · Digital-asset rails
API-first Provider-neutral Policy-controlled Multi-rail Audit-ready

One control plane between your product and the providers that execute.

Financial products shouldn't be hard-wired to one provider, one wallet stack, one payment rail, or one compliance vendor. OVAAL sits in the middle, so your team controls the experience while authorised providers and rails do the regulated work.

Initiators

People, businesses, and (on the roadmap) software agents that ask to move or manage money.

Governance

Identity, permissions, policy, and approvals decide what each initiator is allowed to do.

OVAAL control plane

Accounts, wallets, routing, ledger, reconciliation, and audit, kept as one operational record across every provider.

Execution

Authorised providers, banks, payment rails, and digital-asset rails settle the actual money movement.

Six modules. One integration.

Adopt the whole control plane or the modules you need. Providers and rails plug in beneath each one.

Available

Accounts & Wallet Orchestration

Human and business accounts with unified identity, permissions, delegated access, and recovery. The first rail today is ERC-4337 smart-contract wallets with passkeys and gasless flows.

Accounts & wallet orchestration →
Available

Money Movement & Routing

Route deposits, transfers, conversions, and payouts across eligible providers and rails using cost, eligibility, availability, and observed performance.

Money movement & routing →
Available

Settlement & Reconciliation

Track an instruction from authorisation through execution, settlement, exception handling, reconciliation, and receipt, as one record your finance team can audit.

Settlement & reconciliation →
Available

Policy & Automation

Define who or what may initiate a financial action, under which conditions, within which limits, and with which approvals. Every rule previews before it runs.

Policy & automation →
Available

Risk & Compliance Orchestration

Connect KYC, KYB, sanctions, wallet screening, transaction monitoring, and Travel Rule workflows through configurable integrations you operate under your own authorisation.

Risk & compliance orchestration →
Available

Developer Platform

Integrate through versioned APIs, SDKs, webhooks, sandbox tooling, and implementation support. Exportable data and a self-host path on the roadmap.

Developer platform →

Every instruction, from request to receipt.

One operational record follows each financial action through its whole life. Fewer manual steps, and the evidence is there when an auditor asks.

Instruction Policy check Execution Settlement Reconciliation Receipt
Roadmap: design partners

Ready for agent-initiated finance.

The same governance that controls human and business actions extends to software agents. An agent can initiate a financial action only inside policies, permissions, limits, and approval rules you define. Every instruction is logged, reviewable, and revocable.

Today, policy and automation are live for human- and business-initiated flows. Fully agent-initiated finance is in design with early partners. We mark it as roadmap rather than claiming autonomy we haven't shipped.

Built for the platforms that move other people's money.

Brokers & trading platforms

Funding, withdrawals, client wallets, multi-provider routing, and one reconciliation view, instead of fragmented rails and manual ops.

Brokers & trading platforms →

EMIs & neobanks

Add programmable wallet and digital-asset capability through a controlled layer, without rebuilding your control and reporting infrastructure.

For EMIs & neobanks →

Wallets & crypto platforms

Connect fiat rails, payouts, and compliance workflows, bridging on-chain activity to regulated off-chain flows.

For wallets & crypto →

Marketplaces & digital platforms

Coordinate accounts, payouts, approvals, and reconciliation across many participants and service providers.

Marketplaces & platforms →
Roadmap

AI-agent platforms

Give agents scoped access to financial actions (policy, limits, approvals, audit, revoke) without unrestricted authority over funds.

AI-agent platforms →

Who owns what.

OVAAL is the technology layer. Your license owns the regulated relationship. Authorised providers execute the regulated service. We make the split explicit before the first call.

ActivityCustomer (you)OVAALAuthorised provider
Regulatory permissionsPrimary for your business modelTechnology role unless expressly authorisedPrimary for the outsourced regulated service
KYC / KYB policyPolicy ownerWorkflow orchestrationVerification where contracted
Safeguarding / custodyDepends on modelNo, unless expressly authorisedPrimary where applicable
Routing configurationOversight and commercial choicesRules engineExecution eligibility
Settlement & reconciliationReview and finance opsPlatform record and workflowSource confirmations
Support & complaintsPrimaryTechnical escalationService-specific escalation

From architecture review to production.

A scoped path, not a guaranteed timeline. How fast you reach production depends on scope, your regulatory responsibilities, and provider onboarding.

Step 1
Architecture review

Map your model to the control plane and agree the responsibility split.

Step 2
Sandbox

Integrate against the SDK and sandbox. Compliance-pack review in parallel.

Step 3
Pilot

Controlled flows with a defined cohort. DPA and MSA closed.

Step 4
Production

Cohort ramp to general availability with a joint incident runbook.

Security and evidence, by design.

Non-custodial

By default. Liability stays partner-side, funds stay end-user-side

Provider-neutral

Policy-based routing across eligible providers and rails

Audit-ready

One operational record and exportable audit logs

Independent security review Access controls & audit logging NDA materials on request Non-custodial architecture

Security overview → · Compliance model →

Common questions.

What is OVAAL?

OVAAL is a neutral control plane for programmable financial products. One modular layer runs accounts and wallets, money movement and routing, settlement, reconciliation, and the policies that govern every transaction. OVAAL is a technology and orchestration platform, not a bank, EMI, or CASP.

Who is it for?

Brokers, EMIs, wallets, marketplaces, and AI-native platforms build on it under their own license.

Does OVAAL hold customer funds or a license?

Unless expressly stated, OVAAL is not a bank, payment institution, electronic-money institution, or crypto-asset service provider. Regulated services are provided by appropriately authorised customers and third-party providers.

Does OVAAL do AI-agent payments today?

Today, policy and automation are live for human- and business-initiated flows. Fully agent-initiated finance is in design with early partners. We mark it as roadmap rather than claiming autonomy we haven't shipped.

See how it maps to your stack.

Book an architecture review and we'll walk through control-plane fit, 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.