Turkish Software Developer Refuses to Deliver Source Code: Legal Remedies for Foreign Companies (2026 Updated Guide)

A Turkish software developer refuses to deliver source code to a foreign company. Learn how contracts, copyright ownership, access credentials, injunctions, evidence preservation, termination and compensation claims may affect recovery of the software.

A foreign company that hires a Turkish software developer, technology company or independent programmer may face a serious business crisis when the developer refuses to deliver the source code after receiving payment. The foreign client may possess a functioning application, website or SaaS platform but remain completely dependent on the developer for updates, security patches, hosting, database access and future development. The legal solution depends heavily on the contract, intellectual property provisions, payment history, project specifications and the precise software assets being withheld. A foreign company facing this problem should immediately preserve evidence, secure all existing system access and determine whether it can demand source-code delivery, transfer of credentials, performance of contractual obligations, termination, compensation or urgent judicial protection.

Why Does a Software Developer Refuse to Deliver Source Code?

Disputes frequently arise because the developer claims that invoices remain unpaid, the parties disagree about project scope, additional development was requested without additional payment, intellectual property provisions are unclear or the developer believes that the client purchased only a right to use the finished software rather than ownership of the underlying code.

The first legal question is therefore not simply who paid for the project. The entire contractual relationship must be examined.

Does Paying for Software Automatically Give the Foreign Company Ownership of the Source Code?

Not necessarily. Payment for software development and ownership of intellectual property rights should not automatically be treated as identical.

The contract should be reviewed to determine what rights were transferred, when the transfer was intended to occur, whether delivery of source code was expressly required and whether any conditions were attached to the transfer.

Review the Software Development Agreement First

The agreement may determine most of the dispute. Important provisions can include project scope, deliverables, milestones, acceptance procedures, payment obligations, source-code delivery, intellectual property rights, licensing, confidentiality, termination, warranties, maintenance, hosting and dispute resolution.

A foreign company should compare each contractual obligation with what was actually delivered.

Source Code and Intellectual Property Ownership Are Different Issues

A company may have contractual rights to receive a copy of source code without necessarily owning every intellectual property right in every component. Conversely, the parties may have agreed on a transfer of certain economic rights while still disputing whether all technical materials were delivered.

These issues should be separated carefully.

Identify Exactly What Is Being Withheld

“Source code” can mean different things to different parties. The foreign company should identify whether it is missing the main application repository, backend code, frontend code, mobile application code, database schema, infrastructure scripts, deployment files, API documentation, encryption keys, build instructions or other technical assets.

The legal demand should describe the missing materials precisely.

Repository Access Can Be Critical

Modern software projects are often maintained through source-code repositories. Determine who controls the organization and administrator account and whether the foreign company has a complete copy of the repository.

Preserve the current repository state before access can be removed.

Preserve Commit History

Commit history may show who developed particular components, when work was performed and whether the developer continued making changes after contractual disputes arose.

It can also become relevant when determining whether the code delivered is complete.

Secure Hosting and Cloud Accounts

Source-code disputes can escalate into operational emergencies if the developer also controls hosting infrastructure.

The foreign company should identify every cloud, server, domain, database, email, analytics, payment and deployment account associated with the project and determine who has administrative control.

Change Credentials Where Legally and Technically Appropriate

If the company already owns or controls relevant accounts, security should be reviewed immediately. Former developers should not retain unnecessary administrative privileges after a serious dispute develops.

However, companies should avoid unauthorized access to accounts that legally belong to another party.

Preserve Communications

Emails, messaging records, project-management systems and meeting notes may establish what the developer promised.

Particularly important communications may concern source-code ownership, delivery dates, repository access, project completion, payment and acceptance.

Preserve Payment Evidence

Collect invoices, bank transfers, payment confirmations and accounting records.

If the foreign company has paid the full contract price, this may be important when responding to an allegation that source code is being withheld because payment remains outstanding.

What If Some Invoices Are Unpaid?

