Fees guide

Telegram Gift Marketplace Fees

Separate the gross sale price from seller and buyer fees, royalties, network, withdrawal and conversion costs to estimate net proceeds.

Reviewed

A crystal gift on a balance scale beside layered fee tokens and a market curve
Compare marketplaces by the amount you spend or receive after the complete route.

Cost map

How to handle each fee type

Record only what the current flow shows or what you deliberately enter as an assumption.

CostWhere to verifyIf unknown
Seller or buyer feeFinal marketplace order or listing flow.Keep that side's net result unavailable.
RoyaltyCollection and marketplace terms for the exact asset.Do not merge it into a guessed marketplace rate.
Network or transferWallet or transaction confirmation for the action.Mark the on-chain or transfer total incomplete.
Withdrawal or conversionPayout screen, supported route and quoted currency.Report proceeds before this step, not after it.
Other fixed costThe exact prompt, receipt or manually documented scenario.List it separately and do not hide it in rounding.

There is no universal fee schedule

Costs depend on the destination, action, item, settlement currency and current terms. A seller fee shown in one flow is not automatically the buyer fee, royalty or withdrawal cost in another.

Use only a fee shown by the destination, documented by a primary source or entered manually for a scenario. Do not publish a universal marketplace rate from memory or copy an old assumption into a current transaction.

Stored market data

Small percentages matter at market scale

Current snapshot

This stored market series and current gift table make fee calculations concrete. Apply the destination's verified rate to the actual transaction amount.

Total market cap
77,818,102 TON+173.27%
Fresh snapshot
Daily total market cap across broadly covered stored collection snapshots. The series runs from to ; missing observations are not synthesized.
Latest stored total
77.8M TON
Full-series move
+173.3%
Collections covered
116
Snapshot date

Comparison table

Floor, supply and market-cap context

CollectionFloor7DPublished supplyMarket cap
Desk Calendar thumbnailDesk Calendar3.69 TON+0.8%500,0001M TON
Liberty Figure thumbnailLiberty Figure3.44 TON+17.0%300,000849.4K TON
UFC Strike thumbnailUFC Strike12.2 TON+3.9%60,000717.5K TON
Light Sword thumbnailLight Sword5.05 TON+10.0%150,000631.5K TON
Xmas Stocking thumbnailXmas Stocking2.5 TON+6.4%600,000561.9K TON
Plush Pepe thumbnailPlush Pepe4,700 TON+0.0%3,00013.3M TON

Source: stored marketplace snapshots in this project. Floors are reference observations, not guaranteed sale prices or trade offers.

Separate each possible cost

Seller and buyer fees are marketplace charges applied to different sides of a transaction. A royalty may be a separate collection or creator deduction. A network fee can apply to an on-chain transfer. Withdrawal, transfer, conversion or payment charges may appear later in the flow.

A fee can be a percentage, a fixed amount or a combination. Record its currency and the base it applies to; the same-looking rate can produce a different result when the charge is calculated from another amount.

Gross sale value and net proceeds

Gross sale value is the amount paid or displayed before deductions. Net proceeds are what the seller receives after every seller-side cost that actually applies.

A useful scenario is: gross sale value minus known seller fee, royalty, network, transfer, conversion and withdrawal costs. If any required input is unknown, label the net result incomplete or unavailable; an unknown fee is not zero.

Keep currency and conversion visible

A listing can be denominated or settled in Stars, TON or another supported unit. Keep the original amount visible and state the conversion reference separately.

USD and cross-currency totals are estimates when they rely on a stored or manually entered rate. Timing, rounding and the actual payment or withdrawal route can change the final amount.

Fees are not the whole pricing gap

The spread between a seller's ask and the price a buyer will execute can be larger than the published fee. Low liquidity, thin listing depth and a specific attribute combination can widen that gap.

Do not use the collection floor as a guaranteed execution price. It is a visible or stored asking-price reference and may not match the item, available quantity or final transaction.

Use calculators as editable scenarios

