All guides
GuideNFTIntellectual PropertyWeb3

NFT resale royalties and enforceable holder licences

Making NFT resale royalties collectable: who owes the payment, how holders accept the licence, what code can enforce and which remedies work.

16 min read

NFT royalties need an identified payer, agreed terms and a collection route. ERC-2981 supplies royalty information; payment depends on the transaction mechanism. A later holder’s obligation requires its own legal basis. For an English-law collection, the recommended design combines recorded holder acceptance, tested settlement routes and a fresh artwork licence that separates earlier sellers’ debts. (ERC-2981, Specification and Rationale; RTS Flexible Systems Ltd v Molkerei Alois Müller GmbH [2010] UKSC 14, [45].)

An England-based studio wants continuing revenue while holders remain able to transfer their tokens. The design turns on who owes each payment, what the buyer accepts and which transactions the software actually controls.

The route developed here uses the law of England and Wales for the holder agreement and Ethereum ERC-721 tokens. France supplies the EU national-law comparison; California and Ninth Circuit authority supply the US contract comparison. Territorial copyright rules and mandatory consumer protections require separate attention when the studio targets those markets.

  • Define the resale royalty as a payment obligation with a named creditor, debtor, trigger and calculation. Token ownership alone does not establish acceptance of that obligation. English law can also bind a third party who enforces a contractual right to the terms of the contract relevant to exercising that right. (RTS Flexible Systems, [45]; Kingdom of Spain v London Steam-Ship Owners’ Mutual Insurance Association Ltd (No 2) [2026] UKSC 36, [7]–[9], [47]–[51].)
  • Obtain clear acceptance of the holder terms before granting the relevant licence. Preserve the wording, interface and acceptance record. Online incorporation depends on notice and assent, with particular attention to unusual burdens. (Parker-Grennan v Camelot UK Lotteries Ltd [2024] EWCA Civ 185, [31], [46]–[51]; Berman v Freedom Financial Network, LLC, 30 F.4th 849, 856–858 (9th Cir. 2022).)
  • Test each supported sale and transfer route. A royalty query, a marketplace setting and a transfer validator perform different functions. Wrapping or custody may allow economic transfers without moving the original token. (ERC-721, Specification; ERC-2981, Specification; OpenSea, Creator fee enforcement; OpenZeppelin Contracts 5.x, ERC721Wrapper.)
  • Keep the contractual royalty separate from copyright ownership and statutory artists’ resale rights. French rules expressly include certain original digital artworks. Their application still depends on the work and sale. (Copyright, Designs and Patents Act 1988, s. 90; 17 U.S.C. §§ 202, 204; French Intellectual Property Code, arts. L122-8, R122-2–R122-5.)
  • Pursue the person who owes the payment. Make suspension and termination precise, preserve a complying later holder’s independent grant, and review sanctions for fairness. Copyright remedies require an infringement, not merely an unpaid invoice. (CDPA 1988, ss. 16, 96–97; Consumer Rights Act 2015, s. 62; MDY Industries, LLC v Blizzard Entertainment, Inc., 629 F.3d 928, 939–941 & n. 4 (9th Cir. 2010), amended 17 February 2011.)

Define the payment before choosing the collection mechanism

The studio’s legal and finance teams should approve a royalty schedule before engineering configures the collection. The recommended payer is the seller who accepted the holder agreement. Name the studio or other entitled recipient as creditor. If a marketplace deducts the amount from sale proceeds, explain when that payment discharges the seller’s liability.

The schedule should specify:

  • The covered disposition, including any agreed sale of a wrapped token or custodial entitlement.
  • The rate and calculation base, with express treatment of taxes, marketplace charges, refunds and bundled consideration.
  • The valuation method for barter, non-cash consideration and payments in another currency.
  • The recipient, payment deadline, reporting obligation and method for resolving a disputed calculation.
  • Exclusions for gifts and transfers between wallets with unchanged beneficial ownership, together with the evidence needed to claim them.

These are proposed commercial terms. They become obligations through an effective agreement; a percentage in token metadata does not supply that agreement. A royalty on gross proceeds also differs from a share of profit. Finance should be able to reproduce the amount from the agreed formula and the actual transaction records. (RTS Flexible Systems, [45]; ERC-2981, Specification.)

Credit verified marketplace payments against the same contractual liability to prevent duplicate collection. State who must pay a shortfall and how overpayments are returned. Keep statutory artists’ resale royalties in a separate ledger. Their creditor, calculation and collection rules can differ from the studio’s negotiated fee.

