OVAAL for the MENA regulatory lane.
UAE (VARA) and Bahrain (CBB) are two of the clearest crypto regulatory frameworks anywhere. We support both as first-class regional lanes, not bolted on, not a Phase 2 roadmap item. Partners run on the same infrastructure as our EU partners, with local compliance, rails, and data-residency options.
Who this is for.
- VARA-licensed broker-dealers (UAE Virtual Assets Regulatory Authority Category I / II / III).
- CBB-licensed crypto-asset service providers (Central Bank of Bahrain Crypto-Assets Module).
- DIFC-licensed and ADGM-licensed entities whose crypto scope falls under VARA or federal rules.
- Regional neobanks adding crypto capability under their banking license + VARA/CBB partnership.
What MENA partners ship.
- Stablecoins: USDC + USDT (per local authorization) + regional tokens where partner-chosen.
- Fiat rails: AED + BHD payouts via VARA-registered / CBB-registered payment partners.
- AML screening: Chainalysis or TRM — same stack as EU, with UAE / Bahrain sanctions-list overlays.
- Data residency: UAE data-center preference for VARA partners; Bahrain for CBB partners.
- Travel Rule: UAE VARA + CBB Crypto-Asset Module compliance via Notabene or 21 Analytics.
Dual-regime partners.
Some partners operate in both lanes — an EU-headquartered CASP with a VARA-licensed UAE subsidiary, or a neobank serving both. OVAAL's stack handles both simultaneously: per-user jurisdiction tag routes the flow (EU user → SEPA rails + MiCA defaults; UAE user → AED rails + VARA defaults).
Partner policy defines the routing rules. OVAAL's infrastructure executes.
Early MENA partners get shaping rights.
The core stack (code path, partner-policy configuration, Travel Rule, AML) runs the same in MENA as in EU. Regional calibration happens alongside first-wave partners:
- AED and BHD payout rails. Regional PSP integrations. First signed partners influence the final shortlist.
- Arabic language and RTL UI. Framework is i18n-ready. Rendering ships per partner demand.
Joining the MENA cohort early means your volume, jurisdictional edges, and product preferences shape the integration. Partners who come in later run on infrastructure the founding cohort already hardened.