You hold the EMI authorisation, the SEPA rails, and the user base. What you don't have is 12 to 18 months of in-house engineering to add programmable wallets and digital-asset rails, and the reporting plumbing to keep them auditable. OVAAL is the orchestration layer you embed against your existing licence: programmable accounts, money movement, settlement and reconciliation, policy and audit, in one integration. Your brand. Your users. Your licence.
OVAAL is a technology and orchestration platform, not a bank, EMI, or CASP. You hold the regulated relationship under your own authorisation; authorised providers execute the regulated service. Availability depends on jurisdiction, provider approval, and service scope.
One integration brings six modules. Take the whole control plane or the modules you need. Each one routes to authorised providers and rails beneath it.
Add programmable accounts and wallets to your app with unified identity, permissions, delegated access, and recovery. The proven first rail today is ERC-4337 smart-contract wallets with passkey login and gasless flows.
Route deposits, conversions, transfers, and payouts across eligible providers and rails using cost, eligibility, availability, and observed performance, not a single hard-wired path.
Track each instruction from authorisation through execution, settlement, and reconciliation as one operational record your finance and ops teams can audit. Near-real-time settlement where the selected provider, destination institution, and jurisdiction support it.
Define who or what may initiate a financial action, under which limits and approvals. Every rule previews before it runs, and every instruction is logged and revocable.
Connect KYC, KYB, sanctions, wallet screening, transaction monitoring, and Travel Rule workflows through the risk and compliance stack, configurable integrations you operate under your own authorisation.
Integrate through versioned APIs, SDKs, webhooks, sandbox tooling, and implementation support. Exportable data, with a self-host path on the roadmap.
All six ship from one SDK and one contract. You decide which modules surface to your users, and when.
Your EMI authorisation is the regulatory anchor. OVAAL does not hold a consumer-facing licence and does not become a vendor in your regulated chain unless expressly authorised.
KYC, KYB, customer support, complaints, and lifecycle stay with you. Your customer, your relationship, your obligations.
White-label or deep-embed via SDK. OVAAL is visible to your end-user only if you choose to surface it.
Your balance records remain the source of truth. OVAAL provides one operational record across providers for orchestration and audit, not bookkeeping in place of yours.
We scope the right shape with you on the architecture review. We don't guess it. Building for a different segment? See all solutions.
OVAAL is the technology layer. Your EMI 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, under your EMI licence | Technology role unless expressly authorised | Primary for the outsourced regulated service |
| KYC / KYB policy | Policy owner | Workflow orchestration | Verification where contracted |
| Safeguarding / custody | Per your model and authorisation | No, unless expressly authorised | Primary where applicable |
| Routing configuration | 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 |
Book an architecture review and we'll walk through control-plane fit, the responsibility split, and a realistic integration path for your EMI. Prefer to read first? The integration brief is a one-page PDF covering modules, the responsibility model, and indicative commercials.