The contract should identify a real counterparty and a usable notice address. A wallet address helps connect evidence to a transaction, but it does not establish the signer’s legal identity or authority to bind a business. Product and legal teams should decide what identity and authority evidence the proposed licence requires before opening that flow.

Obtain each holder’s agreement at the point it matters

The first buyer’s promise does not automatically become every later buyer’s debt. English law generally confines contractual burdens to the parties. Assignment transfers rights, while obligations and liabilities cannot simply be assigned. The Supreme Court’s judgment of 28 October 2026 confirms a qualification: a third party claiming a contractual benefit can become subject to related burdens. It distinguishes that position from a condition that must be satisfied before a benefit arises. (Kingdom of Spain, [47]–[51], [60]–[65].)

That decision concerns insurance and arbitration. It supplies no rule making every NFT recipient liable for mint terms. The issuer must identify the contractual right asserted, the related condition and the person claiming it. Express acceptance remains the recommended route for a resale payment promise.

Use a direct licence from the studio to each eligible holder. The buyer accepts the identified version in exchange for the permissions granted. The outgoing holder’s future permission ends or narrows as the agreed transfer provision specifies. Accrued debts remain with the person who incurred them. This design depends on the studio having authority to grant each successive licence.

Before acceptance, show the royalty trigger and rate, transfer restrictions, termination grounds and governing-law provision beside a readable link to the complete terms. Require an affirmative action expressly tied to those terms. Preserve the screen, terms version, timestamp, wallet and acceptance message. A wallet request should describe the legal action being authorised, rather than present an unexplained signature.

English appellate guidance supports assessing whether the trader gave sufficient notice, including additional prominence for unusual burdens. US online assent needs its own review: Berman requires reasonably conspicuous notice and an unambiguous manifestation of assent where actual knowledge is absent. A generic continuation button can fail that test. (Parker-Grennan, [31], [46]–[51]; Berman, 856–858.)

For a sale outside the studio’s interface, require the accepting seller to direct the purchaser to the accession process before sale. The studio should offer an accessible route for later holders to obtain their own licence. Acceptance after acquisition creates the agreement on its actual terms; it does not prove acceptance at the earlier sale or repair missing pre-sale disclosures.

If the purchaser receives the token without accepting, distinguish token possession from permission to use the artwork. The issuer may have no contractual royalty claim against that purchaser. Any copyright claim depends on a restricted act without permission and the applicable exceptions. An existing licence or valid third-party entitlement must also be respected. (CDPA 1988, s. 16; Kingdom of Spain, [7]–[9].)

A marketplace can collect acceptance for the studio only through an arrangement that actually does so. Where the creator relies on a promise between seller and buyer, English third-party rights require the statutory conditions to be met. Identify the beneficiary and check any exclusion of those rights. Platform membership terms alone do not establish this arrangement. (Contracts (Rights of Third Parties) Act 1999, s. 1; OpenSea Platform Terms, 20 October 2026, s. 5.2.)

Test what each transaction route can collect

Engineering should produce a route record identifying the chain, collection address, deployed version, administrator powers and permitted marketplaces. For every route, record whether the transaction pays the royalty, is blocked, or completes without collection. Legal and product teams can then describe the supported behaviour accurately.

ERC-2981 provides a query for the recipient and royalty amount against a supplied sale price. It neither transfers the funds nor makes every token transfer conditional on payment. Its participation model does not cancel a separate contractual payment promise. (ERC-2981, Abstract, Specification and Rationale.)

A marketplace settlement contract can distribute proceeds when the sale passes through its supported process. The evidence should show the order price, royalty recipient and amount actually credited. It must also identify private listings, accepted offers and any routes that use different settlement rules.

OpenSea documents enforcement for compatible ERC721-C and ERC1155-C collections using Seaport and configured transfer validation. The relevant token, validator, authorisation and order settings must work together. Its current Platform Terms separately place communication and enforcement of NFT terms on the participants. Technical support therefore needs to be checked alongside the actual contractual commitments. (OpenSea, Creator fee enforcement; Platform Terms, 20 October 2026, ss. 3.9, 5.2.)

A transfer validator can reject a transfer that fails its rules. That control can restrict permitted venues, smart wallets or recipient contracts. It does not establish the true economic price where parties place additional consideration elsewhere. An ordinary ERC-721 transfer carries no standard sale-price field. The same event can accompany a gift, a self-transfer or a separately paid sale. (ERC-721, Specification; OpenSea, Creator fee enforcement.)