The GiftsWatch Fee Calculator contains stored reported seller-fee assumptions that are editable. Replace the relevant rate with the value shown in the current marketplace flow, and clear it when you cannot verify it.

The Profit Calculator can add a purchase price and known extra costs. Its result is still a scenario: it does not predict liquidity, execution price, listing availability or price movement.

Verify the final amount before confirming

On the destination, review the final price, every visible deduction, settlement currency and amount receivable. Check any separate transfer or withdrawal step before treating the sale as complete.

Save the confirmation and transaction record. If the final amount differs from the scenario, use the marketplace receipt or transaction data as the factual record and update your assumptions.

A practical framework for Telegram Gift marketplace fees

Marketplace fees are rarely captured by one percentage. A buyer may pay a listing amount, platform charge, conversion spread and wallet cost. A seller may face commission, royalty, withdrawal friction and another conversion before reaching the desired currency. Some costs are explicit; others appear as a worse exchange rate or a balance that cannot be used in the same way as TON or cash. An honest comparison follows the money from the starting asset to the final usable balance.

The most useful way to approach Telegram Gift marketplace fees is to start with the decision you actually need to make. Your goal is to compare routes on an all-in basis and avoid mistaking a low advertised fee for a cheap transaction. That sounds simple, but it prevents a common research failure: collecting dozens of prices, screenshots and opinions without deciding which evidence can change the answer. Write the decision in one sentence, set a maximum amount of money or time you are prepared to risk, and define the condition that would make you walk away. A clear boundary turns market information into a decision tool instead of a source of pressure.

For this guide, the central question is which marketplace and settlement route produces the best verified outcome for this specific purchase or sale. Answer it in layers. First establish what the item, balance or marketplace action really is. Then confirm that the route is available to your account and region. Only after those checks should you compare prices, fees and timing. If any earlier layer is uncertain, a precise-looking number at the end of the process is still unreliable. This order also makes it easier to explain the decision later, because every conclusion has a visible reason behind it.

The beginner trap is comparing headline commissions while ignoring spread, settlement asset, withdrawal conditions, network costs and the value of time. Avoiding it does not require advanced trading knowledge. It requires a slower first pass, consistent comparison units and a refusal to treat an asking price as proof of value. A good process is intentionally boring: identify, verify, compare, calculate, execute, and record. The same sequence works whether the amount is small or large; what changes is how much evidence you require before accepting uncertainty.

Build an evidence stack before trusting a number

Useful research separates facts from estimates. For Telegram Gift marketplace fees, the strongest starting evidence is the destination's current confirmation and payout screens, official fee disclosures where available, and a timestamped conversion quote. A marketplace screen can show what is offered now, while a stored tracker can show how a reference moved over time. Community posts may reveal sentiment or a newly noticed attribute, but they are not a substitute for the actual item page or the current transaction screen. Label every note as official rule, live listing, stored snapshot, completed result, or opinion. That single habit prevents very different kinds of evidence from being blended into one confident claim.

Fee schedules and product flows can change faster than evergreen articles. Treat every percentage in a guide as a framework input, not a permanent promise. Recheck the platform immediately before acting and preserve what the final screen shows. If a fee is bundled into a quoted rate, compare the effective amount received with an independent reference rather than calling the route fee-free.

Freshness matters as much as source quality. Record when you checked each value, which currency it used, and whether the page described a collection floor, a model floor or one individual listing. If two sources disagree, do not average them automatically. Investigate the scope first: one may include attributes, fees or a different marketplace population that the other excludes. The right comparison is not the largest dataset; it is the smallest set of observations that actually answers the decision you wrote down.

  • Define the starting asset and the final balance you actually want.
  • Capture platform commission, royalty, network and withdrawal charges.
  • Measure the conversion spread using quotes taken at the same time.
  • Separate fixed costs from percentage costs and buyer fees from seller fees.

Work a real listing from identity to execution

Suppose one marketplace advertises a lower seller commission but pays into a balance that must be converted twice, while another charges more and settles directly into the desired asset. The first route wins on the fee label and can still lose on net proceeds. Model both paths as a sequence. Use the same assumed sale price, timestamp the exchange rates and compare the final usable amount after every step.

