An exchange planning Gulf expansion discovers that Saudi Arabia – the region's largest economy – still operates without a comprehensive virtual-asset service provider framework. Activities that would require licensing in the UAE or Bahrain today sit in regulatory silence in the Kingdom, creating execution risk for businesses that assume permissionless entry and capital risk for those that build before clarity arrives. The legal question for any digital-asset operator eyeing Saudi Arabia is whether to enter the market now, wait for dedicated regulation, or structure through a neighbouring licensed hub and serve Saudi users cross-border.
Saudi Arabia has no standalone crypto or VASP licensing regime as of this publication. Virtual-asset activity is not prohibited, but it is not affirmatively regulated either. The Saudi Central Bank (SAMA) has issued warnings on the risks of trading cryptocurrencies, the Capital Market Authority (CMA) has stated that tokens are not securities under current law, and no regulator has opened applications for VASP authorisation. Businesses operating on-the-ground in the Kingdom do so without a tailored legal framework, meaning compliance is drawn from general e-commerce, AML and payment-service rules that were not written for digital assets. Cross-border operators serving Saudi nationals or residents from a licensed jurisdiction face different questions – principally whether the activity triggers local registration or whether the overseas licence and a properly structured user agreement are sufficient. In our licensing practice across the Gulf, we see three operator profiles: those who wait, those who soft-launch under e-commerce cover and AML procedures while monitoring for a regime announcement, and those who structure through Dubai or Abu Dhabi and treat Saudi Arabia as a cross-border customer base. This guide sets out the present position, what changes are visible on the policy horizon, and how businesses map their options before committing capital or a domain to the Kingdom.
What is the regulatory architecture for digital assets in Saudi Arabia?
Saudi Arabia has no dedicated framework for virtual assets. No VASP Act, no authorisation process, no published rulebooks. The vacuum is structural: the legal and regulatory system was built for traditional finance and has not yet extended to crypto. The Saudi Central Bank (SAMA) regulates payment services and e-money; the Capital Market Authority (CMA) supervises securities offerings and investment activities; the Ministry of Commerce handles business registration and e-commerce licensing. None of them today grants a licence category for a crypto exchange, custodian or token issuer.
SAMA's public position, articulated in multiple statements over the past several years, is that cryptocurrencies carry substantial consumer risk and that the Bank has not licensed any entity to deal in them. The CMA has clarified that tokens do not fall within the definition of a security under the Capital Market Law unless they confer traditional rights – equity, debt, profit-participation – and that initial coin offerings are not registered offerings. These statements create a regulatory perimeter by negative space: virtual assets are not payment instruments under SAMA's remit, not securities under the CMA's, and not governed by a stand-alone statute. The result is that a business providing exchange, custody or brokerage services for digital assets operates without sector-specific authorisation and must instead piece together coverage from general business licensing, AML registration if applicable, and the e-commerce regulatory framework.
The absence of a framework does not mean an absence of enforcement capacity. SAMA and the Saudi Arabian Monetary Authority retain jurisdiction over unlicensed payment activity and over businesses that mislead consumers into believing they hold regulatory approval. Operators marketing services as "SAMA-licensed" or "CMA-approved" when no such licence exists face administrative action and reputational harm. In our advisory work with Middle East operators, we see this gap create two kinds of paralysis: operators who believe Saudi Arabia is "open" because there is no explicit prohibition, and operators who believe it is closed because there is no licence to obtain. Neither is accurate. The position is that the activity is neither licensed nor banned, and that a business must assess risk and build a compliance posture from adjacent rules while waiting for clarity.
How do cross-border operators approach Saudi users?
A licensed exchange in Dubai or Malta faces a separate question when Saudi nationals appear in the user funnel. Is serving them from an overseas platform – without a local presence, office or staff – lawful, and does it trigger Saudi registration? The answer turns on how the service is marketed, how user agreements are drafted, and whether the operator holds itself out as doing business in Saudi Arabia or merely accepting Saudi users who reach the platform.
E-commerce law in the Kingdom requires businesses that market and transact with consumers inside Saudi Arabia to register and display Saudi commercial registration details. If an exchange runs Arabic-language ads targeting Saudi users, offers riyal on-ramps through Saudi payment gateways, and describes itself as serving the Saudi market, it is likely engaging in e-commerce activity in the Kingdom and would need to register. If, by contrast, the platform is English-language, accepts Saudi users passively without Saudi-specific promotion, settles only in dollars or stablecoins, and clearly disclaims that the service is provided from a foreign jurisdiction under foreign law, the registration trigger is less clear. The line is not bright. The Ministry of Commerce has broad authority to require registration of online businesses serving Saudi consumers, and the practical risk is not immediate enforcement but the inability to open Saudi banking rails, payment partnerships or eventually convert to a local licence when a regime is introduced.
In our practice, operators who want optionality in the Saudi market without committing to a physical presence typically structure defensively: they hold a Gulf licence (VARA in Dubai, ADGM in Abu Dhabi, or Bahrain), they geo-fence or apply enhanced due diligence to Saudi users, they settle in non-fiat instruments to avoid triggering payment-service definitions, and they draft terms that explicitly state the service is provided cross-border. This does not eliminate legal uncertainty, but it minimises the claim that the business is operating in Saudi Arabia without authority. We map this structure before an operator goes live, because reversing course after user acquisition – moving an established Saudi user base out of the platform or applying for retroactive registration – is far more expensive than building correctly at the outset.
What is the position on payment and on-off ramps?
Payment services in Saudi Arabia are the domain of SAMA. The law defines regulated payment activity to include money transfer, e-wallets and payment facilitation. Crypto-to-fiat on-ramps – services that accept Saudi riyals and deliver digital assets, or vice versa – sit in contested space. If structured as a payment service they require SAMA authorisation. If structured purely as a sale of a digital commodity they may not, but that characterisation is untested. SAMA has not issued guidance distinguishing a riyal-to-bitcoin transaction from a payment service, and until it does, operators treat riyal on-ramps as high-risk.
The consequence is that most digital-asset businesses serving Saudi users avoid direct riyal integration. They onboard users with stablecoins or accept international wire transfers in dollars, settling the exchange leg off-shore. Saudi users who want to fund an account typically buy USDT or USDC peer-to-peer or through an international exchange, then deposit the stablecoin. This adds friction – each hop is an AML checkpoint and a delay – but it keeps the operator outside the payment perimeter. A business that processes riyal deposits at scale without a payment-service licence risks being deemed an unlicensed money transmitter, with consequences that include orders to cease activity, fines and referral to enforcement authorities.
Banking the business itself is separate from user on-ramps but equally constrained. Saudi banks, responding to SAMA's public warnings on crypto risk, generally decline to open accounts for entities whose primary business is virtual-asset exchange or custody. An operator incorporated in Saudi Arabia with an e-commerce licence can sometimes secure a business account if the description of activity is generic ("technology services", "software platform"), but that account becomes unsustainable once crypto transactions flow through it at volume. Most operators solve this by banking the holding company in a crypto-friendly jurisdiction – often the same place the operating licence sits – and routing any Saudi presence through service agreements and minimal local cash flow. This is not a permanent solution, but it is the working model pending regulatory development.
What are the AML and financial-crime obligations?
Saudi Arabia is a member of the Middle East and North Africa Financial Action Task Force (MENAFATF) and has implemented the FATF Recommendations into domestic law through the Anti-Money Laundering Law and implementing regulations. Virtual-asset service providers are explicitly covered by the FATF standards under Recommendation 15, but Saudi Arabia has not yet transposed that recommendation into binding local requirements. The effect is that a business dealing in virtual assets in the Kingdom has an AML obligation in principle but no sector-specific rulebook to follow.
In practice, this means an operator builds an AML and counter-terrorist-financing (CFT) programme using the general framework: customer due diligence, transaction monitoring, suspicious-activity reporting to the Saudi Financial Intelligence Unit (SAFIU), record-keeping, and staff training. The obligation exists; the question is which standard to adopt in the absence of VASP-specific rules. Conservative operators apply the FATF Virtual Asset guidance – customer identification at onboarding, Travel Rule data exchange on transfers above a threshold (typically 1,000 USD or EUR equivalent, though Saudi Arabia has not set its own threshold), ongoing monitoring for high-risk jurisdictions and transaction patterns, and annual independent reviews. A business that waits for domestic VASP rules to build AML procedures risks being non-compliant the day those rules take effect, because compliance programmes require time to operationalise. Waiting is not a neutral option.
The Travel Rule is particularly acute for exchanges serving cross-border flows. A transfer between a Saudi user and a counterparty on a foreign platform should, under FATF guidance, carry originator and beneficiary data. Many smaller platforms cannot yet exchange that data in a standardised format, and enforcement varies widely by jurisdiction. Saudi Arabia has not published Travel Rule implementation guidance, but an operator that ignores the data obligation because local rules are silent will face problems when those rules arrive or when a foreign regulator or compliance partner asks why the Saudi leg of the transaction lacks required fields. In our compliance practice, we build the Travel Rule workflow into the platform architecture from launch, even in jurisdictions where enforcement is not yet active, because retrofitting data pipelines after the user base scales is a multi-quarter rebuild.
How is token issuance and ICO activity regulated?
Token issuance in Saudi Arabia falls under the Capital Market Authority's jurisdiction if the token qualifies as a security. The CMA applies a substance test: if the token confers ownership, profit rights, voting control or a claim on assets, it is likely a security and the offering must comply with the Capital Market Law – prospectus, registration, disclosure, ongoing reporting. If the token is a pure utility instrument with no investment expectation and no secondary-market trading contemplated, it may sit outside securities regulation, though that characterisation must be defensible under scrutiny.
Initial coin offerings have not been common in the Saudi market, in part because the CMA's public position has been that most ICOs as structured internationally would require registration and that international token sales targeting Saudi investors without CMA authorisation are unlawful. The Capital Market Law prohibits offering securities to the Saudi public without prior approval, and an ICO marketed through social media, Telegram groups or crypto forums that reaches Saudi nationals arguably constitutes an unregistered public offering. Enforcement is uneven – the CMA has not published a string of ICO enforcement actions – but the risk is present, and issuers who run global token generation events without geo-fencing or KYC checks create liability if Saudi participants later claim mis-selling.
Stablecoin issuance presents a separate classification question. A fiat-backed stablecoin pegged 1:1 to the dollar or riyal resembles e-money, which under many regimes requires an e-money licence or equivalent authorisation. Saudi Arabia has an e-money framework under SAMA, but it has not yet addressed whether a stablecoin issuer falls within that framework. Until SAMA clarifies, a business issuing a riyal-pegged stablecoin or a multi-currency basket token backed by reserves faces material legal uncertainty and should assume that operating without engaging the regulator is high-risk. The safer path for an issuer targeting Gulf users is to obtain an appropriate licence in a jurisdiction that has already addressed stablecoins – the UAE under VARA, or a European member state under MiCA's e-money token (EMT) regime – and distribute into Saudi Arabia on a cross-border basis under the same principles that govern exchange services.
What is the policy trajectory and anticipated regulatory development?
Saudi Arabia's Vision 2030 economic transformation programme includes digital infrastructure and fintech as priorities. The Kingdom has launched a regulatory sandbox under SAMA for fintech firms, established the Saudi Fintech initiative, and expressed interest in central bank digital currency experimentation. These signals suggest that a virtual-asset framework is probable, not merely possible, but the timeline remains uncertain. No draft legislation has been published, no public consultation launched, and no regulator has announced plans to open VASP applications.
Informed market participants expect that if a regime arrives, it will follow the model set by the UAE and Bahrain: activity-based licensing, fit-and-proper criteria for management, capital and insurance requirements, AML and Travel Rule obligations mirroring the FATF standards, and supervision by SAMA or the CMA depending on the activity. The regime may distinguish between exchange, custody, advisory, and token-issuance functions, with separate or tiered licences. It may require a local presence – a Saudi entity, local directors, a physical office – or it may permit branches of foreign licensed entities. Until draft law or regulations appear, these are assumptions, not facts.
For a business deciding whether to launch in Saudi Arabia today or wait, the calculus is this: launching under current law means building without regulatory cover and accepting that the first movers will face compliance retrofits when rules arrive. Waiting means ceding the market to competitors willing to operate in the grey zone, but it also means being able to apply for a licence without the baggage of a legacy user base acquired under ambiguous legal authority. In our experience, operators with short capital runways and immediate revenue needs lean toward soft launch; those with patient capital and a multi-year Gulf strategy wait for clarity or structure through a neighbouring licensed hub. Neither path is wrong, but the choice must be deliberate, documented, and explained to investors and banking partners.
What is the tax treatment of digital-asset activity?
Saudi Arabia introduced value-added tax (VAT) in 2018 at a standard rate that has since been adjusted; VAT applies to taxable supplies of goods and services in the Kingdom. The treatment of digital-asset transactions for VAT purposes has not been definitively addressed by the Zakat, Tax and Customs Authority (ZATCA), and practices vary. In many jurisdictions, the sale of cryptocurrency is treated as a supply of goods (exempt or zero-rated under certain frameworks, taxable under others) or as a financial service (often exempt). Saudi Arabia has not published crypto-specific VAT guidance, leaving operators to apply general principles or seek private rulings.
Corporate income tax in Saudi Arabia applies to resident companies and to non-residents with a permanent establishment in the Kingdom. An exchange incorporated and managed in Saudi Arabia is subject to Saudi corporate income tax on worldwide profits. A foreign exchange serving Saudi users without a local presence is unlikely to have a permanent establishment unless it maintains an office, dependent agents or server infrastructure that creates a fixed place of business in the Kingdom. The permanent-establishment analysis turns on facts – where servers sit, where staff work, where decisions are made – and a business that runs Saudi-Arabic marketing and customer support from a Riyadh office is at risk of creating taxable presence even if the booking entity is offshore. Tax structuring for digital-asset businesses serving the Gulf is a recurring question in our practice, because the combination of multiple licensing jurisdictions, Cloud infrastructure that crosses borders, and remote teams creates permanent-establishment exposure that many founders do not anticipate. We pressure-test the structure before launch, not after the first tax audit.
What are the common mistakes operators make in the Saudi market?
The first mistake is entering Saudi Arabia on the assumption that silence equals permission. A founder reads that there is no VASP law, concludes the market is open, incorporates a Saudi LLC, launches an exchange, and only later discovers that banking is closed, that payment processing is unworkable without a SAMA licence, and that the business has built an entire compliance stack that will be obsolete the day regulations are published. The correct sequence is structure assessment, risk documentation, and staged entry – not "launch first, ask questions when a problem appears."
The second mistake is under-investing in AML and financial-crime controls because there is no sector-specific rulebook. The absence of VASP regulations does not eliminate the AML obligation; it shifts the reference standard to general principles and international best practice. An operator that onboards users with minimal KYC and no transaction monitoring because "Saudi Arabia doesn't have Travel Rule enforcement yet" is building a compliance debt that becomes unmanageable once the user base scales. In a recent advisory matter, an exchange with several thousand Saudi users discovered that its lack of Travel Rule infrastructure made it ineligible for banking partnerships and integration with larger platforms that required Travel Rule compliance as a commercial prerequisite. Rebuilding the data architecture took six months and cost the business two major partnership opportunities. The cost of building correctly at the outset – professionally designed CDD, transaction monitoring, Travel Rule messaging – is measured in weeks of development time. The cost of retrofitting is measured in quarters and lost revenue.
The third mistake is inconsistent messaging to Saudi authorities, banking partners and users. A business tells the Ministry of Commerce that it is a "blockchain technology consultancy" to secure commercial registration, tells the user base in Arabic-language marketing that it is a "licensed crypto exchange," and tells a prospective bank that it is a "software platform." The regulatory system is small and interconnected. Inconsistent descriptions surface quickly, and they destroy credibility with the regulator when a licensing regime is introduced and the business applies for authorisation. The approach that preserves optionality is to describe the activity accurately and consistently – virtual-asset exchange, custody, advisory – and to be transparent that the business operates without a sector-specific licence because none is available, not because the licence was sought and denied or waived.
What are the structure options for businesses targeting the Saudi market?
Operators entering the Saudi market before a VASP regime is in place typically choose one of three paths. Path one is full local presence: a Saudi entity, e-commerce registration, AML procedures drawn from general principles, and the acceptance that banking and payment processing will be constrained until a regulatory framework arrives. This path suits businesses that need a Saudi brand, that serve primarily Saudi nationals, and that have the capital to sustain operations while waiting for rules to clarify. It is not the majority path, because the costs and friction are high relative to the near-term revenue opportunity.
Path two is the licensed offshore hub with cross-border service delivery. The business holds a VASP licence in Dubai, Abu Dhabi, Bahrain or a European jurisdiction, structures terms of service to make clear the service is provided from that location, applies geo-fencing or enhanced due diligence to Saudi users to manage concentration risk, and forgoes riyal on-ramps and Saudi payment integration. This path is common among operators building a Gulf footprint, because the VARA or ADGM licence carries credibility with banking partners and users, and the entity can convert or apply for a Saudi licence later without unwinding an unlicensed local operation. The trade-off is that the business cannot market itself as Saudi, cannot easily onboard users who have never held crypto before (because they face the stablecoin-funding friction), and may lose market share to a competitor willing to run a local entity with fewer controls.
Path three is the wait-and-watch posture. The business monitors Saudi regulatory development, builds no Saudi presence, and plans to apply for a licence the quarter after regulations are published. This is the lowest-risk approach from a legal perspective, but it cedes the market to others during the wait. First movers in an emerging jurisdiction capture user mindshare and liquidity, and entering a market after competitors have established network effects requires significantly higher customer-acquisition cost. The path you choose depends on your capital position, your risk tolerance, and your time horizon. A business with a multi-year investment thesis and patient backers can wait. A business that needs revenue in the next four quarters cannot. We help operators map the three paths in the first strategy call, before any formation documents are signed or marketing spend is committed, because changing structure mid-flight is expensive and often impossible without losing users or banking.
The Saudi market is large, relatively young in digital-asset adoption, and untested in regulatory enforcement. Operating there today requires a deliberate risk posture, defensible compliance design, and contingency planning for multiple regulatory scenarios. If your business is weighing Saudi Arabia as an operating jurisdiction or as a cross-border user base, map the structure now – before formation, before a domain goes live, and before the first Saudi riyal touches your platform. Contact OBOLUS at info@oboluslaw.com for a scoped assessment of your entry options and the compliance architecture each path requires.
FAQ
How long does a crypto licence take to obtain?
Saudi Arabia does not currently issue crypto or VASP licences, so there is no application timeline to report. In jurisdictions that do license virtual-asset businesses – the UAE, Malta, Singapore, Lithuania – the timeline from initial submission to authorisation typically ranges from several months to over a year, depending on the complexity of the business model, the completeness of the application, and the regulator's workload. Operators planning for a Saudi licence when a regime is introduced should assume a comparable timeline and should use the interim period to build the compliance infrastructure – governance documents, AML procedures, capital adequacy, insurance – that licensing authorities universally require.
Which jurisdiction suits my crypto business?
The answer depends on where your users sit, where you can secure banking, and what your business model requires. An exchange serving primarily Gulf users benefits from a UAE or Bahrain licence, which signals regulatory credibility in the region and opens banking partnerships. A custody provider serving institutional clients globally may prefer Switzerland or Singapore for their mature legal frameworks and depth of financial-services expertise. A token issuer targeting European retail investors should consider a MiCA-compliant jurisdiction. The choice is never purely regulatory – it is the intersection of licensing, tax, banking access, and the ability to recruit and retain the team. Structure decisions are not reversible without cost, so the analysis must happen before incorporation, not after the business is live.
Do I need a separate custody licence?
In many flagship jurisdictions – the UAE under VARA, the EU under MiCA, Singapore under the Payment Services Act – custody of client digital assets is a separately regulated activity and requires specific authorisation. An exchange licence does not automatically permit custody, and an entity that holds user funds without the correct licence category faces enforcement risk. In Saudi Arabia today there is no custody licence to obtain because there is no VASP framework, but a business that custodies assets for clients should assume that when regulations arrive, custody will be a gated activity requiring capital adequacy, insurance, segregation of client assets, and regular audits. Building custody operations without those protections today means retrofitting them later under regulatory pressure, often while the business is unable to onboard new clients or access banking. The correct approach is to design for the licensing standard you expect, not for the regulatory silence that exists now.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit, and we pressure-test structures before capital and reputation are at risk. Every engagement is scoped, priced and delivered under an SLA. To discuss your Saudi Arabia entry plan or your Gulf licensing strategy, contact info@oboluslaw.com.
By Aisha Tan, Licensing & Jurisdictions Analyst – advising on VASP authorisation, cross-border structuring and regulatory-framework navigation across emerging and established digital-asset hubs.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.