NFT royalty disclosures should make every charge and payout understandable before a transaction is approved. This checklist helps marketplaces explain creator royalties, platform fees, buyer charges, optional payments, and chain-specific limitations, then verify that the checkout language matches what the product and smart contracts actually do.
Overview
An NFT marketplace fee page is not enough on its own. Collectors usually encounter pricing in several places: a collection page, an item page, a wallet confirmation, a fiat or crypto checkout, a receipt, and sometimes a secondary-sale history. Creators may also see a different view in their dashboard or payout report. A reliable NFT royalty policy connects these touchpoints.
Start by separating the amounts involved in each transaction:
- Asset price: the amount paid for the NFT or other digital asset.
- Creator royalty: a payment associated with a creator or rights holder when the applicable sale path supports it.
- Platform fee: the marketplace’s stated charge for listing, matching, settlement, custody, payment processing, or another service.
- Network or gas cost: a blockchain transaction cost that may be paid by the buyer, seller, marketplace, or another party, depending on the flow.
- Payment-provider charge: a separate cost that can arise when the marketplace supports cards, bank transfers, fiat conversion, or other payment rails.
- Taxes or regulatory charges: amounts that may depend on the buyer’s location, transaction type, or product configuration and should be reviewed for the relevant markets.
Do not describe every amount as a “royalty.” A royalty is a creator-related payment, while platform and payment fees compensate other participants or services. Clear labels reduce disputes and make creator earnings easier to reconcile.
Royalty behavior can also vary by contract design, marketplace settings, token standard, chain, wallet flow, and whether the transaction occurs inside or outside the marketplace. The policy should state what the marketplace controls, what the creator’s contract supports, and what cannot be guaranteed. For revenue routing and payout logic, use the operational checks in the NFT marketplace revenue splits checklist.
Checklist by scenario
1. Primary sale or mint
- Show the item price and currency before the buyer connects a wallet or begins payment.
- Identify whether the creator royalty is included in the listed price, added separately, or routed from proceeds.
- Explain who pays network costs and whether the marketplace is sponsoring or abstracting those costs.
- State whether a card or fiat checkout uses a payment provider and whether its charge is included in the displayed total.
- Show the estimated amount the creator receives, using careful language if final settlement can change.
- Match the collection page, checkout, receipt, payout report, and transaction record.
2. Secondary sale on the marketplace
- Display the seller’s asking price separately from the platform fee and any creator-related amount.
- Explain whether the royalty is calculated as a percentage, a fixed amount, or another contract-defined value.
- Identify the party responsible for each charge: buyer, seller, marketplace, or creator.
- Show an estimate of seller proceeds and creator proceeds before approval.
- Record the applied policy version, contract address, token identifier, chain, and transaction identifier for support and reconciliation.
3. Optional creator royalties or buyer-selected payments
If a payment is optional, label it as optional at the point where the user makes the decision. Do not present a selected default as though it were mandatory. A suitable checkout pattern is:
Creator payment: optional. You may choose the amount shown or continue without adding a creator payment. This selection may affect the total charged and the amount routed to the creator.
The marketplace should record the user’s selection, the final amount, and the routing result. The creator agreement should explain how optional payments are represented in reports and whether the marketplace promotes or recommends a particular setting.
4. Cross-chain, third-party, or unsupported transaction paths
- List the supported chains and the exact transaction types covered by the policy.
- Explain when a transfer, bridge, external wallet, or third-party marketplace may change the available royalty behavior.
- Do not imply that a marketplace can enforce a payment on every chain or across every contract type unless that capability has been tested.
- Tell users what happens when the contract does not expose the required royalty information or the marketplace cannot verify it.
For cross-chain assumptions, pair the policy review with a cross-chain transfer due diligence checklist.
5. Refund, cancellation, or dispute
Explain whether a refund reverses creator and platform allocations, how pending payouts are handled, and whether network costs can be recovered. Avoid promising a reversal that the payment rail or smart contract cannot perform. Link the disclosure to the marketplace’s refunds and disputes workflow.
Fee-disclosure template
Use the following structure as a starting point, then replace each bracketed field with values generated from the actual transaction flow:
Total due: [amount and currency]
Asset price: [amount]
Creator royalty: [amount or percentage, recipient, and whether mandatory or optional]
Marketplace fee: [amount or percentage and payer]
Payment-provider fee: [amount, included or separate, if applicable]
Network cost: [estimated, sponsored, included, or paid separately]
Estimated creator proceeds: [amount, with conditions or settlement caveat]
Chain and contract: [network, contract address, token identifier, and supported transaction type]
Important limitation: [plain-language explanation of unsupported wallets, contracts, chains, external sales, or changing estimates]
At checkout, keep the first view short. Put calculation details behind an expandable explanation, but do not hide a mandatory charge or use “from” pricing when the buyer is about to approve a known total. For wallet users, the marketplace should make clear whether the wallet confirmation can show a different network cost. For guest or fiat buyers, explain the conversion rate, final charge, and settlement currency in terms the buyer can understand. Review the related NFT checkout UX patterns before launch.
Royalty-policy decision table
| Situation | Policy language should say | Implementation check |
|---|---|---|
| Marketplace-controlled secondary sale | What the marketplace applies, who pays, and how proceeds are calculated | Compare displayed totals with settlement and payout records |
| Contract-defined royalty | That the amount depends on the contract and identify supported contract behavior | Read the contract data and test representative transactions |
| Optional payment | That the buyer can decline or change it, if applicable | Verify defaults, consent capture, routing, and receipts |
| Unsupported contract or external sale | What the marketplace cannot verify or enforce | Trigger accurate warnings and prevent misleading estimates |
| Fiat or sponsored checkout | Which costs are included, estimated, or paid by the platform | Reconcile provider events, blockchain events, and user receipts |
What to double-check
- Calculation order: Confirm whether the platform fee and creator amount are calculated from the asset price, gross total, net proceeds, or another defined base.
- Rounding: Document decimal precision and rounding at every stage. Small differences can become support issues when displayed values do not reconcile.
- Currency conversion: Distinguish an estimated display currency from the currency actually settled on-chain or through the payment provider.
- Chain and token coverage: Test each supported chain, token type, contract version, and wallet flow. A multi-chain NFT wallet integration should not inherit assumptions from one network.
- Event and receipt data: Ensure the NFT marketplace API, webhook events, receipts, and creator dashboard use consistent identifiers and amounts. The marketplace API data quality audit provides a useful review model.
- Creator agreement: Define the royalty recipient, payout timing, supported sale paths, adjustments, refunds, reporting access, and policy-change notice process.
- Security boundaries: Make sure transaction approval screens do not disguise fees or request permissions unrelated to the sale. Use the wallet security review workflow for permission checks.
- Regional review: Have qualified counsel review disclosures, consumer-facing wording, tax treatment, marketing claims, and marketplace terms for each jurisdiction in which the product operates. This article is an implementation checklist, not legal advice.
Common mistakes
- Calling every charge a royalty: Separate creator payments from platform, network, provider, and tax-related amounts.
- Promising universal enforcement: A marketplace should not claim to guarantee royalties across external contracts, chains, or venues it does not control.
- Showing only a percentage: Display the estimated currency amount and the calculation base so users can understand the real impact.
- Using different definitions in different screens: Align collection pages, checkout, receipts, dashboards, terms, and API responses.
- Leaving optional payments ambiguous: Make the user’s choice explicit and preserve an auditable record of it.
- Ignoring failed or partial transactions: Define how retries, pending states, reversals, refunds, and duplicate webhooks affect creator payouts.
- Updating copy without updating code: A revised policy is misleading if fee configuration, contract calls, or payment-provider behavior remain unchanged.
When to revisit
Review the royalty policy before each collection launch, seasonal planning cycle, fee experiment, contract upgrade, chain expansion, payment-provider change, or new wallet flow. Revisit it after a refund incident, creator dispute, checkout redesign, reconciliation failure, or change to the marketplace’s payout model.
Maintain a simple review record containing the policy version, effective date, supported chains and contract types, fee configuration, sample transaction results, API and webhook mappings, approval owner, and unresolved limitations. Run a test purchase or simulated transaction for every material change, then compare the result across the item page, checkout, wallet approval, on-chain record, provider record, receipt, and creator payout report.
Finally, monitor the live flow rather than relying only on documentation. Set alerts for mismatched totals, missing royalty events, unexpected fee recipients, delayed payouts, duplicate webhook processing, and transactions outside the stated support matrix. The wallet integration monitoring checklist can help structure this process. A disclosure is trustworthy when the words, interface, APIs, smart-contract behavior, and settlement records continue to agree.