Start with the exact object: the transaction amount, side of the market, marketplace, settlement currency, custody path and desired final balance. Copy the identifying details into your notes before looking at price. Next choose a comparable that shares the attributes buyers are likely to care about: the same gift and transaction size executed through alternative routes at near-identical reference rates. A collection-wide floor can provide context, but it should not silently replace a model-level comparison. When there are few close matches, widen the set one dimension at a time and state what changed. This keeps an imperfect comparison honest and stops a rare-looking trait from acquiring an invented premium.

Then verify the route itself. For fee research, open a representative transaction flow far enough to see the complete breakdown without approving it, and confirm how proceeds become available. Open the destination from a trusted bookmark, Telegram's own interface, or a link you independently confirmed. Check the domain after the page loads and again before approving a wallet action. Read the asset, amount, currency, recipient and permission request on the final screen. If the listing disappears, the price changes, or the wallet request describes a different action, stop and restart from the verified item page rather than trying to rescue the transaction.

Finally, separate observation from execution. A visible offer tells you what a seller is asking; it does not guarantee that the item remains available, that the transaction will settle at that amount, or that you could immediately reverse the trade. Take a timestamped note of the final screen, but never share seed phrases, one-time codes or private wallet information in the process. The objective is a transaction you can explain and verify, not merely a transaction completed quickly.

Calculate the real outcome, not the headline price

A headline price is only the first line of the calculation. Normalize every candidate into one comparison currency at a stated reference rate, then add marketplace fees, royalties or commissions shown by the destination, wallet or network costs, spreads between conversion routes, and any amount lost while moving between Stars, TON or another balance. Keep uncertain charges as a range instead of hiding them inside a single estimate. When two routes use different settlement assets, compare the amount you can actually spend or withdraw after the entire sequence, not the number shown at the first step.

Use two formulas. Buyer all-in cost equals listing price plus buyer-side platform charges, conversion spread, network cost and any funding fee. Seller net proceeds equal sale price minus commission, royalty, network or withdrawal costs and conversion spread. For small transactions, fixed costs can dominate; for larger transactions, percentage costs matter more. Calculate in native units first, then convert the final totals with one dated reference rate.

Run at least three scenarios: expected, adverse and break-even. The expected case uses the current verified inputs. The adverse case assumes a weaker sale price, a wider spread or a longer wait. The break-even case solves for the minimum result that recovers all costs. This is especially important in a thin market, where one low listing or one enthusiastic buyer can distort the apparent floor. A scenario table does not predict the future; it makes your assumptions visible before money is committed.

Treat time as a cost as well. A route that appears cheaper may require manual matching, multiple conversions or a long holding period. A faster route may justify a modest premium when certainty matters, while a collector with no deadline may prefer patience. Write down which trade-off you are choosing. If the decision changes only because one volatile reference moved a few percent, the margin of safety was probably too small from the beginning.

Stress-test the plan before the final click

The main analytical risk is false precision. A spreadsheet can produce a result to several decimal places even when the fee rule, exchange rate or withdrawal path is uncertain. Mark estimates as ranges and add a confidence note. The operational risk is approving a transaction because it matches the spreadsheet while the live screen shows a changed fee or asset. The live verified confirmation always supersedes the earlier model.

Separate market risk from operational risk. Market risk means the item may become less desirable, less liquid or cheaper. Operational risk means you may use the wrong domain, approve the wrong wallet action, misunderstand custody, send to the wrong recipient or discover that the route is unavailable. A cheap purchase does not compensate for an unsafe route. Resolve operational uncertainty first, because it can turn a manageable market loss into a complete loss of access or assets.

A seller calculates profit using a marketplace's commission but forgets that the payout must be converted through a thin pair. The quoted sale looks profitable; the final balance falls below cost after spread. The solution is not a more complicated profit percentage. It is drawing the full settlement route before listing and testing the conversion with a realistic amount.

