Caucasus VASPs are the most-discussed Sanctions-Edge cohort. They are not the only one. Turkish, Kazakh, UAE-domiciled, and (increasingly) Bosnian and Serbian VASPs serving CIS-adjacent flows face the same structural diligence at EU and US sponsor banks: documented separation from sanctioned-jurisdiction flows, on-chain forensics overlay, customer-base composition test. The diligence framework has hardened materially since the EU's 20th sanctions package adopted on 23 April 2026 — and it is now treated by sponsor-bank credit committees as a structural overlay rather than a discretionary one.

This article generalises what we covered for Caucasus VASPs into a broader Sanctions-Edge VASP framework. The five jurisdictional clusters that face the same diligence overlay; the five components of the documented sanctions perimeter; the practical steps that distinguish VASPs that get banked from those that don't; and the 20th-sanctions-package implications that shaped the 2026 baseline.

Sanctions-Edge does not mean sanctioned. The cohort is fully legitimate from the perspective of the home jurisdiction, FATF, and Western sponsor banks. The cohort is exposed because the geographic adjacency to sanctioned flows raises sponsor-bank diligence depth — and the firms that have built the documented perimeter pass through that depth quickly.

The five jurisdictional clusters

1. Caucasus

Georgia and Armenia. Domestic VASP regimes well-developed (NBG and CBA Regulation 7/01). Russia exposure is the dominant filter. We cover this cluster in detail in our Caucasus article; the framework here generalises the Caucasus playbook.

2. Central Asia

Kazakhstan, Kyrgyzstan, Uzbekistan. The 20th EU sanctions package¹[1] designated the Kyrgyz exchange TengriCoin — the first such designation of a third-country VASP — and explicitly placed Central Asian VASPs into the EU enhanced-diligence perimeter. Kazakh VASPs benefit from the country's mature crypto regulation but face the same Filter weighting as Caucasus VASPs.

3. Turkey

Major regional crypto hub. Turkish CASP framework introduced in 2024. Turkey faces a complex sanctions-overlay diligence given its position in Russia-related trade flows and the historical role of Turkish banks in Russia-adjacent settlement. Turkish VASPs accessing EU/USD rails in 2026 face the deepest documentation expectations of any Sanctions-Edge cluster.

4. UAE (and broader Gulf)

Dubai (VARA) and ADGM (FSRA) host significant VASP populations. The UAE's status as a regional financial hub for Russian, Iranian, and Belarusian-adjacent flows places UAE VASPs into the Sanctions-Edge cohort despite the strength of the home regulatory regime. EU sponsor banks underwrite UAE VASPs with explicit attention to cross-border customer flows from sanctioned jurisdictions.

5. Western Balkans

Serbia, Bosnia and Herzegovina, Montenegro. Smaller cohort, but recently emerging as VASP-domiciliation jurisdictions for firms seeking proximity to EU markets without EU regulatory burden. The Western Balkans cluster is increasingly diligenced under the same Sanctions-Edge framework, particularly for Russian-citizen-UBO firms.

The five-component sanctions perimeter

What sponsor banks expect to see during diligence on a Sanctions-Edge VASP. Calibrated to FATF²[2] Recommendations 15 and 16 plus the EU/US sanctions architecture:

Component 1 — Sanctions policy with explicit jurisdictional exclusion

Board-approved policy explicitly excluding Russian, Belarusian, Iranian, North Korean, and Syrian customers (or as scoped). Dated, signed, with named MLRO/Compliance owner. Refresh cadence at least annual.

Component 2 — KYC enforcement

Customer onboarding flow that enforces nationality, residency, and tax-residency screening. Cross-checks against sanctioned-jurisdiction nationality and residency. PEP screening with enhanced sensitivity for sanctions-adjacent jurisdictions. Documented exception-handling and override-approval workflow.

Component 3 — On-chain forensics overlay

Integration with at least one institutional analytics provider (Chainalysis, Elliptic, TRM Labs) with the Russia-nexus heuristic enabled. Inbound transaction screening, outbound transaction screening, ongoing monitoring on customer wallet activity. Documented threshold for blocking vs flagging.

Component 4 — Customer-base composition reporting

Quarterly numerical breakdown of customer base by nationality, residency, and tax-residency. Reported to the board, retained for supervisor and sponsor-bank inspection. Trend analysis quarter-on-quarter — sponsor banks weight stability heavily.

Component 5 — Geo-fencing infrastructure

IP-level geographic enforcement at signup and at every login. Blocked-jurisdiction list maintained in line with sanctions framework. VPN-detection layer to prevent geographic spoofing. Combined with Component 2's KYC enforcement, geo-fencing creates the documented compound exclusion that sponsor banks score.

The Sanctions-Edge VASP perimeter — five components.

