Every virtual asset service provider operating under the Bank of Lithuania's supervisory regime must maintain a transaction monitoring program that satisfies the applicable AML/CFT provisions and the FATF standards they implement. As MiCA (the EU Markets in Crypto-Assets Regulation) reshapes the compliance baseline across every member state, a Lithuania-registered CASP (crypto-asset service provider) faces a higher and more auditable standard than the prior VASP registration framework demanded. Getting the program wrong is not a technical failure – it is an enforcement event, and enforcement in Lithuania has historically moved faster than operators expect.
Transaction monitoring, under the Bank of Lithuania's AML/CFT supervisory posture, means real-time or near-real-time detection of unusual or suspicious patterns, documented risk appetite, rule logic tied to a written risk assessment, and a functioning escalation path to the designated MLRO (Money Laundering Reporting Officer). The regime is not satisfied by off-the-shelf software running on default settings. Regulators expect calibrated thresholds, peer-reviewed rule sets, and evidence that alerts are acted upon. This page maps the regulated basis, the practical build-out, the cross-border interaction with banking and tax, and the decision point for an inbound operator.
What is the regulatory basis for transaction monitoring in Lithuania?
The Bank of Lithuania supervises VASP and CASP compliance obligations under the national AML law that implements the EU's successive AML Directives, reinforced by the FATF Recommendations – in particular FATF Recommendation 15, which extends the anti-money-laundering and counter-terrorist-financing standard to virtual asset activities. Under the MiCA transition, firms that held VASP registration are expected to progress to CASP authorisation, and the compliance obligations migrate with that authorisation: the underlying AML/CFT duties are continuous, not replaced. The Bank of Lithuania has issued supervisory guidance making clear that VASP/CASP entities must demonstrate a live, calibrated transaction monitoring function – not merely a policy document stating that one exists.
The legal architecture matters for an inbound business because Lithuania has historically been an accessible EU entry point. Its regulator is a national competent authority under MiCA, which means that a CASP authorised here may passport across the EU and EEA. That passporting benefit is available only to entities that sustain full compliance on home-state terms. A monitoring program that satisfies a lighter offshore standard will not satisfy the Bank of Lithuania on examination.
In our cross-border practice, we have seen firms arrive in Lithuania with monitoring setups built for a Caribbean or Pacific registration – lighter on rule logic, absent a functioning MLRO, and with no documented risk-appetite statement tied to the Lithuanian customer base. The gap between that baseline and what the Bank of Lithuania expects on inspection is significant.
For a scoped assessment of your current AML program against the Bank of Lithuania's supervisory expectations, contact OBOLUS at info@oboluslaw.com. The process above describes the standard path. Your facts – the entity, the user base, the banking – change the analysis. Map your options.
What does a compliant transaction monitoring program actually cover?
A compliant program under the Bank of Lithuania's expectations covers five operational layers: a written risk assessment, calibrated detection rules, alert triage and disposition, Suspicious Activity Reporting (SAR) to the Financial Crime Investigation Service (FCIS), and a record-keeping architecture that survives a regulatory inspection. Each layer must be documented, tested, and owned by a named individual.
The risk assessment is the document that all other layers reference. It must categorise the firm's customer types, product lines, geographies, and delivery channels by money-laundering and terrorist-financing risk. Rule logic in the monitoring system must demonstrably connect to the risks identified in that assessment. A regulator finding rule logic that does not map to the risk assessment will treat the entire program as deficient.
Detection rules must cover, at minimum: structuring and aggregation patterns, rapid cycling through wallets, high-frequency low-value transactions inconsistent with customer profile, unexplained geographic exposure, and on-chain indicators associated with sanctions-listed addresses or mixers. The system is expected to use both rules-based and – increasingly – behaviour-based alert generation. Default vendor rules are a starting point, not a finish line.
Alert triage requires a documented workflow. An alert must be assigned, reviewed against customer and transaction context, resolved with a written disposition, and, where escalated, routed to the MLRO within a defined time window. The MLRO then decides whether to file an SAR with the FCIS or close the alert with documented reasoning. That workflow must be tested and the test results retained.
Record-keeping obligations run for a minimum period set under the national AML law; firms must ensure their data architecture can produce a complete transaction record for any customer account within the timeframe a regulator's production order specifies. Cloud-based architectures do not reduce this obligation – they require additional documentation of where data sits and how it is retrieved.
How does the Travel Rule interact with transaction monitoring in Lithuania?
The Travel Rule – the obligation to collect, verify, and transmit originator and beneficiary identification data alongside a virtual asset transfer – operates in parallel with transaction monitoring, not as a substitute for it. Under the FATF standard and its EU-level implementation, a Lithuanian CASP must pass Travel Rule data on transfers above the applicable threshold and must screen that data against sanctions lists before a transfer executes.
The practical integration point is the pre-transaction screening workflow. If the monitoring system flags a transfer for review at the same moment that the Travel Rule obligates the firm to transmit originator data, the two workflows must not conflict. In practice, this means the monitoring system and the Travel Rule compliance tool must share a data model or be integrated so that a hold on one leg does not create a regulatory gap on the other.
Lithuania, operating under the Bank of Lithuania and now converging on MiCA, applies the Travel Rule to crypto-asset transfers in line with the EU Transfer of Funds Regulation (TFR) as it extends to crypto assets. The data threshold and the verification standard are set at EU level under that regulation. Firms must maintain a counterparty VASP/CASP identification process – knowing that the receiving entity at the other end of a transfer is itself a regulated and compliant institution – and that process must be documented and periodically reviewed.
Operators we advise routinely underestimate the operational complexity of the counterparty-identification element. Sending Travel Rule data to an unknown or unverified CASP is itself a compliance gap. The monitoring program must include a process for evaluating and re-evaluating the counterparty universe.
How does the KYC framework connect to transaction monitoring?
Transaction monitoring is only as good as the customer data it runs against. A KYC (Know Your Customer) framework that fails to collect accurate source-of-funds information, beneficial ownership detail, or expected transaction patterns will generate monitoring rules that cannot distinguish unusual from expected. The Bank of Lithuania expects both the KYC program and the monitoring program to be documented as parts of an integrated AML/CFT system, not as separate functions owned by separate teams with no shared data.
At onboarding, the customer risk rating produced by the KYC process must feed directly into the monitoring rule set. A customer rated as higher risk must attract tighter monitoring thresholds, shorter review cycles, and enhanced due diligence triggers. If the KYC and monitoring systems are separate platforms, the firm must demonstrate a documented data-transfer process that keeps the monitoring system current as customer risk ratings change.
In our cross-border practice, we regularly advise operators who have inherited a KYC platform from a prior corporate group that was not built for virtual-asset risk. The customer data architecture may be adequate for a payments firm but will miss the on-chain behavioral signals that the Bank of Lithuania expects a CASP-class firm to monitor. Bridging that gap requires either system integration or a documented manual process, and neither option is fast.
Enhanced due diligence obligations attach to customers who are politically exposed persons (PEPs), who operate from high-risk jurisdictions identified under FATF guidance, or who are identified as higher risk in the firm's own risk assessment. The monitoring system must carry those flags so that the triage team reviewing alerts can apply the correct intensity of review.
If a prior application stalled or an account was closed, a second read can surface the structural reason and the route back. Write to OBOLUS at info@oboluslaw.com or map your options here.
Who must act as MLRO and how is governance structured?
A Lithuania-registered CASP must appoint a named MLRO who satisfies the Bank of Lithuania's fitness and propriety expectations for that function. The MLRO is the officer responsible for receiving internal disclosures, making external SAR filings with the FCIS, and overseeing the AML/CFT program as a whole. The role cannot be shared with a function that generates a conflict of interest – most commonly a revenue or business development role.
Under the applicable AML provisions, the MLRO must have the seniority and independence to act on a disclosure without requiring board approval for each filing. In practice, that means either a direct reporting line to the board or a documented escalation protocol that allows the MLRO to file an SAR and simultaneously notify the board, rather than seeking prior authorisation. The Bank of Lithuania has examined governance arrangements where the MLRO lacked effective independence and treated the resulting SARs as potentially compromised.
For cross-border operators – a parent entity in a third country with a Lithuanian CASP as a subsidiary – the MLRO must be an individual with genuine authority over the Lithuanian entity's AML/CFT decisions. Group-level compliance frameworks are permitted, but the Lithuanian MLRO cannot be a figurehead who defers every decision to a non-EU parent compliance team. Regulators in the leading hubs increasingly expect the local compliance officer to demonstrate actual decision-making authority and knowledge of the local regulatory standard.
The MLRO function must be supported by a documented training program for all staff who handle customer transactions or alerts. Training records must be maintained. The Bank of Lithuania has made clear in its supervisory communications that an MLRO who cannot demonstrate that staff are trained to the current standard is an indicator of systemic program weakness.
How does transaction monitoring interact with banking and cross-border operations?
A Lithuania-registered CASP's transaction monitoring obligations do not stop at the boundary of the crypto rails. Fiat inflows and outflows – client deposits, client withdrawals, settlement flows – run through Lithuanian or EU-licensed banking and payment institutions, and those institutions apply their own AML/CFT monitoring to the same flows. Misalignment between the CASP's monitoring program and the bank's expectations is a recurring cause of account closure.
Banks providing EUR accounts to CASPs in Lithuania expect to see a monitoring program at least as rigorous as their own. They will ask, in the course of account maintenance, for evidence that the CASP screens its customers against sanctions lists, applies Travel Rule obligations, and has a functioning SAR process. A CASP that cannot produce that evidence in a form the bank's compliance team can assess will face progressive derisking – reduced transaction limits, requests to move volume elsewhere, and ultimately account termination.
Operators we advise routinely discover this interaction only after a banking relationship is in distress. The monitoring program that satisfies the Bank of Lithuania from a regulatory perspective must also be documentable in a form that a commercial bank's compliance team can evaluate quickly. That means a written summary of the program, the technology in use, the rule logic (at a level of abstraction that does not expose proprietary models), and the governance structure – all in a form that a non-specialist reader can assess in under an hour.
For a Lithuanian CASP with users or business flows across EU member states – the expected case for a firm using MiCA passporting – the monitoring program must address the risk profile of the full user base, not just Lithuanian-resident customers. A passporting firm serving customers in high-risk jurisdictions who happen to access the service through the Lithuanian entity still carries that risk on its books. The risk assessment must reflect it, and the monitoring rules must address it.
A recent monitoring matter: cross-border CASP in transition
In a recent compliance matter, a payments-adjacent crypto business had operated under a pre-MiCA VASP registration in Lithuania for several years with a monitoring program built for low transaction volumes and a predominantly domestic customer base. When the operator expanded to serve EU customers through passporting, the monitoring rule set did not scale: thresholds calibrated for domestic wire-equivalent amounts generated almost no alerts on cross-border transfers that were, on any objective analysis, high-risk. The Bank of Lithuania's examination identified the gap. We were engaged to conduct a gap analysis, rebuild the risk assessment to reflect the expanded customer universe, recalibrate rule logic, and document the remediation for regulatory submission. The operator retained its authorisation and banking relationships. The timeline from engagement to regulatory sign-off was a matter of weeks – not months – because the underlying data architecture was sound and the MLRO was cooperative throughout.
Which monitoring setup profile fits your business?
Profile A – Early-stage CASP seeking authorisation: The priority is building a monitoring program that satisfies the Bank of Lithuania's initial authorisation review. The risk assessment, rule logic, and MLRO governance must be in place before application. The system need not be the most sophisticated available, but it must be documented, calibrated to the firm's product and customer risk profile, and owned by a qualified MLRO. Timeline to a functional program: typically several weeks from a clean starting point, longer where KYC and monitoring systems must be integrated.
Profile B – Established CASP expanding under MiCA passporting: The monitoring program must be recalibrated to the expanded customer and geographic risk profile. The Travel Rule integration must cover the counterparty universe in each passported jurisdiction. Banking relationships in the host member states will scrutinise the program independently of the Bank of Lithuania. Remediation after a bank flags a program gap typically takes longer than pre-emptive calibration. Engage counsel before the passport notification, not after the bank query arrives.
Profile C – Inbound group with a non-EU parent and a Lithuanian CASP subsidiary: The MLRO governance, the risk assessment, and the monitoring rules must be locally owned. A group-level AML program that does not address Lithuanian-specific risk indicators and does not grant the local MLRO genuine decision-making authority will not satisfy the Bank of Lithuania. The cross-border interaction between the parent's compliance framework and the Lithuanian entity's obligations must be documented. Failure to document it is itself a compliance gap that examination will surface.
A common assumption is that a single offshore licence, supported by a group-level compliance program, is sufficient to serve clients globally. In our experience, that assumption is the most frequent structural error we encounter. The Bank of Lithuania – like every national competent authority under MiCA – requires a locally anchored program. The offshore entity's compliance standard is a floor, not a substitute.
Related at OBOLUS
- Compliance, AML & Travel Rule for digital-asset businesses – the full practice area covering AML program design, Travel Rule implementation and MLRO advisory across jurisdictions.
- KYC and onboarding framework from a cross-border perspective – how customer due diligence integrates with transaction monitoring across multi-jurisdiction operations.
- Corporate bank account opening from a cross-border perspective – the banking interaction with AML program documentation and CASP account maintenance.
FAQ
What does the Travel Rule require from a VASP?
The Travel Rule requires a VASP or CASP to collect, verify, and transmit originator and beneficiary identification data alongside virtual asset transfers above the applicable threshold. Under the EU Transfer of Funds Regulation as extended to crypto assets, this applies across transfers between regulated entities. The sending firm must verify counterparty VASP/CASP status and retain records of all data transmitted. Non-compliance is a reportable deficiency under both FATF standards and the Bank of Lithuania's supervisory framework.
Who must act as MLRO for a crypto firm?
A Lithuania-registered CASP must appoint a named, fit-and-proper individual as MLRO. That person must have genuine decision-making authority over SAR filings, be independent of revenue-generating functions, and report to the board or have a direct escalation path to it. For group structures with a non-EU parent, the Lithuanian MLRO must exercise local authority – they cannot defer all decisions to a parent compliance team. The Bank of Lithuania expects the MLRO to demonstrate knowledge of the Lithuanian and EU regulatory standard.
How do regulators audit crypto AML programs?
The Bank of Lithuania examines AML/CFT programs through document review, system demonstrations, and interviews with key personnel including the MLRO. Examiners will test whether the risk assessment maps to the rule logic, whether alerts are actioned within documented timeframes, and whether SAR filings are timely and well-reasoned. Record-keeping is examined against the minimum retention period in the national AML law. A program that exists on paper but is not operationally embedded will be identified as deficient and may result in remediation orders or, in serious cases, supervisory action on the authorisation.
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. We map the licence stack across operating, custody and payment layers before you commit. Digital assets are the whole of our practice. We advise crypto exchanges, custodians, token issuers and funds across more than seventy licensing jurisdictions. To discuss your situation, contact info@oboluslaw.com or email us at info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – specialising in AML/CFT program design, transaction monitoring architecture, and supervisory engagement for digital-asset businesses in EU and cross-border licensing contexts.
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.