Correspondent banking access in Lithuania has become a defining operational challenge for digital-asset businesses that chose the jurisdiction as their EU regulatory anchor. A VASP (virtual asset service provider) or EMI (electronic money institution) registered under the Bank of Lithuania's supervision can hold a licence and still find itself without a single functional fiat rail – because the licence and the bank account are two entirely separate relationships, governed by different rules and different risk appetites. The question every operator in this situation faces is not whether Lithuania is a viable home, but whether the business can build the banking architecture that makes the licence operational. This page maps that architecture: the regulatory basis, the practical route to correspondent access, the cross-border complications, and where the process breaks down.
Why Banking Is the Harder Problem Than the Licence
Securing fiat rails in Lithuania is genuinely harder than securing the licence itself, and operators who treat them as sequential rather than parallel problems lose months. The Bank of Lithuania administers VASP registration and, under the transition to MiCA (Markets in Crypto-Assets Regulation), will serve as the national competent authority for CASP authorisation across the EU. That regulatory standing is real and passport-capable. It does not, however, compel any bank to open an account.
Lithuanian commercial banks – and the international correspondent banks behind them – apply their own anti-money-laundering frameworks independently of the Bank of Lithuania's licensing decisions. A bank's compliance function will evaluate the business model, the customer base, the transaction volumes, the jurisdictions touched and the control environment. A freshly issued licence addresses none of those concerns on its own. In our cross-border practice, we regularly advise clients who assumed that regulatory approval would smooth the path to banking. It does not. It is necessary but not sufficient.
The correspondent banking problem is also structural. Most Lithuanian banks settle euros through a correspondent relationship with a larger European clearing bank. That correspondent applies its own AML and sanctions policies to the traffic passing through it. If the correspondent bank deems crypto-originated flows to carry unacceptable risk, it can instruct the Lithuanian bank to exit certain business categories – regardless of the client's licence status or compliance quality. Operators who do not map this layered structure before they launch consistently face a frozen-rails scenario within their first operating year.
Operating without secured fiat rails while holding a live licence is not a neutral position. It exposes the business to customer complaints, regulatory questions about operational readiness, and in some structures, to a determination that the licence is dormant – with consequences for renewal under MiCA.
For a scoped assessment of your banking architecture before you commit to Lithuania, contact OBOLUS at info@oboluslaw.com. The process above describes the standard path. Your facts – the entity structure, the user base geography, the transaction profile – change the analysis materially. Map your options
The Regulatory Basis for Banking Access
The right to access payment systems in Lithuania derives from the EU's Payment Services Directive framework, which the Bank of Lithuania transposes. Payment institutions and EMIs authorised in Lithuania hold a statutory right of access to payment systems on objective, non-discriminatory and proportionate terms. VASPs registered under the anti-money-laundering regime do not hold the same statutory access right – their banking relationships are commercial, not mandated.
This distinction matters enormously for structuring. A business that holds only a VASP registration sits in a different legal position than one that also holds a payment institution or EMI authorisation from the Bank of Lithuania. The latter can invoke the access framework; the former is dependent entirely on commercial negotiations with individual banks and their correspondents.
MiCA introduced the CASP authorisation category, which transitions the prior VASP registration model into a full licence regime. MiCA's passporting mechanism allows a CASP authorised in Lithuania to provide services across the EU and EEA without a separate licence in each member state. That passporting right improves the regulatory profile of the business in the eyes of some banks – it signals that the entity has passed a more substantive supervisory review. It does not, however, resolve the correspondent banking question directly. Banks assess the passport as one data point among many.
The applicable AML framework – rooted in the FATF Recommendations, specifically Recommendation 15 on virtual assets, and the Travel Rule (the obligation to pass originator and beneficiary data with a transfer) – also shapes banking access. A business that can demonstrate a mature Travel Rule compliance programme, robust transaction monitoring and a clean VASP forensics posture will move through bank compliance diligence materially faster than one that cannot. The legal and the operational are inseparable at this stage.
Who Needs Correspondent Banking Access in Lithuania?
The businesses most acutely affected by the Lithuanian correspondent banking problem are those whose revenue model depends on fiat-crypto or crypto-fiat conversion at scale – exchanges, OTC desks, payments companies and custodians that hold client fiat balances. Token issuers with treasury management needs and funds with subscription/redemption flows are similarly exposed. Each of these profiles faces the same underlying dynamic: the licence enables the activity, but the bank account enables the revenue.
An operator running a crypto exchange in Lithuania that cannot move euros in and out of client wallets effectively cannot operate. An OTC desk without a correspondent-connected account cannot settle trades. A custodian that cannot receive client fiat to convert to custodied assets cannot onboard institutional clients. In each case, the banking gap is a business-ending constraint, not a compliance inconvenience.
The cross-border dimension intensifies the problem. Many Lithuanian-licensed businesses serve users across the EU and beyond. Their banking partners must be comfortable with cross-border flows, with the jurisdictions of the customers they are serving, and with the transaction patterns that emerge. A bank comfortable with Lithuanian retail flows may be uncomfortable with flows from high-risk jurisdictions – even if those flows are fully licensed and compliant under the applicable regime.
How Can a VASP or EMI Secure Banking Access in Practice?
Securing correspondent banking access in Lithuania requires a structured, multi-track approach rather than a sequential application to a list of banks. The process begins with pre-engagement positioning, not with a bank application form.
The first step is documentation architecture. A bank's compliance team will need a complete picture of the business – the licence or registration, the AML/KYC policy suite, the transaction monitoring system, the beneficial ownership structure, the customer base profile, the expected transaction volumes and corridors, and the controls around high-risk activity. Businesses that submit this package in a coherent, pre-organised form reduce the time from initial outreach to a compliance decision by a meaningful margin. In our practice, we have seen structurally identical businesses with identical licences separated by many months in their banking timelines purely because of documentation quality and sequencing.
The second step is target bank selection. Not all banks that formally accept crypto clients in Lithuania maintain the same correspondent relationships or the same risk appetite for every business model. An exchange with high-volume retail flows faces different scrutiny than a B2B payments company with a small number of institutional counterparties. Matching the business profile to the right banking partner – including the partner's upstream correspondent – is a legal and commercial judgement that precedes any application.
The third track is the EMI route. Where a business cannot secure a direct bank account with a correspondent-connected Lithuanian bank, an EMI (electronic money institution) authorised under the Bank of Lithuania can serve as a bridge – providing IBANs, holding client funds against safeguarding requirements, and connecting to payment networks. The EMI route is increasingly the primary fiat rail for crypto businesses in Lithuania, not the backup. Understanding which EMIs maintain active correspondent relationships, which accept crypto-originated business and which can support the required transaction corridors is itself a subject of ongoing legal and commercial intelligence.
A fourth, less visible track is the IBAN segregation structure. Client money safeguarding requirements under the applicable payment services regime require that client funds be held separately from the institution's own funds. Some EMIs achieve this through trust accounts with named credit institutions; others through insurance or guarantee instruments. The choice of safeguarding method affects which banks will engage and on what terms. Getting the structure right from the outset avoids a rebuild later.
If a prior banking application stalled or an account was unexpectedly closed, contact OBOLUS at info@oboluslaw.com. A second structural read frequently surfaces the underlying compliance gap or the correspondence-bank pressure that drove the decision – and the route back. Map your options
The Cross-Border Interaction: Tax and Banking
A Lithuanian entity's banking architecture does not exist in isolation. The jurisdictions where the business's customers are located, where the entity's parent or shareholders sit, and where the management and control functions operate all feed into both the tax analysis and the banking risk assessment. Operators who treat the Lithuanian entity as a standalone often discover that its banking relationships depend heavily on the group structure around it.
From a tax perspective, a Lithuanian operating entity that books revenue from EU customers will face Lithuanian corporate tax on Lithuanian-source profits, and the question of whether cross-border intra-group flows are priced at arm's length. Banks are increasingly sensitive to transfer pricing arrangements – particularly where a Lithuanian entity appears to be a front for a group whose economic substance sits elsewhere. A bank that identifies a thin-substance structure during onboarding diligence will either refuse the account or impose enhanced ongoing monitoring that becomes operationally burdensome.
The VAT treatment of crypto-related services also interacts with banking. In Lithuania, as across the EU, the VAT treatment of virtual currency exchange services broadly follows the principle established in EU case law that currency exchange is VAT-exempt. But advisory fees, token-issuance services and certain platform revenues may be taxable. A business that has not correctly characterised its revenue streams may present a confusing picture to a bank compliance function that is assessing AML risk partly through transaction volume and revenue logic.
For businesses with shareholders or management in jurisdictions outside the EU, the correspondent banking problem extends to the ultimate beneficial ownership disclosure. A bank onboarding a Lithuanian VASP will request KYC on every UBO above the applicable threshold. If those UBOs are in jurisdictions on the Financial Action Task Force's high-risk or monitored lists, the application will face enhanced scrutiny or outright refusal – regardless of the Lithuanian entity's own compliance profile. We map UBO jurisdictions as part of pre-engagement structuring precisely to avoid this collision.
Common Mistakes That Kill Banking Access
The mistakes that most reliably destroy a Lithuanian banking application are structural, not technical. They happen before the application is submitted, not during it.
The first is timing. Businesses that seek banking after they have launched operations – with a transaction history already on-chain and customers already waiting – present a more complicated risk picture than those that secure banking before going live. Banks can review a clean, prospective business model. They struggle with a live business that is already generating unexplained crypto flows without a banking relationship to anchor them.
The second is entity complexity without explanation. A Lithuanian VASP that is one of four group entities – with a Cayman holding company, a BVI IP entity and a UAE operational subsidiary – is not automatically a problem. But it is a problem if the compliance documentation does not explain the group structure clearly and demonstrate why it is structured that way. Banks do not give the benefit of the doubt to unexplained complexity.
The third is a mismatch between the stated business model and the actual transaction profile. A company that described itself to the Bank of Lithuania as a B2B settlement layer but presents a bank with retail transaction patterns will face immediate questions. Consistency between the regulatory filing, the compliance documentation and the actual operating model is not just a best practice – it is a prerequisite for banking access.
The fourth – and perhaps the most common in our experience – is the myth that a single licence is sufficient for global operations. A Lithuanian VASP registration does not authorise the business to serve customers in Singapore, the United States or the United Kingdom without separate local authorisation or a careful jurisdictional analysis. A bank whose correspondent sees traffic patterns that suggest unlicensed cross-border service provision will terminate the relationship. The regulatory perimeter and the banking perimeter must align.
Micro-Matter: Stabilising a Payments Company in Distress
In a recent matter, a payments company holding a Bank of Lithuania payment institution licence had its correspondent banking relationship terminated at short notice after its upstream correspondent revised its crypto-business policy. The business had no secondary banking relationship and faced an operational standstill within days. We were engaged on an emergency basis in the same week the notice was received. We undertook a rapid structural audit – reviewing the entity's AML documentation, transaction monitoring outputs, UBO profile and existing correspondent exposure – and identified two EMIs with active correspondent relationships and demonstrated experience in similar business models. We prepared the full onboarding package within the relevant SLA and the entity was operational on a primary EMI rail within a matter of weeks. A secondary bank relationship was established in the following month. The business retained its regulatory standing throughout and faced no enforcement action.
Decision Matrix: Which Profile Should Choose Which Route
The right banking route in Lithuania depends on the operator's profile, transaction scale and cross-border exposure. No single structure suits every business.
A retail exchange with high-volume, multi-corridor flows and a large EU customer base should pursue a direct correspondent-connected bank account as the primary structure, backed by an EMI as a contingency rail. The compliance documentation burden is substantial. The timeline from first outreach to a live account varies by institution but is consistently measured in months, not weeks. The key risk is upstream correspondent policy change – a structural risk that requires ongoing monitoring and a maintained backup relationship.
A B2B OTC desk or settlement-layer business with a small number of institutional counterparties and predictable, documented flows is a materially easier bank onboarding proposition. EMI-first structures work well for this profile; the compliance narrative is cleaner. Timeline is shorter. The key risk is counterparty jurisdiction – if the institutional clients include entities in jurisdictions on monitored lists, the risk profile elevates regardless of the business's own clean record.
A custodian with client fiat balances requires a safeguarding-compliant account structure – typically a trust account or a ring-fenced client account at a credit institution – in addition to an operating account. Both relationships must be established and both will face separate compliance review. This profile should plan for the longest timeline and the most intensive documentation process.
A token issuer with treasury needs and no ongoing fiat-crypto conversion business presents the simplest profile. The business is not a VASP in the traditional sense; it holds fiat for treasury management rather than for customer flows. Banks generally apply lower AML intensity to this model, and the timeline from engagement to account opening is correspondingly shorter. The key risk is classification: if the token was issued in circumstances that attract securities or payment instrument characterisation, the risk profile changes materially.
Related at OBOLUS
- Banking, Payments & EMI Onboarding for Digital Asset Businesses – full-service guidance on fiat-rail architecture across the major EU and offshore hubs
- Client Funds Safeguarding in Ireland – safeguarding structures for EMIs and payment institutions under the Irish regulatory regime
- Licence Renewal and Variation in the United States: Federal and State MTL – managing ongoing licensing obligations across US money-transmitter regimes
FAQ
Why do banks close crypto company accounts?
Banks close crypto company accounts for several interconnected reasons. The most common are upstream correspondent pressure – where the bank's own clearing bank restricts crypto-related traffic – inadequate AML documentation, unexplained entity complexity, and a mismatch between the stated and actual business model. Enforcement action or regulatory enquiry in another jurisdiction touching the same group will also trigger a review. In most cases, the account closure is not arbitrary: it reflects a specific compliance signal that, once identified, can often be addressed through restructuring or enhanced documentation.
How can a VASP onboard with an EMI?
A VASP seeking to onboard with an EMI in Lithuania should approach the process as a structured compliance submission, not an account application. The EMI will require the VASP's registration documentation, a full AML/KYC policy suite, beneficial ownership disclosure, a business model description, expected transaction volumes and corridors, and evidence of transaction monitoring capability. EMIs that actively serve the crypto sector have established onboarding frameworks; matching the VASP's profile to the right EMI before submission reduces the timeline significantly. Allied counsel familiar with the relevant EMI market can materially accelerate this step.
What does client-money safeguarding require?
Client-money safeguarding under the applicable payment services regime requires that funds received from clients be held separately from the institution's own funds at all times. In practice, this means a ring-fenced account at a credit institution, a trust account in favour of clients, or an equivalent insurance or guarantee instrument. The safeguarding account must be clearly designated, the credit institution must acknowledge its role, and the institution must be able to demonstrate compliance on demand. The specific method permitted, and the documentation required, varies by licence category and regulator – an EMI and a payment institution face different operational obligations.
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 structures 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 – so that the entity structure, the regulatory regime and the banking architecture align from day one. To discuss your situation, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – specialising in VASP and CASP regulatory frameworks across the EU, with particular focus on the Bank of Lithuania's VASP and MiCA transition regime and the fiat-rail compliance structures that support licensed digital-asset operations.
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.