Use a pause rule for urgency. If a seller, bot, private message or countdown pushes you to skip a check, wait. Genuine market opportunities can disappear, but security decisions made under artificial pressure are rarely worth preserving. For an unfamiliar marketplace, test the smallest practical amount and verify the result in the destination account before increasing size. Never approve a vague signature merely because the page design looks familiar.

  • Are every route's start and end assets identical?
  • Were exchange quotes captured at comparable times and sizes?
  • Does the final screen agree with the modeled fee breakdown?
  • Is the difference large enough to matter after uncertainty and time?

Keep a small research notebook

A research notebook turns one decision into reusable experience. It can be a spreadsheet, a private note or a simple table, but every row should preserve enough context to reconstruct the conclusion. Record the timestamp, destination, exact item or balance, visible attributes, asking price, normalized price, known fees, source links and the action you took. Screenshots are useful supporting evidence, yet searchable text is better for comparison. Store only public market information; never store seed phrases, passwords, recovery codes or unnecessary personal data.

Maintain a route calculator with one column per step rather than one field called fees. Store native amount, rate, fixed charge, percentage charge and resulting balance. Add a source link and checked date to every input. When a platform changes terms, update that row rather than rewriting old outcomes; historical calculations remain useful for understanding why a previous decision was reasonable.

Review the note after the outcome is known. Ask which assumption mattered most, which source was stale, whether the closest comparable was genuinely comparable, and whether the final cost matched the estimate. Do not rewrite the original prediction to make it look correct. The gap between expectation and result is the valuable part. Over time, this record shows where your process is reliable and where you tend to overpay, rush, underestimate fees or confuse rarity with demand.

Set a refresh trigger rather than checking constantly. Revisit the decision when a verified platform rule changes, a materially closer comparable appears, the relevant floor moves beyond your chosen range, or your own objective changes. Constant monitoring creates noise and encourages impulsive action. A defined trigger protects attention while still keeping the analysis current enough for the decision it supports.

  • Starting asset, amount and transaction side
  • Every route step and resulting balance
  • Fixed fees, percentage fees and conversion spread
  • Reference rates, sources and checked time
  • Final usable amount and uncertainty range

What a good decision looks like

The cheapest marketplace is the route with the strongest verified net outcome for your transaction, not the smallest fee badge. A useful fee comparison is reproducible, timestamped and explicit about the starting asset, final balance and uncertain inputs.

A good outcome is not automatically a profitable one. It is a decision made with verified identity, an appropriate comparison set, explicit costs, a realistic exit or completion path, and risk small enough that an adverse result remains acceptable. Markets can move after excellent research. Judge the quality of the process separately from the short-term price move, then use the result to improve the next decision.

Recheck fee-heavy routes whenever transaction size changes. A method that is efficient for a valuable collectible may be wasteful for a low-priced gift because fixed costs occupy a larger share. Keep convenience and custody in the comparison as well: a slightly higher transparent cost can be rational when it removes an uncertain conversion or transfer step.

Before acting, return to the one-sentence decision at the start of this field manual. If the evidence answers it and the final screen matches the plan, proceed at the size you chose. If you still need a story to explain away a missing fact, an unexplained premium or an unverified route, the correct action is to pause. The ability to skip a questionable trade is part of the edge, not a failure to participate.

FAQ

Frequently asked questions

Should an unknown marketplace fee be entered as zero?

No. Zero is a factual rate, while unknown means the required input is missing. Leave the estimate unavailable or label it incomplete until the current fee is verified.

Is the lowest fee always the best sale route?

No. The final result also depends on liquidity, the execution price, settlement currency, supported actions and every other applicable cost.

Sources

Primary sources consulted

  1. Telegram Gifts API referenceTelegram · reviewed 2026-07-21
  2. Gift Marketplace, Posting Several Stories at Once, Auto-Translate For ChannelsTelegram · reviewed 2026-07-21
  3. Blockchain limits: gas and fee parametersTON Docs · reviewed 2026-07-21