The license
Your CASP or EMI authorization is the regulatory anchor. OVAAL does not hold a consumer-facing license.
Solutions / For EMIs + neobanks
A Web3 feature shelf for your EMI.
You have the EMI license, the SEPA rails, and the user base. What you don't have is 18 months of in-house crypto engineering. We give you the Web3 layer you embed against that existing license: AA-native wallets, bill-pay from stablecoins, ramp aggregation. Your brand. Your users. Your compliance. Our rails.
The OVAAL SDK, on your license.
| Capability | How it shows up to your user | Link |
|---|---|---|
| Smart-contract wallet | Passkey login, no seed phrase, gasless UX | /platform/wallets/ |
| Crypto deposit + withdrawal | Best-rate single-quote with transparent fees | /platform/ramps/ |
| Pay bills from stablecoin | Rent, utilities, subscriptions — SEPA Instant settled | /platform/bill-pay/ |
| DCA + take-profit automation | Plain-English rule builder with pre-trade simulation | /platform/automation/ |
| Compliance stack | Travel Rule, AML, MiCA, audit-log export | /platform/compliance-stack/ |
All five ship from one SDK. One contract. One integration engineer.
What stays yours.
The user
KYC, KYB, customer support, lifecycle — your customer, your relationship.
The brand
White-label or deep-embed. OVAAL is visible to your user only if you choose to surface it.
The ledger
Your balance records are the source of truth. OVAAL is orchestration, not bookkeeping.
Three common integration shapes.
- Bill-pay first, wallet later. Your EMI already has the fiat rails; you add USDC/EURC-funded bill-pay as a new deposit source. Lowest-risk start.
- Wallet + ramp, no bill-pay yet. Your app adds a crypto account where users can deposit, hold, convert, withdraw — no automation. Phase-in the rest later.
- Full shelf from day one. Wallet + ramps + bill-pay + automation + compliance. More integration surface, more differentiation.
We help you scope the right shape on the first call, not guess.