Joint analysis India · IT and SaaS exporters
Payoneer
Insights · Contracts and IP · Joint whitepaper

Who owns the code you build for a foreign client?

Under India’s Copyright Act, the developer who writes the code is presumptively its owner, while the foreign client who paid for it often assumes it bought everything. A contract that does not settle the question leaves your reusable code, and sometimes your core product, open to a claim.

An excerpt from Part II of The IT & SaaS Exporter’s Playbook, the whitepaper Infinilex wrote with Payoneer for Indian IT and SaaS exporters. Download the full whitepaper from Payoneer.

This is Part II of the whitepaper, on intellectual property, lightly edited for the web. The whitepaper was written in April 2026 and states the law as it stood then. The other parts cover the cross-border service agreement, business structures and GST zero-rating, getting paid globally and the FIRA trail, and DPDP compliance, with worked examples and FAQs. The full whitepaper is published by Payoneer: download it from Payoneer’s site. General information, not legal advice.

Without a Background IP carve-out and a section 19 compliant assignment clause, the reusable code you bring to a client project may end up belonging to the client.

The legal default

Under section 17 of the Copyright Act, 1957, the Indian developer who writes the code is presumptively its owner, but the foreign client who commissioned it frequently assumes it acquired all IP rights upon payment. Without a clause satisfying section 19 (written, signed by the assignor, specifying scope, duration and territorial extent), the position remains ambiguous.

An inadequate IP clause is not a technicality; it is a commercial risk. Without a Background IP carve-out, your pre-existing code libraries may belong to your client.

The four-part IP architecture

The four-part IP architecture for IT service agreements
CategoryWhat it coversPosition in the contract
Background IPPre-existing tools, frameworks, libraries and proprietary methodologiesShould not be transferred. The client receives only a limited, non-exclusive, revocable licence.
Foreground IPNewly created IP: software, code and work product produced during the engagementBespoke builds: assign to the client on payment. SaaS: the platform is typically licensed rather than assigned.
Customer data IPAll information uploaded, generated or processed through the platform by the clientTypically remains the client’s property. The provider receives only a restricted processing licence.
Feedback and derivativesFeature suggestions, enhancement ideas and customisations made during the serviceGeneral feedback: the provider’s IP. Bespoke features built exclusively for the client: negotiated.

What a valid assignment needs: section 19

An assignment of copyright under section 19 of the Copyright Act must be:

  • in writing;
  • signed by the assignor (the developer or the company);
  • specific about the scope of the rights transferred;
  • specific about the duration of the assignment; and
  • specific about the territorial extent of the rights.

The feedback clause: a common drafting failure

Prepare a clearly defined feedback clause that distinguishes general product feedback, which remains the provider’s IP, from bespoke custom features built exclusively for a client’s use, which are subject to negotiated IP terms.

Case study · The feature that became their product

A Bengaluru SaaS company provides a workflow automation platform. An enterprise client suggests a predictive routing algorithm over several planning calls. The SaaS team builds it. Two years later, the client claims the algorithm belongs to them under the contract clause: “all improvements developed during the service relationship are the property of the client.” The SaaS company’s core product differentiator is now subject to a contested IP ownership dispute that surfaces in the next funding round.

The SaaS licence clause: six elements

  • Reverse engineering ban: prohibit decompilation, disassembly or cloning.
  • Permitted user count: define seats, named users or concurrent sessions.
  • Geographic restrictions: state territory limitations or global permissions.
  • Sub-licensing rights: specify whether the client can grant access to its own clients.
  • Termination conditions: when the licence terminates and what happens to data.
  • Data portability on exit: the client’s right to export all data in a machine-readable format.

Frequently asked questions

We signed a contract saying “all IP created belongs to the client” and used our proprietary component library. Do they own it?

This will depend on whether your agreement contained a Background IP carve-out and the specific terms of the agreement. If it used broad language assigning “all IP created” without expressly preserving your pre-existing components, the legal position is genuinely contested: the client may have a colourable claim to your library as embedded in their deliverable. This is why clearly defined Background IP carve-outs are important in IT service agreements.

Copyright in software arises automatically on creation under the Copyright Act, 1957, and registration is not required. Voluntary registration with the Copyright Office under section 45 creates a public record and provides presumptive evidence of ownership, which can help in a dispute. For export contracts, a properly executed, section 19 compliant written assignment clause matters more than registration. Registration does not extend protection outside India; international protection comes from the Berne Convention, to which India is a party, so Indian-authored software is protected in Berne member countries without formal registration.

What else the full whitepaper covers

  • The cross-border service agreement: scope and deliverables, payment terms, liability caps and warranties, and governing law and dispute resolution.
  • Business structures: sole proprietor, LLP or private limited company, and when to incorporate.
  • GST on export of services: the conditions for zero-rating and the Letter of Undertaking.
  • Getting paid globally: collecting in foreign currency and the FIRA documentation trail.
  • DPDP compliance for IT and SaaS companies that process their clients’ data.
  • FAQs on enforcement, GST, reporting, penalties and foreign investment.
The full whitepaper

The IT & SaaS Exporter’s Playbook

All five parts, with worked examples and FAQs, published by Payoneer.

Further reading

FEMA compliance for export of services: eFIRC and Softex · DPDP compliance checklist for startups · Pvt Ltd vs LLP vs Delaware C-corp

Important notice

General information, not advice. Nothing on this page is legal, tax or financial advice. It summarises the law for general information and leaves out detail that may matter to your facts. Take advice on your own contracts before relying on it.

No client relationship. Reading or responding to this page does not create a client, advisory or fiduciary relationship with Infinilex or with Payoneer.

Source. Excerpted from The IT & SaaS Exporter’s Playbook, published by Payoneer on 29 October 2026 (© 2005-2026 Payoneer Inc). Infinilex contributed the legal and regulatory commentary, written in April 2026. Lightly edited for the web. The law is stated as at April 2026; it has moved since in some of the areas the full whitepaper covers, so check the current position before relying on it.

Independent firms. Infinilex and Payoneer are independent of each other. This collaboration does not create a partnership, joint venture or agency, and neither is responsible for the other’s services.

Payoneer × Infinilex The IT & SaaS Exporter’s Playbook, Part II (excerpt) · October 2026 www.payoneer.com · infinilex.io