The MENA lane of the control plane.
This lane is designed to support deployments by authorised firms operating under VARA in the UAE and the Central Bank of Bahrain in Bahrain. Two of the clearer digital-asset frameworks in the region. Partners run on the same control plane as the EU lane, with local rails, compliance and data-residency options configured per market.
Availability is not guaranteed. Product availability in MENA depends on jurisdiction, the selected providers' approval, and service scope, and is configured per partner. OVAAL is not a bank, EMI or virtual-asset service provider.
Who this lane is for.
- VARA-authorised firms in the UAE, across the relevant activity categories.
- CBB-authorised firms in Bahrain, under the Central Bank of Bahrain's crypto-asset rules.
- Other UAE-authorised entities whose digital-asset scope sits under the applicable federal or free-zone framework.
- Regional banks and neobanks adding digital-asset capability alongside their own authorisations and provider partnerships.
What the MENA lane orchestrates.
Categories shown here. The specific providers we integrate, and your options per market, are disclosed in the gated compliance pack where contractually allowed.
- Stablecoin settlement: assets permitted under the partner's authorisation, issued by authorised providers, where supported.
- Fiat rails: AED and BHD payouts via regulated regional payment partners, subject to provider eligibility.
- AML & sanctions: screening and monitoring via AML screening vendors, with regional sanctions overlays, operated under your authorisation.
- Travel Rule: regional Travel Rule workflows via Travel Rule providers.
- Data residency: regional cloud preferences taken into account per market.
Dual-regime partners.
Some partners operate in more than one lane, for example an EU-authorised firm with a VARA-authorised UAE entity, or a bank serving several markets. The control plane handles them together: a per-user jurisdiction tag routes each flow to the right rails and policy defaults for that market.
Partner policy defines the routing rules. OVAAL's control plane executes them, and authorised providers settle the regulated services beneath it.
Early MENA partners get shaping rights.
The core control plane (code path, partner-policy configuration, compliance orchestration) runs the same in MENA as in the EU lane. Regional calibration happens alongside first-wave partners:
- AED and BHD payout rails. Regional provider integrations. First signed partners influence the shortlist.
- Arabic language and RTL UI. The framework is internationalisation-ready; rendering ships as partner demand confirms it.
Joining the MENA cohort early means your volume, jurisdictional edges and product preferences shape the integration. Partners who come in later run on a lane the founding cohort already hardened.