Before launching an NFT collection, map every payment route from buyer to creator, collaborator, marketplace, and tax record. This guide compares primary-sale splits, secondary royalties, smart-contract distributions, and custodial payouts, then shows how to estimate net proceeds with transparent assumptions. Use the formulas, agreement template, and launch checklist to test your NFT payment split before publishing a contract or opening an NFT checkout.
Overview
An NFT royalty split is not one universal feature. It can refer to a division of primary-sale revenue, a creator royalty requested or enforced on secondary sales, or a payment arrangement handled by a marketplace, payment gateway, or smart contract. These mechanisms have different timing, fee, refund, and dispute implications.
The first step is to separate the collection’s income into two channels:
- Primary sales: the initial sale of an NFT by the creator, project, or authorized merchant.
- Secondary sales: later transfers or resales made through a marketplace or other supported venue.
A primary sale can often be divided according to a smart contract, checkout configuration, or off-chain accounting process. A secondary royalty may depend on the receiving marketplace and its treatment of royalty instructions. Policies, supported tokens, enforcement methods, payout limits, and fees can change, so do not describe a royalty as guaranteed until you have verified the specific marketplace and contract behavior.
| Model | Best suited to | Payment timing | Main trade-off |
|---|---|---|---|
| Smart-contract split | On-chain primary sales and defined collaborators | At or shortly after settlement, depending on implementation | Requires careful contract testing and address verification |
| Marketplace-enforced royalty | Secondary-market creator compensation where supported | When an eligible resale settles | Coverage and enforcement may vary by marketplace |
| Custodial marketplace payout | Teams preferring a platform-managed workflow | According to the platform’s payout schedule | Introduces platform rules, limits, and counterparty dependence |
| Manual collaborator payout | Small teams with trusted accounting controls | After sale reconciliation and approval | More operational work and greater risk of missed or incorrect payments |
For a broader view of checkout choices, review the NFT payment gateway comparison. Whichever model you choose, document who receives funds, in which token, on which network, and under what conditions.
How to estimate
Use a simple waterfall calculation for each sale. The goal is to avoid treating the list price as the amount available for collaborators.
Net distributable amount = gross sale value − marketplace fee − payment-processing fee − gas charged to the project − refunds or reserves.
Then apply the agreed split:
Collaborator payout = net distributable amount × collaborator percentage.
Creator or project share = net distributable amount − all collaborator payouts.
If a fee is percentage-based, calculate it from the correct base. For example, a 5% marketplace fee on a 2 ETH sale is 0.10 ETH before any other deduction. If the platform applies fees to a different amount, use that documented basis instead. Fixed fees should be entered separately rather than combined casually with percentage fees.
For multiple collaborators, the percentages should normally total 100% of the defined distributable pool. If the project retains a reserve, state whether that reserve is taken before or after collaborator shares. Avoid vague wording such as “artists receive a portion of proceeds.” Specify the pool and the calculation order.
For token conversions, select one accounting method before launch. You might record every payout in the settlement token, or convert each sale to a reference currency at the transaction time for bookkeeping. Do not mix methods across sales without recording the conversion rate, timestamp, network, transaction hash, and wallet involved.
Primary-sale estimates should also account for failed transactions, underpayments, canceled orders, and refunds. A checkout can display a split while still requiring operational handling when a payment does not settle exactly as expected. The NFT checkout troubleshooting guide covers these exceptions in more detail.
Inputs and assumptions
Create a payout worksheet with one row per sale or settlement batch. At minimum, include:
- Token sale price and token symbol.
- Blockchain network and collection contract.
- Marketplace, NFT checkout, or payment gateway.
- Marketplace, gateway, and network fees, with their calculation bases.
- Refund, reserve, or chargeback assumptions, if applicable.
- Each collaborator’s legal or business name, wallet address, and percentage.
- Settlement date, transaction hash, and payout status.
Separate a royalty rate from a payment split. A 7% secondary royalty is not automatically the same as a 7% share of primary-sale proceeds. Likewise, a collaborator may receive 20% of primary-sale net proceeds but no secondary royalty, or a separate percentage may be negotiated.
Consider these implementation choices before launch:
- Smart-contract split: funds are directed by code. This can reduce manual work, but an incorrect wallet address, token rule, or upgrade path can be difficult to correct.
- Custodial payout: a marketplace or service holds or routes funds before paying recipients. This may simplify onboarding but requires review of payout timing, supported assets, withdrawal rules, and account controls.
- Manual payout: one treasury wallet receives funds and the administrator sends shares. This is flexible, but it needs two-person approval, reconciliation, and clear evidence of every payment.
Use a dedicated treasury or payout wallet where appropriate, limit signing permissions, and verify recipient addresses through an independent channel. A wallet connection does not prove that a displayed address belongs to the intended collaborator. For operational controls, see the NFT wallet security checklist and the guide to monthly NFT payment reconciliation.
Collaborator-split agreement template
Adapt this outline with legal and tax advice appropriate to your situation:
Project: [collection name and contract address, if available]
Participants: [names or entities]
Primary-sale pool: [gross receipts or net receipts after specifically listed deductions]
Primary-sale shares: [recipient and percentage for each participant]
Secondary royalties: [rate, eligible venues if defined, and whether the rate is separate from primary-sale shares]
Fees and gas: [who pays each fee and how it is calculated]
Payment asset and network: [token, chain, and conversion method if needed]
Timing: [automatic settlement, scheduled batch, or manual payment deadline]
Refunds and disputes: [who may approve them and how already-paid shares are handled]
Wallet changes: [verification procedure and notice period]
Records: [required transaction hashes, statements, and reconciliation schedule]
This outline is a business record, not a substitute for a contract or tax advice. It is especially important to clarify whether percentages apply before or after fees and whether the arrangement continues after a collaborator leaves.
Worked examples
Example 1: Primary sale with two collaborators
Assume, for illustration only, one NFT sells for 2 ETH. The marketplace fee is assumed to be 5%, the gateway fee is assumed to be 1%, and the project records 0.02 ETH of network cost. There is no reserve or refund in this example.
- Gross sale: 2.00 ETH
- Marketplace fee: 0.10 ETH
- Gateway fee: 0.02 ETH
- Network cost: 0.02 ETH
- Net distributable amount: 1.86 ETH
If the illustrator receives 30% and the developer receives 20% of net proceeds, their estimated payouts are 0.558 ETH and 0.372 ETH. The project share is the remaining 50%, or 0.93 ETH. These are illustrative inputs, not a statement of prevailing fees.
Example 2: Secondary royalty
Assume a later resale is 1 ETH and the collection’s stated royalty is 5%. The theoretical royalty is 0.05 ETH before any marketplace-specific deductions or limitations. If the marketplace does not honor, enforce, or route that royalty in the relevant transaction, the actual result may differ. Record the marketplace, sale transaction, stated royalty, received amount, and any fee in the reconciliation sheet rather than assuming the configured percentage was paid.
Example 3: Stablecoin or multi-token checkout
If buyers can pay with more than one token, calculate the split in the settlement asset actually received. If the agreement promises a share in a reference currency, define the conversion source and timestamp in advance. Otherwise, collaborators may receive different economic outcomes from identical percentage shares because token values move between authorization, settlement, and conversion.
When to recalculate
Recalculate the model before every collection launch, contract upgrade, collaborator change, or expansion to another marketplace. Also revisit it when a payment gateway changes its fee basis, a marketplace changes royalty handling, a supported token is added or removed, a network changes its transaction-cost profile, or the project introduces refunds, reserves, subscriptions, or token-gated benefits.
At launch, use this verification checklist:
- Confirm the collection contract address and the deployment network from a trusted project record.
- Copy each payout wallet address from a verified source; compare it character by character and confirm a small test transfer where appropriate.
- Recalculate that all collaborator percentages match the defined pool and total the intended allocation.
- Run a test transaction or testnet flow covering the supported token, checkout, split logic, refund path, and transaction records.
- Confirm who pays gas and whether gas is deducted before or after the split.
- Check marketplace royalty treatment rather than relying only on a collection-page display.
- Save the deployed code or configuration, agreement version, fee assumptions, wallet approvals, and test transaction hashes.
- Assign one person to reconcile receipts and another to approve payouts.
Keep a dated version of the worksheet so that a later change does not overwrite the assumptions used for earlier sales. This makes collaborator questions, tax preparation, and customer support easier to resolve. For multi-wallet operations, the guide on tracking NFTs across wallets and blockchains can help organize records. A reliable NFT payment split is less about selecting one “best” model than making the calculation, custody path, and exceptions visible before buyers arrive.