Opening a corporate bank account in Turkey for a digital-asset or cross-border payments business is achievable — but the path turns on entity structure, regulatory status and the nature of underlying transactions. Turkish banks operate under close supervision by the Banking Regulation and Supervision Agency (BDDK) and the Central Bank of the Republic of Turkey (TCMB), and both apply heightened scrutiny to businesses whose revenues derive from crypto-asset activity, foreign currency flows or digital payment services. A company that arrives at the account-opening interview without a clear compliance narrative, audited financials and a coherent ultimate-beneficial-owner (UBO) structure is unlikely to proceed past the correspondent-bank review stage.
The starting point matters. Turkey enacted a crypto-asset regime in 2024, bringing virtual-asset service providers under the supervision of the Capital Markets Board of Turkey (SPK), and mandating that crypto-asset exchanges and custodians serving Turkish users hold a domestic licence. For an inbound digital-asset business, that regulatory posture directly affects whether a Turkish bank will open and maintain a corporate account — and what documentation it will demand. This page sets out the regulated basis, the practical process, the cross-border interaction with banking and tax, and the decision point a business should reach before engaging a Turkish bank.
What is the regulated basis for corporate banking in Turkey?
Turkish corporate banking sits within a dual-supervision structure: BDDK sets prudential standards for banks, and TCMB governs payment systems and foreign-currency operations. Any business that touches crypto assets, stablecoins or cross-border payment flows must also engage the SPK licensing question before approaching a bank, because a bank's compliance function will ask it regardless.
Under the 2024 crypto-asset legislation, a business that trades, transfers, custodies or brokers digital assets for Turkish residents requires an SPK-issued licence. The legislation follows a model broadly consistent with the direction of the EU's MiCA (Markets in Crypto-Assets Regulation), in that it distinguishes between service categories — exchange, custody, transfer and brokerage — and imposes capital, fit-and-proper and AML/CFT obligations on each. Unlicensed activity serving the Turkish market is prohibited.
A foreign company with no Turkish clients can, in principle, establish a Turkish entity purely for treasury or operational purposes and seek banking on that basis. The analysis is different. Turkish banks will still require a clean corporate structure, a substantiated business-purpose letter and AML documentation, but the SPK licence question recedes if the entity genuinely has no Turkish user base. In our cross-border practice, the error we see most often is a company conflating those two profiles — believing a foreign-licensed entity can freely open a Turkish operational account without addressing the domestic-user question. It cannot, at least not without careful advance structuring.
Who needs an SPK licence before opening a bank account in Turkey?
Any legal entity providing crypto-asset services to Turkish residents — regardless of where the entity is incorporated — must hold or be in the process of obtaining an SPK crypto-asset service provider authorisation before a mainstream Turkish bank will onboard it as a business-banking client for its digital-asset operations. The SPK introduced the licence framework through amendments to the Capital Markets Law, with the transition period structured to allow existing market participants to regularise their status.
The licence categories map to activities rather than asset classes. An exchange needs separate authorisation from a custody-only business; a business offering both requires a broader authorisation covering both activities. That distinction matters for the bank-account conversation, because the bank's compliance team will compare the entity's declared activities against its licence scope. A mismatch — for example, a company licensed only for custody attempting to account for exchange-revenue inflows — will trigger an enhanced-due-diligence review that is difficult to resolve quickly.
Businesses that are purely technology vendors, software providers or infrastructure operators with no direct customer-facing digital-asset function occupy a different position. Turkish banks have historically been more straightforward with entities in that category, provided the underlying revenue does not derive from unlicensed VASP activity. Even so, the bank will require a detailed explanation of the business model, the customer type and the expected transaction volumes and corridors.
For a scoped assessment of your entity's position under the SPK regime and what documentation a Turkish bank will require, contact OBOLUS at info@oboluslaw.com. The process above describes the standard path. Your facts — the entity structure, the user base and the banking corridors — change the analysis materially.
How does the corporate account-opening process work in Turkey?
The Turkish corporate account-opening process follows a defined sequence, but the timeline varies considerably depending on the bank's internal risk appetite for digital-asset clients and the quality of the application file presented at the first meeting.
At the outset, the business must select a bank whose correspondent relationships and internal risk policy are compatible with its transaction profile. Turkey's large state-owned banks have generally applied conservative policies toward crypto-asset clients. Several private commercial banks and the Turkish branches of international banks have developed more structured onboarding procedures for regulated digital-asset businesses, particularly where an SPK licence or a foreign VASP authorisation is in place. Selecting the wrong bank at the beginning is the single most common cause of delay — the entity invests weeks in document preparation, only to receive a flat refusal at the compliance committee stage.
The document set a Turkish bank requires for a digital-asset or payments business will typically include: certificate of incorporation and articles of association; UBO declarations with passport copies and proof of address for all beneficial owners above a stated ownership threshold; an audited financial history or, for new entities, a business plan with projected financial statements; AML/KYC policy documentation; a compliance officer appointment letter; and, where applicable, the SPK licence or an official confirmation that an application is pending. Banks applying the TCMB's payment-systems rules may also require a description of settlement flows and the identity of correspondent institutions used for fiat settlement.
Once the document file is complete, the bank's compliance committee reviews the submission. In a straightforward case involving a licensed entity with clean UBO structure, the review can conclude within a matter of weeks. In complex cases — multiple-jurisdictional ownership chains, novel asset types, or high-risk corridor transactions — the process extends, and additional information requests are common. We advise clients to treat the first submission as a formal presentation and to anticipate at least one round of supplementary questions.
Following committee approval, account documentation is signed, initial capital is deposited and the account is activated. Ongoing transaction monitoring obligations then apply; Turkish banks file suspicious transaction reports under the Financial Crimes Investigation Board (MASAK) framework, which is Turkey's financial-intelligence unit operating under FATF Recommendation 15 obligations.
How does Turkish banking interact with cross-border licensing and tax?
A Turkish corporate bank account rarely sits in isolation. For most digital-asset businesses, it forms one part of a multi-jurisdictional banking stack that includes a primary licensed entity in a major regulatory hub, a payment institution or EMI for fiat-to-crypto settlement, and potentially one or more treasury entities. The interaction between those layers — and the way Turkish banking rules apply to inbound foreign-currency flows — requires advance planning.
Under TCMB regulations, certain categories of foreign-currency transaction by Turkish entities require specific reporting and, in some cases, prior notification. A digital-asset business receiving large inbound foreign-currency settlements from foreign exchanges or liquidity providers must ensure its transaction-documentation practices satisfy both the bank's AML requirements and the TCMB's capital-flow reporting framework. Failure to maintain that documentation does not merely create a regulatory risk; it creates the practical risk of transaction rejection or account suspension during a period of high commercial sensitivity.
On the tax side, Turkish corporate income tax applies to Turkish-resident entities on their worldwide income. A branch or subsidiary incorporated in Turkey is a Turkish tax resident. A foreign entity with a "permanent establishment" in Turkey — a concept that, in the digital-asset context, turns on where servers, personnel and customer contracts are located — may also be drawn into the Turkish tax base. The interaction between Turkish transfer-pricing rules and intra-group treasury flows deserves early attention, particularly where the Turkish entity's primary function is to hold fiat balances on behalf of a foreign parent.
In our cross-border practice, we structure the Turkish banking engagement as one element of a wider mandate that addresses the licence, the banking and the tax layer together. A business that resolves the banking question in isolation, without confirming the tax residency analysis or the transfer-pricing policy, often finds that the account it spent months opening creates an unintended Turkish tax exposure.
Can a digital-asset business use an EMI instead of a Turkish bank?
An EMI (electronic money institution) licensed in the EU or the UK can provide fiat-rails access to a Turkish digital-asset business without the business needing a Turkish corporate bank account for every operational purpose. That model is widely used, and it addresses some of the practical friction that arises from Turkish banks' conservative onboarding posture toward crypto clients.
The limitation is settlement. A Turkish entity still requires a Turkish bank account to receive Turkish lira from domestic clients, to pay Turkish-resident staff and suppliers, and to comply with certain TCMB foreign-exchange obligations. An EMI account in a foreign currency — typically EUR or GBP — does not substitute for that domestic functionality. The practical architecture that operators in this space use most often combines a Turkish corporate bank account for local lira operations with an EU- or UK-licensed EMI for cross-border euro settlement.
In a recent matter, a payments business seeking to serve the Turkish market had already obtained an EMI passported under MiCA but had not resolved its Turkish lira settlement question. The entity's Turkish corporate bank applications were stalled at the compliance-committee stage because its AML documentation did not separately address the Turkish regulatory perimeter. We restructured the onboarding narrative, aligned the Turkish AML policy with MASAK's expectations and separated the lira-settlement function into a dedicated Turkish subsidiary. The bank account opened within weeks of the revised submission. No specific timeline is guaranteed, and individual facts will always determine the outcome.
If a prior application stalled or an account was closed, a second read of the file can surface the structural reason and the route back. Write to OBOLUS at info@oboluslaw.com for a scoped file review.
What mistakes cause corporate bank account applications to fail in Turkey?
Most Turkish corporate account failures for digital-asset businesses trace to a small set of avoidable errors, and all of them share the same root: the application was prepared as though Turkey were a standard commercial banking engagement rather than a regulated-activity onboarding with a compliance-committee decision-maker at its centre.
The first and most frequent mistake is mismatched entity purpose. A company incorporated for holding or treasury purposes presents a very different risk profile from an operating exchange. Presenting an entity with a broad objects clause and then describing exchange-like transaction flows creates immediate compliance concern, even where the described activity is permissible. The business description and the entity's constitutional documents must be internally consistent and consistent with the SPK analysis.
The second mistake is incomplete UBO disclosure. Turkish banks apply MASAK's beneficial-ownership requirements, and those requirements extend beyond the first legal layer. A fund with multiple-class shares held by a Cayman SPV held by a BVI company held by a foundation in a privacy jurisdiction will require a clear walk-through of each layer, with contemporaneous corporate documents for each. Partial disclosure does not fail quietly; it triggers escalation to the bank's financial-crime team, which effectively resets the process.
The third mistake is the absence of a Turkish-language compliance narrative. The compliance committee reviewing the application is based in Ankara or Istanbul, not in London or Dubai. Providing English-language AML policies without a Turkish executive summary, and without a Turkish-licensed compliance adviser identified on the file, signals that the applicant has not invested in the engagement. Turkish banks respond to that signal as a risk indicator.
A common assumption among inbound businesses is that a single offshore licence — a BVI FSC registration or a Cayman VASP Act filing, for example — is sufficient to satisfy a Turkish bank's regulatory-status requirement. It is not. Turkish banks are looking for evidence of substantive regulatory oversight, ideally by a recognised regulator, or for the SPK licence itself. An offshore registration without substantive supervisory engagement behind it will rarely be accepted as a satisfactory risk-mitigation measure.
Which entity profile should consider a Turkish bank account?
The decision to pursue a Turkish corporate bank account follows from the entity's commercial purpose in Turkey. Three profiles appear most often in the businesses we advise.
A digital-asset exchange or crypto-asset service provider with Turkish retail users requires an SPK licence and a Turkish lira settlement account. That business has no meaningful choice about the Turkish banking question — it is a regulatory and operational necessity. The relevant decision is which bank to approach, in what sequence, and with what documentation strategy. The timeline for a licensed entity with a clean structure is typically a matter of weeks from complete submission; for a business navigating the SPK licensing process concurrently, the banking timeline extends to reflect the licensing process.
A payments or EMI business with Turkish corporate clients — not Turkish retail users — may be able to operate for a period through a foreign EMI account while the Turkish corporate banking application progresses. That intermediate structure works for euro-denominated business-to-business flows, but it exposes the entity to TCMB reporting requirements for foreign-currency flows into Turkey and requires careful documentation of each inbound payment.
A holding or treasury entity with no Turkish user-facing activity faces a lighter regulatory burden on the SPK side but must still present a clean, well-documented corporate structure to the bank. The risk for this profile is an assumption that the reduced regulatory friction means the banking engagement is simple. Turkish banks apply the same AML scrutiny regardless of the entity's user base.
Related at OBOLUS
- Banking, Payments & EMI Onboarding – end-to-end banking stack and EMI onboarding for digital-asset businesses across major hubs.
- Payment institution licensing in Georgia – an alternative or complementary licensing route for fiat-rails access in the CIS region.
- Staking and rewards taxation for early-stage founders – tax analysis for founders structuring token income across multiple jurisdictions including Turkey.
FAQ
Why do banks close crypto company accounts?
Banks close crypto company accounts when transaction flows cannot be matched against documented business activity, when UBO disclosure is incomplete, or when the business lacks a licence that the bank's compliance policy treats as a minimum requirement. In Turkey, MASAK-driven AML obligations heighten this risk: a single unresolved suspicious-transaction flag can trigger account suspension pending enhanced review. The most effective mitigation is a well-prepared onboarding file that pre-empts the compliance questions before the account is opened, not after.
How can a VASP onboard with an EMI?
A VASP (virtual asset service provider) seeking to onboard with an EMI must typically demonstrate regulatory status in its home jurisdiction, a documented AML/KYC programme aligned with FATF standards, and a clear description of its fiat-settlement flows. EMIs licensed under MiCA or the UK's FCA regime apply their own risk-based onboarding criteria; a VASP holding an SPK licence or a comparable recognised authorisation is materially better placed than an unlicensed entity. The process involves document review, compliance calls and, in most cases, an ongoing transaction-monitoring agreement.
What does client-money safeguarding require?
Client-money safeguarding requires a licensed entity to hold client funds in accounts that are legally and operationally segregated from the firm's own capital. Under most regulated regimes — including payment institution rules aligned with EU standards and the SPK's crypto-asset framework — segregated accounts must be held at an authorised credit institution, clearly designated as client-money pools, and reconciled against individual client balances at defined intervals. A Turkish bank account used for client-money purposes must carry the appropriate designation and must be documented in the entity's regulatory permissions and internal policies.
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 structure licensing, banking and tax as one mandate rather than three disconnected workstreams. To discuss your situation, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst — specialises in VASP licensing, corporate banking onboarding and regulatory compliance for digital-asset businesses operating across multiple jurisdictions including Turkey and the EU.
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.