A digital-asset firm operating under the Astana Financial Services Authority (AFSA) regime quickly discovers that a licence alone does not satisfy the regulator. The Travel Rule – the obligation to collect, verify and transmit originator and beneficiary data alongside every qualifying virtual-asset transfer – is a standing compliance requirement, not a one-time checkbox. Fail to embed it before your first audit and the consequences are immediate: suspended activity approvals, restricted banking access, and the kind of correspondent-bank churn that can strand client funds across borders. This page sets out what a Travel Rule compliance program requires under the AIFC/AFSA framework, how to build one, and where the cross-border pressure points sit for an inbound operator.
The regulatory basis: AFSA, FATF and the Travel Rule in the AIFC
The Astana Financial Services Authority (AFSA), the prudential and conduct regulator inside the Astana International Financial Centre (AIFC), implements AML/CFT rules aligned with the Financial Action Task Force (FATF) Recommendations – in particular Recommendation 15, which extends the Travel Rule to virtual-asset service providers. Any entity that holds a digital-asset trading facility or custody authorisation under the AIFC framework is simultaneously a VASP (virtual asset service provider) for FATF purposes and must comply with Travel Rule obligations as a condition of that authorisation.
The AIFC operates as a common-law jurisdiction within Kazakhstan. Its courts and regulations are structurally independent of Kazakhstan's civil-law courts, which matters when you are tracing a cross-border payment or enforcing a disclosure obligation. The AFSA's AML/CFT regime draws on the FATF framework wholesale: customer due diligence, transaction monitoring, suspicious activity reporting, and the Travel Rule data-transmission obligation all apply from the moment a firm is authorised.
FATF's Recommendation 15 requires VASPs to obtain, hold and transmit originator and beneficiary information with each transfer that meets or exceeds the applicable threshold. The precise de-minimis figure for the AIFC is subject to AFSA's current published rules – consult those directly, as thresholds vary by jurisdiction and are subject to regulatory revision. What is settled is the principle: transfers above the threshold must carry the data; transfers below it must still be monitored for structuring risk.
The AIFC is not a passive adopter. In our cross-border practice, we have seen AFSA examiners request specific documentation of how a firm's VASP counterparty selection process integrates Travel Rule messaging. That is an operational detail many new entrants underestimate.
Operators entering the AIFC should treat Travel Rule readiness as a pre-authorisation deliverable, not a post-licensing task.
What a Travel Rule compliance program must contain under the AIFC framework
A compliant Travel Rule program for an AIFC-authorised VASP has five structural components. Each one maps directly to an AFSA examination area.
First, counterparty VASP due diligence. Before transmitting or receiving a transfer, your firm must verify that the counterparty VASP is licensed or registered in its own jurisdiction, that it maintains a comparable AML/CFT program, and that the relationship is documented. This is the "sunrise problem" in practice: if the receiving VASP cannot accept Travel Rule data in the required format, the sending VASP may still be liable for the failure.
Second, a data-collection and transmission protocol tied to your core systems. Originator name, account identifier, and – depending on threshold – physical address or national identification must be collected at the point of customer onboarding and attached to the outbound transfer instruction. The protocol must be documented in writing and tested at least annually.
Third, a KYC framework (know-your-customer procedures) that is genuinely integrated with Travel Rule triggers. Many firms maintain a KYC process and a Travel Rule process as parallel workflows; AFSA examiners look for the integration point where a customer's verified identity data feeds the Travel Rule transmission without manual re-entry. Manual re-entry is an audit flag.
Fourth, transaction monitoring calibrated for virtual-asset risk typologies: chain-hopping, mixer use, structuring below the Travel Rule threshold, and counterparty exposure to sanctioned addresses. The monitoring system should generate alerts that your compliance team can action with documented outcomes.
Fifth, a Money Laundering Reporting Officer (MLRO) who is a named individual, with documented authority to file suspicious activity reports to the AIFC Financial Intelligence Unit, approve the Travel Rule policy, and escalate to senior management. The MLRO cannot be a shared resource across multiple licensed entities without AFSA's explicit acceptance of that arrangement.
How cross-border operations add complexity to Travel Rule compliance
A single-office AIFC entity rarely serves only Kazakhstani counterparties. The cross-border reality – users in the EU, banking in Singapore or the UAE, settlement through a US correspondent – multiplies the Travel Rule surface area significantly.
When an AIFC-authorised VASP sends a transfer to a counterparty in the EU, it is interacting with a VASP that operates under the MiCA regime and the EU's Transfer of Funds Regulation, which imposes its own Travel Rule requirements administered by ESMA and national competent authorities. The data fields required under the EU regime are not identical to those the AFSA mandates. Your protocol must handle both, which means your Travel Rule messaging solution must support multi-format output.
In the UAE, a counterparty licensed by VARA (the Virtual Assets Regulatory Authority in Dubai) or the FSRA in Abu Dhabi also operates under a local AML/CFT regime. VARA and AFSA share a common FATF Recommendation 15 foundation, but their implementation rules differ on verification timing and threshold treatment. We regularly advise clients who run a VARA entity and an AIFC entity in parallel – the internal policy must reconcile both regimes without creating a compliance gap in either direction.
Banking is the pressure point that most operators feel first. A correspondent bank serving your AIFC entity will conduct its own VASP due diligence, typically modelled on the Wolfsberg Group's VASP questionnaire or an equivalent framework. If your Travel Rule program documentation is incomplete, the bank will either reject the relationship or impose enhanced due diligence that adds friction to every wire. Operating without the right compliance posture risks enforcement, frozen rails and lost banking – this is not a hypothetical for AIFC operators; it is the documented experience of several early entrants to the regime.
Tax interaction is a secondary but real consideration. Transfer-level data captured for Travel Rule purposes often becomes relevant to withholding-tax analysis and VAT/GST treatment of service fees in the jurisdictions where your users sit. Your compliance data architecture should be built so that the same underlying customer and transaction records can serve both AML and tax reporting without creating conflicting data sets.
For a scoped assessment of your Travel Rule program across AIFC, VARA and MiCA touchpoints, contact OBOLUS at info@oboluslaw.com. The cross-border configuration is where most programs fail their first external review. Map your options before that review is scheduled.
How to build a Travel Rule compliance program for the AIFC: a practical sequence
The AFSA expects a written, board-approved AML/CFT program before it issues an operating permission, and a functioning Travel Rule sub-program before you process your first transfer. The build sequence below reflects what a well-structured initial program looks like in practice.
Step 1: Legal gap analysis. Map your proposed product activities against the AFSA's applicable AML/CFT rules to identify which transfers trigger Travel Rule obligations, which customer segments require enhanced due diligence, and which third-party VASPs you intend to transact with. The gap analysis should also identify the applicable threshold and the data fields required for each transfer category under the current AFSA rulebook.
Step 2: Technology selection. Choose a Travel Rule messaging protocol and platform. The leading interoperability protocols in the market allow VASPs to transmit structured originator and beneficiary data peer-to-peer, but no single protocol covers every counterparty globally. Your solution must accommodate counterparties on different protocols; a "no-match" scenario – where the receiving VASP is unreachable through any supported protocol – must have a documented manual fallback.
Step 3: Policy drafting. The written AML/CFT policy and the Travel Rule annex must be drafted to AFSA standards. This means naming the MLRO, defining the escalation chain, specifying the data retention period, and describing the transaction monitoring thresholds and alert-review workflow. Policies drafted for a different jurisdiction and lightly amended rarely pass AFSA scrutiny; the examiner reads for the AIFC-specific obligations.
Step 4: KYC integration. Wire the Travel Rule data fields into your onboarding workflow so that verified identity data populates the outbound transfer instruction automatically. Test the integration before go-live with a defined sample of synthetic transactions. Document the test results.
Step 5: Staff training and MLRO appointment. The MLRO must be trained on the AFSA's suspicious activity reporting obligations and on the specific triggers for a Travel Rule escalation. All staff with client-facing or transaction-processing roles require AML training documented with signed completion records.
Step 6: Board approval and submission. The board or equivalent governing body approves the final policy. The MLRO and CEO sign the compliance attestation submitted to AFSA as part of the operating permission application or the annual regulatory return.
Step 7: Ongoing monitoring and annual review. The program is a living document. Transaction monitoring rules require calibration as volume and customer mix evolve. AFSA expects annual policy reviews and an annual MLRO report to the board. Third-party audits, while not always mandatory in year one, are increasingly expected as the AIFC's supervised population grows.
In a recent compliance build, a digital-asset trading firm seeking AIFC authorisation engaged OBOLUS in the early months of its application cycle. Its prior AML policy had been drafted against a different jurisdiction's VASP regime and contained no Travel Rule annex specific to virtual-asset transfers. We rebuilt the policy from the AFSA's published AML/CFT rules, integrated the Travel Rule workflow into the onboarding system specifications, and supported the MLRO appointment process. The firm received its operating permission without a request for additional information on the AML documentation – a materially faster path than its prior attempt.
Which operator profile suits an AIFC Travel Rule build – and which does not
The AIFC is not the right compliance home for every digital-asset business. Understanding where it fits and where it does not saves a significant amount of time and regulatory capital.
Profile A – Regional exchange serving Central Asia and the CIS. This profile is well-suited to the AIFC. The AFSA regime is designed for the region, the common-law environment supports commercial dispute resolution, and the jurisdiction's FATF-aligned AML/CFT framework satisfies the correspondent banks that service this geography. The Travel Rule build is straightforward if the counterparty VASP universe is primarily FATF-member jurisdictions. Timeline to a functioning program: typically a matter of weeks from policy gap analysis to board sign-off, assuming technology is already selected.
Profile B – European operator seeking a secondary hub for CIS distribution. This profile works, but the MiCA/ESMA obligations in the home jurisdiction must be reconciled with the AFSA regime from day one. The Travel Rule data fields, the threshold treatment, and the correspondent-bank reporting obligations must be harmonised across both entities. Attempting to run two separate, non-integrated compliance programs creates the gaps that trigger enforcement in both jurisdictions.
Profile C – US-facing exchange seeking an offshore VASP registration. This profile is problematic regardless of jurisdiction. A common assumption is that a single offshore licence is enough to serve clients globally, including US clients; it is not. US persons trigger SEC, CFTC, FinCEN and state money-transmitter obligations that the AIFC licence does not address. An AIFC Travel Rule program is necessary but not sufficient for a US distribution strategy.
Profile D – DeFi protocol with no identifiable counterparty VASPs. This profile sits at the edge of the AFSA's current regulatory perimeter. The Travel Rule applies to VASPs conducting transfers; a genuinely decentralised protocol may not fall within the definition. However, the deployment entity, the front-end operator or the treasury management function may each independently qualify. The analysis must be done before a compliance program is designed.
Common mistakes in AIFC Travel Rule programs – and how to avoid them
AFSA examiners see the same structural failures repeatedly. Identifying them in advance is half the work.
The most common failure is a policy that names the Travel Rule obligation but does not describe the operational process for satisfying it. "We comply with the Travel Rule" is not a compliance program. The AFSA expects a documented workflow: who collects the data, how it is verified, which system transmits it, and what happens when the counterparty VASP cannot receive it.
The second failure is an MLRO who is nominally appointed but operationally powerless. If the MLRO cannot access transaction-level data, cannot halt a withdrawal pending review, and cannot escalate to the board without going through the CEO, the appointment is a formality. Regulators in the leading hubs increasingly expect the MLRO to have a direct reporting line to the board or audit committee, independent of commercial management.
The third failure is a transaction monitoring system calibrated for fiat payments and never adapted for on-chain risk. Blockchain analytics is not a luxury; it is the only way to detect mixer exposure, chain-hopping and sanctions linkages that fiat-era monitoring tools miss entirely. An AIFC-licensed VASP that processes virtual-asset transfers without on-chain monitoring is, in practice, operating blind to a material portion of its AML risk.
The fourth – and arguably most commercially consequential – failure is entering the AIFC on the assumption that the Travel Rule program can be deferred until after banking is established. It cannot. The bank's VASP due diligence questionnaire will ask directly whether a Travel Rule program is in place. Without it, the account is not opened.
If a prior application stalled or a banking relationship was refused on compliance grounds, a structured second read of your program can surface the specific gap. Reach OBOLUS at info@oboluslaw.com to arrange a scoped review. Map your options before the next application cycle.
Related at OBOLUS
- AML and Travel Rule compliance for digital-asset businesses – the full practice overview across all major licensing jurisdictions
- AML/CFT policy drafting for established operators – structured policy builds and gap remediation for operating VASPs
- Stablecoin freeze requests in Switzerland – cross-border recovery mechanics when on-chain assets must be frozen quickly
FAQ
What does the Travel Rule require from a VASP?
The Travel Rule requires a VASP to collect verified originator and beneficiary information – including name and account identifier, and in some cases address or identification number – and transmit that data to the receiving VASP alongside every qualifying transfer. The obligation applies at or above the applicable threshold set by the relevant regulator and is derived from FATF Recommendation 15, which the AFSA's AML/CFT regime implements directly. Transfers below the threshold still require monitoring for structuring risk.
Who must act as MLRO for a crypto firm?
An AIFC-authorised VASP must appoint a named individual as Money Laundering Reporting Officer (MLRO) with documented authority to file suspicious activity reports, approve the AML/CFT policy, and escalate to the board. The MLRO cannot be a purely nominal appointment; the AFSA expects evidence that the role is operationally functional. Shared MLRO arrangements across multiple licensed entities require the regulator's explicit acceptance and are scrutinised closely on examination.
How do regulators audit crypto AML programs?
AFSA examinations of AML/CFT programs typically cover four areas: the written policy and its board approval trail; the operational Travel Rule workflow and its integration with the KYC framework; the transaction monitoring system and its calibration for virtual-asset risk typologies; and the MLRO's records of suspicious activity reviews and escalations. Examiners request sample transaction records to verify that the documented process was followed in practice. Firms that maintain a policy without corresponding operational records fail on the final point.
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 every structure. Digital assets are the whole of our practice. We map the licence, banking and Travel Rule compliance stack across operating, custody and payment layers before you commit – and our disputes team coordinates freezing relief and on-chain tracing across leading common-law forums when recovery is needed. To discuss your situation, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – specialises in AML/CFT program design and Travel Rule implementation for VASPs across AIFC, MiCA and VARA regimes.
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.