ComponentWhat it documentsDiligence weight
1. Sanctions policyBoard-approved exclusion languageFoundation — required
2. KYC enforcementNationality/residency screening + PEPHigh
3. On-chain forensicsRussia-nexus + sanctioned-address screeningHighest
4. Composition reportingQuarterly nationality/residency breakdownHigh — trend-weighted
5. Geo-fencingIP + KYC compound enforcementMedium-High

What the 20th sanctions package changed

Adopted 23 April 2026 by the Council of the EU. Three structural changes that shaped the 2026 Sanctions-Edge framework:

  • First-ever designation of a third-country VASP (TengriCoin, Kyrgyz exchange) — establishes that EU willingness to designate Sanctions-Edge VASPs is no longer hypothetical.

  • Sweeping ban on crypto transactions with Russian and Belarusian VASPs from 24 May 2026 — affects every Sanctions-Edge VASP serving customers who transact with Russian or Belarusian counterparties.

  • Designation of 4 third-country financial institutions linked to Russia's SPFS network — signals expanding willingness to target the financial infrastructure adjacent to crypto.

Practitioner consensus from Chainalysis, Elliptic, and TRM Labs analyses of the package: the EU is signalling a new era of crypto-sanctions enforcement against third-country VASPs. Sanctions-Edge VASPs that have not built the documented perimeter face escalating banking exposure throughout 2026.

AMLR application — what changes in July 2027

AMLR³[3] application from 10 July 2027 codifies several of the Sanctions-Edge expectations into formal EU AML rules. The threshold for self-hosted-wallet verification drops to €1,000; PEP screening hardens; Travel Rule alignment tightens; AMLA direct supervision applies to selected entities. EU sponsor banks underwriting Sanctions-Edge VASPs increasingly score for AMLR-readiness ahead of the July 2027 application date.

Frequently Asked Questions

Is Turkey a Sanctions-Edge jurisdiction?

Yes, but with deeper diligence than other clusters. Turkey is a major regional crypto hub and benefits from the home regulatory framework, but its position in Russia-related trade flows places Turkish VASPs into the deepest layer of the Sanctions-Edge perimeter. Turkish VASPs accessing EU rails in 2026 face the most extensive documentation expectations of any cluster covered here.

What if my VASP has Russian-citizen UBOs?

Russian-citizen UBOs are not in themselves disqualifying. The diligence focuses on (a) the UBO's residency and tax-residency post-2022, (b) the UBO's source of wealth, (c) any Russian-state nexus. Russian-citizen UBOs with documented EU/UK/UAE residency, clean source of wealth, and no state nexus onboard regularly. The diligence is materially deeper but the outcome is achievable.

Can a Sanctions-Edge VASP serve Russian-resident customers via a separate entity?

In principle yes, with the structural answer being a two-entity model — one entity serving Sanctioned-jurisdiction customers with domestic-only banking, one entity serving non-sanctioned customers with EU/USD rails. The two entities should be operationally separate (separate boards, separate compliance functions, no shared customer database) to satisfy sponsor-bank diligence on the EU-rails side. Mixing the books inside one entity makes the EU rails impossible.

What's the most-cited failure point in Sanctions-Edge banking?

Component 4 — composition reporting. VASPs frequently have Components 1, 2, 3, and 5 in place but cannot produce the quarterly numerical breakdown of customer base by nationality and residency. Sponsor banks read this as a structural compliance gap because composition reporting is what allows trend analysis and supervisor-defensible monitoring.

Will the Sanctions-Edge framework relax over time?

Unlikely in the short term. The trajectory through 2026 has been consistent hardening — 20th sanctions package, AMLR application in July 2027, AMLA direct supervision phasing in. Plan for the framework as a structural feature of EU/US sponsor-bank diligence rather than a transitory constraint.

Book a free regulatory bankability assessment. We respond within 24 hours.

Book Assessment

The Sanctions-Edge VASP framework is the diligence overlay that the 20th sanctions package made explicit and that AMLR will codify in July 2027. Build the five-component perimeter before applying for EU/USD rails, document each component to inspection-ready depth, and revisit quarterly as sanctions architecture evolves.

Footnotes & Citations

  1. Council of the EU — 20th round of EU sanctions against Russia (23 April 2026), including the designation of Kyrgyz exchange TengriCoin as the first third-country VASP designation for Russia-adjacent activity.

  2. Financial Action Task Force — Updated Guidance for a Risk-Based Approach to Virtual Assets and VASPs (October 2021).

  3. Regulation (EU) 2024/1624 (AMLR) — single rulebook on AML/CTF for financial entities including CASPs, applying from 10 July 2027.

ShareLinkedIn
Take the next step
Related reading

Continue with related resources