Smart contracts in IP licensing can calculate and pay royalties automatically, but deploying code does not by itself create a valid grant of rights. A copyright licence must be in writing and follow the signature and content rules the Copyright Act applies to assignments, and a patent licence must be in writing with every term embodied. A licence executed electronically in a legally recognised way and linked to identified payment code is a practical structure: the code pays, and the licence grants.
This article covers the position in India as at October 2026, for in-house counsel and IP managers asking whether a blockchain payment layer can sit under a copyright or patent licence granted by or to an Indian business. Trade mark and design licences are outside its scope, as are token issuance, cryptoasset settlement and cross-border remittance.
Quick answer: Treat the smart contract as the payment layer and a signed written licence as the legal layer. The code should pay only what the licence says, with a way to suspend disputed amounts. Escalate before coding if the catalogue includes music or film works (society and statutory royalty rights) or the patent is co-owned (the other co-owners must consent unless an agreement allows otherwise). Keep personal data off-chain, and remember that tax law, not the licence or the code, decides what must be withheld.
What smart contracts in IP licensing can and cannot do
A smart contract is code on a blockchain that runs when set conditions are met. It can calculate royalties, split payments between rights holders and release milestone payments. On its own it does not establish a valid grant of rights, resolve vague terms or supply the writing, signature and content Indian law requires, so the terms should sit in a licence that meets those requirements.
Code suits arithmetic: applying an agreed rate to reported sales and dividing the result, as in “10 per cent of net sales, split 60:40 between two co-authors”. Judgments are different. Whether a use falls inside the licensed field or a sale counts as “net” are questions of interpretation, and code settles them only by hard-wiring one reading. Code is also only as accurate as its data: sales figures usually arrive through an outside feed (an oracle), and a wrong feed produces a wrong payment on time. On networks such as Ethereum, a user, another contract or an automation service must trigger execution, so name who supplies the data, initiates the transaction, funds the payout and pays network fees, and what happens if execution fails.
Automate what can be computed and keep a human decision point for what must be judged. Our piece on blockchain solutions for IP challenges covers the technology, and the NFT copyright piece covers tokens that carry a licence.
Is a smart contract enforceable in India?
Yes, if the ordinary conditions of a contract are met. No Indian statute checked for this article regulates smart contracts, so enforceability rests on ordinary law: free consent, competent parties, lawful consideration and object (Indian Contract Act 1872, ss. 2(h), 10, 23). A contract is not unenforceable only because it was formed electronically (Information Technology Act 2000, s. 10A), and an electronic record can satisfy a requirement of writing (s. 4) as can a reliable electronic signature affixed in the prescribed manner for a requirement of signature (ss. 3A and 5). Whether an arrangement meets those requirements turns on its terms and execution, not on the use of code, and a bare payment script will ordinarily lack the grant terms a licence needs. Do not assume a wallet-key signature qualifies.
Two drafting points follow. The licence should say that if prose and code differ, the prose prevails. And money paid by mistake must be repaid (s. 72), with breach losses compensated under s. 73; because a public-chain transfer is hard to reverse, the licence should carry its own repayment obligation.
Proof is separate. The Bharatiya Sakshya Adhiniyam 2023 treats electronic records as documents and does not refuse them only for being electronic (ss. 2(1)(d) and 61). A party relying on an electronic output under s. 63 must file the prescribed certificate, signed by a person in charge of the relevant device or the management of the relevant activities, with an expert’s part (s. 63(4) and the Schedule). Identify the node, service and extraction process, and preserve transaction identifiers, the code version and off-chain inputs. On a public chain no one controls the whole system, so an export from a named operator is more practical, and naming a signatory in the licence does not make that person competent to certify. An admissible record also does not prove ownership, authority or accurate sales data.
What an Indian copyright licence must still say
A copyright licence must be in writing, granted by the owner or a duly authorised agent, under the Copyright Act 1957 (s. 30). Section 30A applies the assignment rules of s. 19 to licences, with necessary adaptations, which brings in the signature requirement (s. 19(1)). The document must identify the work and state the rights granted, the duration, the territory, and the amount of royalty and any other consideration payable (s. 19(2) and (3)).
Where it is silent, defaults apply: five years, India as the territory, and lapse of rights not exercised within one year unless the document says otherwise. These fill gaps in duration and territory; they do not cure a missing signature or an unidentified work or grant. For works not yet created, the licence takes effect for each work only when it exists (s. 30). The parties may still agree advance or milestone payments, but the code should keep those separate from permissions that depend on the work existing.
Code can keep running after the legal term ends. The signed licence should fix five fields (work, rights, term, territory, royalty basis) and the code should take its rate, payee list and cut-off from the same figures. The end date and the final payment date need not match: define the reporting cut-off, any sell-off period, final reconciliation and the survival of payment and audit obligations. Our guide to licensing in India and the overview of types of IP contracts cover the surrounding commercial terms.
Royalty rights and copyright societies: where automation stops
Some royalty entitlements cannot be settled by a payment contract alone. The author of a literary or musical work included in a film or sound recording cannot assign or waive the statutory right to royalties for the uses the provisos cover, except to legal heirs or a copyright society (s. 18, provisos). Assigning the right to make a film leaves the author’s equal share of royalties for uses other than showing it in a cinema hall, and assigning the right to make a sound recording leaves that share for any utilisation (s. 19(9) and (10)). An assignment that conflicts with rights given to a society of which the author is a member is void (s. 19(8)).
The business of licensing works incorporated in films or sound recordings runs only through a registered society, although an owner may license its own works individually, consistently with any society obligations (s. 33(1)). For a music or film catalogue, the first design question is who may license and receive money at each step, not how fast the code can pay. An owner licensing its own rights can still be paid directly, but an intermediary that licenses other people’s works as a business should check s. 33 first. Our note on performers’ royalty rights explains one such stream.
Disputes: pausing payments the code cannot reverse
A blockchain does not automatically implement a court order, and a public-chain transfer is generally hard to reverse. The licence should say which amounts the code may hold back, redirect or return, who may trigger that, what happens to undisputed sums, and which forum or arbitration clause governs. Four design choices follow: suspend only the disputed amount on written notice, keep undisputed royalties flowing, hold the disputed sum in a designated bank or on-chain account (segregation does not by itself create a legally effective escrow), and record who holds the administrator key (the credential that can pause or change the contract), with a manual payment route for a system-wide pause. A court can direct a person but not code, so the arrangement needs an authorised person to give effect to an order.
For assignments, s. 19A(1) allows revocation if the assignee fails to exercise the rights sufficiently and the failure is not the assignor’s fault. Under s. 19A(2), revocation requires terms harsh to an assignor who is also the author, and is barred within five years. The forum is the Commercial Court, which replaced the Appellate Board under the Tribunals Reforms Act 2021, although some consolidations still show the old term. The Act applies s. 19 to licences but not s. 19A, so a licensor’s remedy lies in the licence terms and general contract law.
Fractional and shared patent licensing under the Patents Act
The Patents Act says nothing about tokens. Under the Patents Act 1970, co-owners hold equal undivided shares, and one cannot license without the others’ consent unless an agreement allows it (s. 50). Before licensing a co-owned patent, establish the required consents or the applicable contractual or statutory authority; a fractional-licensing model built on one co-owner’s tokens cannot rest on that co-owner alone. Token ownership by itself confers neither a patent share nor a licence, only whatever contractual royalty entitlement the signed agreement creates.
A patent licence is not valid unless it is in writing, in a document embodying all its terms and duly executed (s. 68). A person who becomes entitled by licence must apply to the Controller for registration (s. 69(1)), on Form 16 (Rule 90; Manual of Patent Office Practice and Procedure, para. 11.03). An unregistered document is not admitted as evidence of title or interest unless the Controller or court directs otherwise (s. 69(5)), though that does not make it invalid. On request the Controller keeps licence terms confidential except under a court order (s. 69(4)), which writing them to a public chain would defeat. Our guide to patent licensing lists what to check before signing.
A worked clause example: prose licence plus payment contract
The facts are illustrative: a photo agency licenses an archive to a publisher for India, for three years, at 10 per cent of net sales paid monthly through a payment rail named in the licence. None of the figures is a market rate.
| Term | Signed licence says | Smart contract does |
| Work and rights | Lists the photographs and the rights granted (for example reproduction, issue of copies and online communication) | Nothing; it holds no rights |
| Royalty basis | Defines “net sales” and the 10 per cent rate | Applies the rate to the monthly figure supplied |
| Term and territory | Three years from signature; India only | Applies the agreed cut-off and territory; still settles accrued royalties, final accounts and permitted post-term adjustments |
| Reporting | Monthly sales report; audit right | Accepts the figure only from the named reporting address |
| Tax | Allocates deduction, deposit, certificates and any gross-up | Pays the net amount; sends the deducted amount to a payer-controlled account |
| Prevailing text | Prose prevails over code | Nothing |
| Dispute | Written notice of a bona fide dispute and the amount affected; a named administrator holds the key | Suspends the disputed amount in a separate account; undisputed royalties continue |
Two clauses make the structure work:
Payment under this licence is made through the payment contract at the address in Schedule 2. If this licence and the code differ, this licence prevails.
Either party may give written notice identifying a bona fide payment dispute and the amount affected. The Administrator shall promptly suspend automated distribution of that amount and arrange its segregation in the account named in Schedule 2. Undisputed royalties remain payable when due. Disputed funds are released on joint written instructions or an order or award binding on the parties. This clause does not postpone tax obligations or override non-waivable royalty entitlements.
Without those mechanisms, automated transfers may continue while the legal dispute remains unresolved.
Personal data and tax on automated payouts
Personal data on a blockchain is hard to correct or erase. The European Data Protection Board’s Guidelines 02/2025 on blockchain, version 2.0 adopted on 7 July 2026 after consultation, recommend storing any additional personal data off-chain, beyond identifiers already in transaction metadata. They are European, but note that a public key can be personal data if it identifies a person by means reasonably likely to be used. Keep payee names and contact details off-chain and put on-chain only what the payout needs. See our note on IP and data privacy. In India, the Digital Personal Data Protection Act 2023 is being commenced in stages: notification G.S.R. 843(E) of 13 November 2025 brings the main obligations (ss. 3 to 17, with minor exceptions) into force eighteen months later, around May 2027, so a licence signed now will mostly run under them.
Section 393 of the Income-tax Act 2025, applicable since April 2026, governs tax deducted at source. This article states no rate. Applicable tax law determines withholding whether or not the licence mentions it. The licence should allocate responsibility for deduction, deposit, certificates and any gross-up, and the workflow should reflect the trigger that applies (for a resident payee, the earlier of credit and payment). Section 393(11) deems a credit to a suspense or other account in the payer’s books to be a credit to the payee, and moving funds into a payer-controlled account is not itself payment of tax. Residency, characterisation, relief, token payouts and GST need separate analysis.
How other jurisdictions treat smart contracts
These approaches bind no Indian court and do not change Indian formalities, but matter when a foreign counterparty expects its own rules. The Law Commission of England and Wales advised on 25 November 2021 that existing law can support smart legal contracts. Arizona provides that a contract is not invalid solely because it contains a smart contract term (Arizona Revised Statutes 44-7061). UNCITRAL adopted a Model Law on Automated Contracting in July 2024, which has no force until a state enacts it.
If the platform itself is the invention: CRI Guidelines 2025
The Patent Office’s Computer Related Inventions (CRI) Guidelines 2025 treat blockchain as an abstract idea unless it shows a concrete technical effect or an improvement in a technological process (s. 5.4). Automating royalty calculations or payment rules may amount in substance to an excluded business method under section 3(k), and using blockchain does not remove that exclusion. Its rental-agreement example points to integration of physical IoT devices and access enforcement without centralised servers as aspects that may take a claim out of the exclusion; that is an illustration, not a universal requirement. A claim to a technical improvement in the underlying system needs separate assessment, including the computer-programme-per-se issue and disclosure. Our review of blockchain patent trends shows where filings are concentrated.
Frequently Asked Questions
A payment script alone should not be treated as a sufficient copyright licence. The arrangement must satisfy ss. 30 and 30A, read with s. 19: a writing, a signature and the identified work, rights, duration, territory and royalty. The defaults for omitted duration and territory (five years, India) do not cure a missing signature or an unidentified grant.
A reliable electronic signature, affixed in the prescribed manner, satisfies a legal requirement of signature under the Information Technology Act. Do not assume a wallet signature meets that standard. The signature attaches to a record, so the licence terms must sit in a document a court can read.
It can pay, but it cannot override the statutory position. Licensing such works as a business runs through a registered copyright society, though an owner may license its own works individually (s. 33(1)). Check society membership and earlier grants before coding the payout waterfall.
Tokens can represent a contractual royalty entitlement under a signed agreement, but they create no share in the patent. A co-owner cannot license a co-owned patent without the others’ consent unless an agreement permits it, and every patent licence must be in writing and embody all its terms.
Money paid by mistake must be repaid (s. 72) and breach losses are compensated under s. 73. Because a public-chain transfer is hard to reverse, the licence should carry its own repayment and set-off clause, and the code should be able to suspend the disputed amount until the error is settled.
A person in charge of the relevant device or the management of the relevant activities, with an expert’s part (Bharatiya Sakshya Adhiniyam 2023, s. 63(4) and the Schedule). Naming a signatory in the licence does not make that person competent to certify the facts, so fix the role and a replacement in an operating protocol.
This article explains the position in India as at October 2026 and is for general information only. It is not legal advice. Laws, fees, and procedures change; verify the current position before you act. For advice on your specific matter, consult a qualified IP professional.