Editor's note, 2026-06-26. This is our founding announcement, revisited. The original framed OVAAL as a consumer bridge between crypto and the bank. The product matured into something one altitude up: a neutral control plane for programmable finance, delivered as B2B2C infrastructure. Partners integrate one orchestration layer (accounts, money movement, settlement, reconciliation, policy and compliance) and onboard their own end-users under their own authorisation. Crypto rails were the first integration we shipped, not the category we sell. The piece below has been updated to the current scope; the dated framing is kept as the record of where we started. For the current product see the platform.

TL;DR

  • Money movement for a regulated fintech is spread across banks, wallets, ramps and compliance vendors. OVAAL puts one control plane over all of it.
  • The OVAAL mark (an oval loop with two notches) reads as a portal: value in, value out, every step on the record.
  • One modular layer for accounts, money movement, settlement, reconciliation and policy. Partners plug in their own providers and rails beneath it.
  • Crypto rails (account-abstraction wallets, ramp aggregation, stablecoin settlement) were the first integration we shipped. They are proof the control plane is real, not the category.
  • This is partner infrastructure. There is no consumer waitlist. Licensed fintechs evaluating a build can talk to us.

Why a control plane, and why now

A licensed fintech that wants to move money well has to wire together a wallet stack, a set of ramps, settlement rails, a reconciliation system and a handful of compliance vendors. Each one solves a slice. None of them owns the instruction end to end, so the partner inherits the gaps: which provider handled what, why a transfer stalled, where the audit evidence lives. The work that should be one record becomes four integrations and the liability that sits between them.

OVAAL exists to be that one record. The partner defines who or what may initiate a financial action, under which limits and approvals; OVAAL routes it across eligible providers and rails, then tracks it through execution, settlement, reconciliation and receipt as a single operational trail. Providers stay pluggable. The control stays with the partner.

What OVAAL Is (and Isn't)

Scope, stated plainly: OVAAL is pure B2B2C infrastructure. Our customer is the licensed partner. The partner integrates the control plane and onboards its own end-users under its own authorisation; OVAAL never holds end-user funds and never acquires consumers directly. Where the text below says "users," it means the partner's end-users.

Inside that scope, OVAAL is a technology and financial-orchestration layer, not a provider of regulated services. It governs accounts, money movement, settlement, reconciliation and policy, and it executes against the partner's compliance rules rather than its own license. Regulated services in the chain are provided by the partner and by appropriately authorised third-party providers. The design is built for evidence and control, not speculation: every instruction is governed, logged, reviewable and revocable.

The Lifecycle the Control Plane Owns

In: deposits and conversion. The partner's end-users move funds in through aggregated ramps and eligible rails. OVAAL routes on cost, eligibility, availability and observed performance, and shows the real fee before the instruction commits. See money movement.

Through: govern, settle, reconcile. Policy decides who or what may act and within which limits; settlement and reconciliation track the instruction from authorisation to receipt as one record. See policy and automation and settlement and reconciliation.

Out: payouts and withdrawal. Funds move back out across the same eligible providers with the timeline and cost surfaced up front, and the audit trail exported on demand. Accounts and wallet orchestration sit underneath all of it. See accounts and wallets.

The Principles That Guide the Build

  • Evidence by default. Every instruction is logged, every limit is explicit, and the audit trail exports. Nothing executes off the record.
  • Clarity over cleverness. The partner can always answer where an instruction is in its lifecycle and which provider handled each step.
  • Control stays partner-side. The partner sets the policies, limits and approvals; OVAAL executes against them. Custody, where it applies, is the partner's or an authorised provider's. OVAAL does not custody end-user funds.
  • Neutrality over lock-in. Providers and rails are pluggable. Versioned APIs and exportable data mean a partner is never trapped in our infrastructure.
  • Honest status. Each capability carries a maturity signal (Available, Pilot, Design Partner, Planned, Partner-dependent) so nothing reads as shipped before it is.

The Mark on Our Masthead

The symbol is an oval loop with two notches and a moving dot: a portal for value going in and coming back out. The idea held even as the product moved up a layer. The loop is now the control plane, and the dot is any instruction passing through it on the record.

What the Control Plane Ships

Available today, with crypto as the proven first rail:

  • Accounts and wallet orchestration, including account-abstraction wallets, passkeys and gasless flows
  • Money movement with ramp aggregation and policy-based routing across eligible providers
  • Settlement and reconciliation as one operational record, with stablecoin settlement over SEPA Instant-connected EMI rails
  • Policy and automation: rules, limits, approvals, previews and revoke

On the roadmap, shown with honest status:

  • Risk and compliance orchestration across configurable KYC, KYB, sanctions, screening and Travel Rule integrations
  • Deeper approval and multi-party signing workflows
  • Broader provider, rail and regional coverage
  • Policy-controlled financial actions for software agents (Planned / Design Partner), always within explicit limits and approvals, never autonomous authority over funds

Compliance, Security, and Availability

OVAAL is a technology and financial-orchestration platform, not a direct provider of regulated services. It is designed to support deployments by authorised firms operating in regulated EU and MENA markets, who hold the license and own KYC, KYB and source-of-funds obligations on their end-users. Compliance workflows connect through configurable integrations the partner operates under that authorisation. Security is built in with access controls, key management, audit logging and incident-response processes. Availability of any capability depends on jurisdiction, provider approval and service scope.

Disclaimer: OVAAL does not provide regulated financial or investment services directly. Regulated services are provided by appropriately authorised customers and third-party providers. Availability varies by jurisdiction and provider.

Postscript: What These Insights Will Be

OVAAL Insights documents the work behind the control plane: routing and settlement design, the responsibility split between partner, OVAAL and authorised providers, and honest case retros once partners are live. Builder-to-builder, for the teams evaluating whether to integrate or rebuild. For the current product, see the platform; for the developer surface, see the developer platform.