The company should determine whether the developer has a legitimate contractual payment claim and whether the disputed payment legally affects the obligation to deliver source code.

A company should not assume that every payment dispute automatically permits indefinite withholding of all software assets.

Review Project Acceptance

Some contracts provide that final source-code delivery occurs only after acceptance or final payment.

Determine whether acceptance occurred formally, implicitly through commercial use or not at all.

Scope-Creep Disputes Are Common

A developer may claim that the original project expanded significantly and that additional compensation is due.

Separate the original contractual deliverables from genuinely additional work. Source code already developed and paid for under the original scope should not be confused with later disputed features.

Intellectual Property Clauses Require Careful Analysis

Software can contain copyright-protected elements. The contract should identify which economic rights were transferred or licensed and the scope of any transfer.

Broad wording such as “all software belongs to the customer” may still require careful legal interpretation when a dispute arises.

Pre-Existing Developer Code May Be Different

A developer may have used libraries, frameworks, templates or proprietary components created before the project.

The client should distinguish project-specific code from legitimate pre-existing technology.

Open-Source Components Must Be Identified

Modern applications frequently incorporate open-source software. The developer cannot simply transfer exclusive ownership of third-party open-source components as though they were created entirely for the client.

The company should obtain an inventory of major dependencies and applicable licenses.

Third-Party Licensed Components Can Affect Delivery

Some projects contain commercial libraries, APIs or software licensed from third parties.

The foreign company should determine whether those licenses can be transferred or whether separate subscriptions are required.

Can the Foreign Company Demand Specific Performance?

Depending on the contract and circumstances, the company may seek performance of contractual obligations, including delivery of agreed software materials.

The exact claim should be structured according to the agreement, nature of the obligation and applicable Turkish law.

A Formal Notice May Be the First Step

Before litigation, a carefully drafted formal notice can identify the breached obligations, specify the missing deliverables and provide an appropriate period for performance where legally relevant.

The notice should avoid vague demands such as “send everything.”

Create a Detailed Delivery List

The notice can identify the expected repository, source files, database documentation, deployment configuration, credentials, technical documentation and other agreed deliverables.

This reduces later disagreement about whether the developer complied.

Can the Contract Be Terminated?

Potentially. Serious non-performance may create termination rights depending on the contractual structure and applicable law.

Termination should not be exercised mechanically. The company should first analyze the consequences for intellectual property, access rights, payments, unfinished work and damages.

Can the Foreign Company Claim a Refund?

Potentially, depending on the nature of the breach, performance already received, termination mechanism and contractual provisions.

A full refund should not be assumed merely because a source-code dispute exists.

Can Compensation Be Claimed?

Where breach causes measurable loss, compensation may potentially be pursued under the applicable contractual framework.

Possible losses can include replacement-development costs, migration expenses and other direct losses causally connected with the breach.

Lost Profits Require Strong Evidence

A foreign company may claim that inability to obtain the source code delayed a product launch or caused customer losses. Such claims require careful proof of causation and amount.

Forecasts alone may not establish the entire claimed loss.

Replacement Development Costs Should Be Documented

If another development company must reconstruct or migrate the system, obtain detailed quotations and invoices.

These records can help demonstrate the financial consequences of the original developer’s non-performance.

Emergency Judicial Protection May Be Necessary

Urgent legal measures may need to be considered if there is a concrete risk that repositories, databases, servers or other critical evidence will be deleted, transferred or rendered inaccessible.

The availability and form of interim protection depend on the specific circumstances and requested measure.

Evidence Preservation Can Be More Important Than Immediate Damages

Software environments change quickly. Repositories can be deleted, access logs overwritten and cloud services terminated.

Preserving evidence before filing a large compensation claim may therefore be strategically important.

Technical Expert Examination May Be Required

A software expert can determine whether delivered files constitute complete source code, whether the application can be compiled or deployed independently and which technical components remain under the developer’s control.

This can convert a vague commercial disagreement into a clearly defined technical dispute.

