AA-native wallets
ERC-4337 smart-contract wallets with passkeys, session keys, paymaster support. Non-custodial by default. The UX your users expect from a Web2 app.
Learn more →
For MiCA-licensed fintechs · For VARA and CBB partners · One SDK, one contract
The Web3 finance stack for licensed fintechs.
OVAAL is the embedded infrastructure layer that MiCA and VARA-licensed partners use to ship crypto features in 4 to 8 weeks. You get AA-native wallets, ramp aggregation, bill-pay, automation, and the compliance plumbing. Your brand. Your users. Your license. Our rails.
MiCA-compliant stablecoin issuers
EU EMI banking partners
Travel Rule providers
On-chain AML screening
ERC-4337 Account Abstraction
Five capabilities, one contract.
Partner integrates once. Ships five feature shelves.
Ramp aggregation
Multi-ramp routing with success-probability scoring. One quote, one all-in rate. Closes the roughly 50% failure gap that kills single-ramp integrations.
Learn more →Embedded bill-pay
USDC and EURC autopay over SEPA Instant rails. MiCA-aligned. Every payment gets a verifiable receipt.
Learn more →Automation
Plain-language DCA, take-profit, DeFi macros. Every rule runs a pre-trade simulation first. Hard caps. MEV-safe execution.
Learn more →Compliance stack
Travel Rule, AML screening, audit log export, EMI partner rails. The compliance pack lands before the first BD call.
Learn more →Built for your license
You hold the CASP, EMI, or VARA license. You own KYC, KYB, source of funds. We execute against your policy.
See the full platform →Built for your license, not ours.
One SDK, one contract, one integration engineer. Target: 4 to 8 weeks from signed paperwork to production.
Your stack
License (CASP / EMI / VARA / CBB). KYC + KYB + source-of-funds policy. End-user relationship + brand.
OVAAL
SDK + API. Wallets, ramps, bill-pay, automation. Inline Travel Rule + AML. Audit log.
End-user
Smart-contract wallet. Passkey or MPC share holds signing authority. Non-custodial by default.
Who integrates OVAAL.
Head of Product at an EMI or neobank
Ship crypto features without spending 18 months on an in-house build. Bill-pay, ramp, and AA wallets drop into your existing app as a feature shelf, under your license.
For EMIs and neobanks →CTO at a crypto-native fintech
Swap a bundle of four or five specialist vendors for one stack. Versioned APIs. Non-custodial by default. Self-host path for enterprise partners. Architecture you can audit on day one.
For crypto-native fintechs →Head of Compliance at a licensed fintech
Clear the infrastructure before your BD team commits. The partner compliance pack covers DPA, sub-processor list, Travel Rule and AML attestations, audit-log export.
See compliance posture →VP BD at a wallet provider
Commercials are published, not hidden. Named co-marketing playbook. Quarterly calls to align on the roadmap.
See pricing →EU and MENA. From V1.
EU, under MiCA
USDC and EURC as defaults, issued by Circle Internet Financial Europe. Travel Rule exchange through a partner-chosen provider. AML screening. SEPA Instant rails through the EMI you already work with, or one of ours.
EU lane details →MENA, under VARA and CBB
For VARA-licensed brokers in the UAE and CBB-licensed fintechs in Bahrain. The stack supports both regions from V1, not bolted on later. Regional AML rules and data-residency options included.
MENA lane details →From signed paperwork to production.
You get a dedicated integration engineer for the whole window. Kill switch and rollback are in the contract, not a conversation for later.
What OVAAL does not do.
- We don't hold your license. You keep the CASP, EMI, or VARA authorization.
- We don't custody end-user funds. AA-native wallets mean your users hold their own keys.
- We don't onboard your users. KYC, KYB, source of funds stay under your policy and your license.
- We don't ship in the US. V1 is EU and MENA. US infrastructure is out of scope.
If you need a licensed custody provider, or a US-centric white-label crypto broker, we're the wrong vendor. We'll tell you that on the first call.
Compliance, documented.
100%
Non-custodial by design
≤90d
Compliance pack review cadence
4-8 wk
Partner integration target
SOC 2 Type II · In progress
ISO 27001 · In progress
MiCA posture · Active
Non-custodial architecture
Ready to evaluate?
The integration brief is a one-page PDF. Product surface, compliance stack, commercial ranges, integration timeline. Thirty seconds to request. We reply within a business day.