Wrappers require a separate decision. A wrapper may hold the original token while buyers trade a different token representing it. In that arrangement, wrapper resales need not trigger the original token’s transfer checks. A restrictive collection may instead block the deposit, and some wrappers add royalty controls. The result depends on the permitted code paths. (OpenZeppelin Contracts 5.x, ERC721Wrapper; Limit Break, Creator Token Standards, Wrapper Standards.)

Apply the same analysis to bridges and custody. Identify what moves, what the holder can redeem and which contract sees each sale. The licence must specify whether a wrapped or custodial holder qualifies for permissions. A promise covering indirect sales still requires an identifiable bound person and evidence of the agreed trigger.

Before claiming enforcement, test supported sales, direct transfers, every transfer function, approved operators and relevant smart-wallet routes. Test wrapper deposits, wrapper resales, withdrawals and any bridge or custody flow the studio permits. Check bypasses, failed payments, refunds and changes to administrators or validators. A standard name or a successful mint cannot replace those results.

If unrestricted transfers remain a product requirement, the business must accept that some royalties will depend on reporting and legal recovery. If collection requires restricted transfer paths, disclose the restriction before purchase. The release decision belongs to the studio after legal, finance and engineering have reconciled their records.

Separate transfer rights from remedies for non-payment

The agreement should specify when the incoming licence starts and when the outgoing holder’s permission ends. Address existing merchandise, sublicences and uses already authorised. Reserve any agreed wind-down rights expressly. A token transfer should produce the rights transition described to buyers, with evidence of the new grant and the departing holder’s remaining obligations.

The recommended protection for later holders is an independent direct grant unaffected by a predecessor’s unpaid royalty. Treat that protection as an express commercial provision. Good faith alone does not create missing copyright permission, and an upstream licence ending can affect a dependent sublicense. CDPA section 90(4), which concerns successors to copyright ownership, does not transfer a seller’s debt to later token holders.

For non-payment, finance should establish the agreement, covered sale, consideration, credits and unpaid balance. Send the debtor a statement identifying the calculation and available dispute process. Draft proportionate notice and cure provisions before suspension or termination. State whether payment restores permissions and which accrued rights survive.

An unpaid contractual royalty supports the contractual remedies established by the agreement and applicable law. Copyright proceedings additionally require a protected act outside permission. US authority distinguishes licence conditions from ordinary covenants, while recognising a special payment-related qualification. Continued licensed use without required payment can raise infringement issues; bare token resale does not establish them. (CDPA 1988, ss. 16, 96; MDY Industries, 939–941 & n. 4.)

Termination should operate on the identified licence and holder. It does not itself reverse a blockchain transfer or retrospectively invalidate uses previously authorised. A later holder with an independent valid grant should retain the protection promised in that grant. If permission was never obtained, analyse the actual use and statutory exceptions before alleging infringement. The UK restriction on damages for innocent infringement concerns ignorance that copyright subsists, rather than ignorance of someone else’s unpaid royalty. (CDPA 1988, ss. 16, 97(1).)

Avoid automatic punitive multiples or compulsory surrender of valuable tokens for small arrears. English penalty doctrine examines secondary obligations imposing detriment out of all proportion to a legitimate interest. Consumer fairness remains a separate requirement. A burn, freeze or seizure function requires both a lawful contractual basis and the technical power described to buyers. (Cavendish Square Holding BV v Makdessi [2015] UKSC 67, [13], [32]; Consumer Rights Act 2015, s. 62, sch. 2, paras. 6–8.)

Finally, allocate responsibility for platform changes. Name the administrator who can alter royalty recipients, validators or supported routes. Require notice, version records and reassessment of affected transfers. A technical update must not silently increase an existing holder’s contractual burden. Preserve a usable reporting and payment route during platform disruption, and obtain fresh agreement where the proposed legal change requires it. (Consumer Rights Act 2015, s. 62, sch. 2, paras. 10–15.)

The studio can proceed with the relevant sales flow once the rights grant, acceptance evidence, payment terms and tested route agree. Unsupported routes should carry an accurate description of their collection limits. Claims about automatic payment should identify the transactions for which the evidence supports them.

Review NFT licence and royalty terms

Review NFT licence and royalty terms. Provide the holder agreement, resale process, target countries and proposed collection settings. Licentium can scope the agreement changes and buyer-rights summary needed to connect those arrangements.

Request a consultation
guideNFTIntellectual PropertyWeb3