Is a ZIP File Enough?

Not necessarily. A folder containing code may be useless if critical dependencies, database structures, environment configurations, deployment instructions or credentials are missing.

The contractual definition of delivery and technical completeness should be examined.

The Code Should Be Capable of Independent Continuation

From a commercial perspective, the foreign company should seek enough technical material to allow another competent developer to maintain and deploy the system without unreasonable dependence on the original developer.

Whether the contract legally requires this depends on its terms and project structure.

Database Access May Be More Urgent Than Source Code

For a live platform, customer and operational data may be commercially more urgent than the code itself.

Determine who controls the production database and whether backups exist.

Personal Data Obligations Must Be Considered

If the application processes personal data, a developer’s continued access to production systems can create separate data-protection concerns.

The foreign company should review access permissions and contractual data-processing arrangements promptly.

Cybersecurity Risks Should Be Assessed

A hostile breakdown in the developer relationship can create operational security risks.

Audit administrator accounts, API keys, deployment tokens and other privileged credentials under the company’s control.

Domain Names Should Be Checked

Sometimes a developer registers the customer’s domain in the developer’s own name or account.

The foreign company should identify the registrant and administrative control before the commercial dispute escalates.

App Store Accounts Can Become Critical

For mobile applications, determine who controls developer accounts, signing certificates and publishing rights.

Possessing source code alone may not be enough to update an application already distributed to users.

Payment Gateway and API Accounts Should Be Reviewed

The company should identify whether payment processors, messaging services, mapping services or other APIs were registered in the developer’s name.

A transition plan may be required.

Can the Developer Shut Down the Software?

The answer depends on the contract, ownership of infrastructure and circumstances. A developer should not simply be assumed to have an unrestricted right to disable a customer’s business system because a commercial dispute exists.

If shutdown is threatened, urgent legal and technical measures should be considered.

Do Not Retaliate Through Unauthorized Access

Foreign companies should avoid attempting to break into developer-controlled systems or obtain passwords through unauthorized means.

A contractual dispute should not be transformed into a cybersecurity or criminal dispute.

Check the Governing Law Clause

International software agreements frequently contain governing-law provisions.

Determine whether Turkish law applies to the contractual relationship or whether another law was selected.

Check the Jurisdiction Clause

The contract may designate Turkish courts, foreign courts or another dispute-resolution forum.

The clause should be analyzed before proceedings are commenced.

Arbitration Clauses Can Change the Strategy

If the agreement contains a valid arbitration clause, the substantive dispute may need to be resolved through arbitration rather than ordinary court litigation.

Urgent interim measures should be considered separately under the applicable framework.

Foreign Companies Should Review Service of Process

International disputes can be delayed by incorrect notices or procedural mistakes.

Corporate names, registered addresses and contractual notice mechanisms should be verified before formal action.

What If There Is No Written Contract?

The absence of a comprehensive signed agreement does not necessarily mean that no contractual relationship exists.

Invoices, payments, emails, proposals, messages, project records and actual performance may help establish the terms of the relationship.

WhatsApp and Email Evidence May Become Important

Communications can show that the developer agreed to transfer source code or provide repository access after payment.

Preserve original records rather than relying only on isolated screenshots.

Avoid Editing Digital Evidence

Keep original emails, message exports, project records and electronic files where possible.

Authenticity can become important if the developer later disputes the communications.

What If the Developer Claims Ownership?

The foreign company should demand that the developer identify the contractual and legal basis for that claim.

The dispute should then be separated into ownership, licensing, possession of technical materials and contractual delivery obligations.

What If an Employee Created the Software?

Different legal questions can arise where the developer was an employee rather than an independent contractor.

Employment status, job duties and applicable intellectual property rules should be examined separately.

What If a Turkish Software Company Subcontracted the Work?

The foreign client may have contracted with one company while the actual programmers were subcontractors.

The primary contractor’s obligations should be examined alongside any intellectual property or access issues created by subcontracting.

Foreign Companies Should Avoid Directly Paying Subcontractors Without Review

Attempting to bypass the primary contractor can create new contractual problems.

First determine who legally owns or controls the relevant deliverables and what rights the client possesses.

Source-Code Escrow Can Prevent Future Disputes

For business-critical software, future contracts can require periodic source-code deposits with an agreed escrow mechanism.

Release events can include insolvency, permanent cessation of support or specified contractual breaches.

Repository Ownership Should Be Agreed From Day One

A safer structure is often to establish the repository under an account controlled by the customer while granting the developer appropriate access.

This reduces dependency if the relationship ends.

Foreign Companies Should Require Technical Handover Clauses

Future agreements should specify exactly what must be delivered upon completion or termination: repositories, documentation, credentials, database schemas, deployment scripts, API information and transition assistance.

Avoid Vendor Lock-In

A company should not discover after several years that only one developer can deploy its application.

Regular backups, documentation and customer-controlled accounts substantially reduce this risk.

Immediate Legal Action Plan

When a Turkish software developer refuses to deliver source code, the foreign company should immediately preserve the contract and communications, secure company-controlled infrastructure, obtain repository backups, identify missing technical assets, document payments, review intellectual property provisions, determine whether any invoices remain legitimately disputed, send a structured formal demand where appropriate, obtain technical expert assistance, evaluate interim protection if evidence or systems are at risk and prepare contractual claims for performance, termination or compensation as supported by the circumstances.

Frequently Asked Questions

Does paying a Turkish developer automatically make the foreign company owner of the source code?

Not necessarily. Payment, contractual delivery obligations and intellectual property ownership are related but legally distinct questions.

Can a foreign company force the developer to hand over source code?

Potentially, where delivery is a contractual obligation. The appropriate remedy depends on the agreement and circumstances.

What if the contract expressly requires source-code delivery?

That provision can provide a strong contractual basis for demanding performance, subject to any conditions contained in the agreement.

Can the developer withhold code because one invoice is unpaid?

The legal position depends on the contract, nature of the payment dispute and relationship between the outstanding obligation and delivery requirements. An automatic right to withhold everything should not be assumed.

Can the foreign company terminate the contract?

Potentially, where the requirements for termination are satisfied. The consequences should be analyzed before termination notice is issued.

Can damages be claimed?

Potentially. Replacement development expenses and other provable losses causally connected with the breach may become relevant.

What if the developer threatens to delete the repository?

Evidence preservation and urgent judicial protection should be evaluated immediately where there is a credible risk of deletion.

Is receiving source-code files alone sufficient?

Not always. Databases, deployment configurations, credentials, documentation and other technical materials may also be required to operate and maintain the system.

What if there is no signed contract?

Emails, proposals, invoices, payments, messages and performance records may still be relevant in establishing the contractual relationship and agreed obligations.

What should the foreign company do first?

Secure all systems and evidence already under its lawful control, identify exactly what technical assets are missing and compare those missing assets with the developer’s contractual obligations before taking legal action.

Client-Focused Legal Support for Software and Technology Disputes

Disputes with Turkish software developers can involve source-code delivery, intellectual property rights, unpaid invoices, repository access, cloud infrastructure, database control, cybersecurity, contract termination, interim measures and compensation claims. Fırat Fesih Kaya Law Office assists foreign companies, international investors, technology businesses and overseas clients in contractual and commercial disputes with Turkish software developers and technology providers. Lawyer Fırat Fesih Kaya provides legal assistance in reviewing software-development agreements, preserving contractual and digital evidence, preparing formal demands, evaluating urgent judicial remedies and pursuing performance, termination and compensation claims where legally available.

Phone:
+90 312 434 22 22

Mobile / WhatsApp:
+90 532 769 22 22

Email:
info@firatfesihkaya.av.tr

Address:
Mevlana Boulevard No:221, Yıldırım Tower, Office No:148
06520 Balgat, Çankaya, Ankara, Turkey