TradingView derivatives workflows

Funding rates on TradingView: venue, interval and price basis

TradingView funding rate data describes payments between perpetual futures longs and shorts. Open Indicators → Fundamentals → Derivatives → Funding rate. For a position-cost study, select the exact futures contract and inspect non-aggregated data. Then check the exchange settlement interval, final rate and valuation price. A funding chart is not an account statement, and a built-in metric does not establish that the same series is available to Pine Script.

See the decision guide

Choose a single venue before reconciling a payment

TradingView offers aggregated and non-aggregated funding views. Its aggregate weights venues by open interest. Spot charts and coin symbol pages show aggregated data; select a futures contract for the individual-exchange view. An aggregate describes a market sample, while your payment belongs to one contract on one venue.

  • Record the full exchange-qualified chart symbol, contract type, quote or settlement currency, aggregation setting, chart timezone and observation time.
  • TradingView documents coverage for selected venues, including Bybit, OKX and Hyperliquid. Coverage, historical start dates and aggregation eligibility vary. Check the help page and the selected contract instead of assuming every market has a live series.
  • Inspect whether the value is a forecast for the next settlement or a finalized historical rate. A screenshot before settlement cannot establish the later payment.

Compare settlement rules and the price used for notional

These official documentation checks are dated October 18, 2026. They describe mechanisms, not current quotes for a particular contract. Bybit and OKX can change settlement frequency. Read the current contract information and next settlement timestamp each time you make a comparison.

  • A last-traded candle price is not automatically the settlement mark or oracle price. Keep each price field named in the record.
  • An interest component, a premium index and a final funding rate are different inputs. Caps, clamps and interval conversions prevent reconstructing every venue rate from a simple spot-versus-perpetual spread.
  • Read the API or interface field definition before dividing by eight. An already-hourly rate must not be divided again.
Venue and contract scopePayment intervalPosition valuation for funding
Bybit USDT / USDC perpetualsPair-specific. An 8-hour schedule uses 00:00, 08:00 and 16:00 UTC; reaching a rate limit can trigger hourly settlement.Base-asset quantity × mark price. Inverse contracts instead divide USD contract quantity by mark price, settling in the base coin.
OKX crypto perpetualsDefault 8 hours; specified contracts use 1, 2 or 4 hours. Automatic frequency changes can move through 8, 4, 2 and 1 hours.Linear: contracts × contract size × multiplier × mark price. Crypto-margined: USD face value × multiplier × contracts ÷ mark price.
Hyperliquid perpetualsPaid hourly. Its documented 8-hour formula is divided by eight for each hourly payment.Base-asset position size × oracle price × hourly funding rate. The funding payment uses oracle price, not mark price.

Reconcile a dated payment with both position sides

This invented linear USDT contract has an 8-hour schedule and no interval change. Both sides below hold 0.4 BTC across the listed assessments. Use positive cash flow for a receipt and negative cash flow for a payment: long cash flow = -quantity × settlement mark × decimal rate; short cash flow is the opposite. These are arithmetic examples, not exchange observations.

  • At 08:00, 0.012% = 0.00012, so 0.4 × 63,250 × 0.00012 = 3.036 USDT. The earlier +0.009% forecast would give 2.277 USDT at that same mark, a different result.
  • At 16:00, the negative rate makes the long receive 0.4 × 62,800 × 0.00006 = 1.5072 USDT. Preserve full precision and reconcile exchange rounding separately.
  • For an inverse illustration, 12,650 USD of face value at 63,250 USD/BTC equals 0.2 BTC. At +0.012%, the long pays 0.000024 BTC. Converting it to dollars later introduces a separate conversion price.
  • A position fully closed before the assessment ordinarily avoids that payment. Bybit warns that opening or closing within five seconds of funding does not guarantee inclusion or exclusion. Use executed closure and the posted funding record, not the time an exit order was submitted.
UTC timestamp and recordRate and valuationLong / short cash flow
2026-10-17 07:45:00: forecast saved+0.009%; next assessment 08:00No booked payment yet
2026-10-17 08:00:00: final assessment+0.012%; mark 63,250 USDT; notional 25,300 USDT-3.036 / +3.036 USDT
2026-10-17 16:00:00: final assessment-0.006%; mark 62,800 USDT; notional 25,120 USDT+1.5072 / -1.5072 USDT
2026-10-18 00:00:00: expected record missingRate unavailableUnknown; do not book 0
Known subtotal onlyTwo verified hypothetical assessments-1.5288 / +1.5288 USDT

Annualize a rate without turning it into a promised return

For a decimal payment rate r every h hours, a simple annualized rate is r × (24 / h) × 365. A hypothetical compounded equivalent is (1 + r)^(365 × 24 / h) - 1. Multiply either result by 100 to display percent. The compounded calculation assumes the same positive receipt rate all year and reinvestment each period with no costs. Funding payments do not automatically satisfy those assumptions.

  • The smallest quoted rate in the table has the largest annualized rate because it repeats most often. These are normalization examples, not forecasts.
  • The table uses the receiving side at positive funding. A long paying +0.012% has a simple annualized funding cost of 13.14% of fixed notional under the same assumptions. That is not a 13.14% account-equity loss forecast.
  • Leverage changes the margin denominator. It does not multiply the payment when position quantity and valuation price stay fixed. Account return also depends on price P&L, cash balances and other positions.
  • If the interval changes, keep each actual payment timestamp. On an invented 10,000 USDT constant notional, one +0.012% payment followed by four hourly +0.002% payments totals 2 USDT over 12 hours. Its simple observed annualization is (2 / 10,000) × (8,760 / 12) = 14.6%, conditional on repeating that window.
  • When notional or funding signs change, sum the actual cash flows first. State the capital denominator and elapsed hours. A missing assessment makes the full-window result incomplete; a recorded zero rate is a valid zero payment.
Invented constant payment rateSimple annualizedCompounded equivalent
0.012% every 8 hours: 1,095 periods/year13.14%14.04%
0.005% every 4 hours: 2,190 periods/year10.95%11.57%
0.002% every hour: 8,760 periods/year17.52%19.15%

Separate what Pine can request from what the chart displays

Pine request.security reads TradingView symbol data; it is not a general exchange REST client. The official Pine request documentation checked for this page does not identify a funding-rate-specific request function or a universal funding ticker format. This guide therefore does not supply a guessed funding symbol. A normal perpetual price ticker supplies price data, not a funding history.

  • For a verified symbol, the request documentation distinguishes gaps from carried-forward values and allows invalid requests to return na with ignore_invalid_symbol. Preserve that unavailable state; substituting zero would invent a measurement.
  • Forward-filling a settled rate across intraday bars is a display choice. Counting each repeated bar as a new funding payment would multiply the cost incorrectly.
  • Keep observation time and settlement time separate in historical work. A finalized rate discovered after assessment cannot support an earlier decision. Do not use future data through lookahead settings.
  • No direct funding feed was independently validated for this page. Until one is validated for your contract, use the native chart for inspection and the exchange ledger for payment research. A compiling script would not prove data availability.
Data pathWhat you can establishLimit to preserve
Built-in Funding rate indicatorRead the supported metric and selected aggregation in Supercharts.Native display alone does not verify an equivalent Pine-requestable feed.
An independently verified TradingView data symbolrequest.security can retrieve available symbol observations at a chosen timeframe.Confirm that the exact symbol exists, represents funding, has documented units and matches several settlement records before using it.
Manually entered rate and intervalPine can calculate a scenario using supplied numeric inputs.A constant input does not become a live feed or historical funding series.
Exchange settlement historyReconcile event timestamps, final rates and account cash flows outside Pine.An API URL cannot be passed to request.security as a data source.

A funding receipt can still accompany a net loss

Consider an invented hedge with long spot and short perpetual positions of equal base quantity. Over one day it receives 8 USDT of funding, incurs 6 USDT of total entry/exit fees and 3 USDT of slippage, and loses 5 USDT from the change in the spot-perpetual basis. Net result = 8 - 6 - 3 - 5 = -6 USDT, before borrowing, transfer costs or taxes. Equal quantities do not remove basis or execution risk.

  • Funding can reverse before a planned exit. Spot borrow costs, unavailable borrow and collateral currency changes can alter the result.
  • A hedge spread across venues still faces liquidation on an individual leg, transfer delays, outages and counterparty risk. An offsetting gain elsewhere may not arrive in time to meet margin.
  • Open interest can help describe position activity, but it is neither the funding rate nor proof of the next price move. Crowded positioning does not specify when a reversal will happen.

Keep a research record that can be checked later

Save one row per assessment with venue, contract, linear or inverse basis, interval, UTC timestamp, rate status, rate units, quantity, mark or oracle price, settlement currency and actual cash flow. Keep the source link and screenshot beside the calculation. Record missing events explicitly so a later review cannot mistake an incomplete ledger for a profitable one.

  • Use Pineify Trading Journal plan and review notes to preserve assumptions and attach the chart screenshot to a trade. Record funding reconciliations in notes; this workflow does not claim an automatic exchange funding import.
  • For AI Chart Analysis, upload a candlestick chart of the same contract and period, with the funding panel or annotations visible. Keep the symbol, timestamps and settings in the image. Use the analysis to review visible price context; it does not verify funding settlements or recover missing data.
Where Pineify fits

Trading Journal

Keep the funding hypothesis, dated settlement calculations and screenshots with your trade review. Enter verified records manually and retain the original exchange statement for reconciliation.

Also useful: AI Chart Analysis. Upload a candlestick chart of the same contract and period with funding context visible. Review the price-chart interpretation separately from the exchange ledger; this does not verify funding payments or execute trades.

Review Trading Journal

Frequently asked questions

Educational information, not investment advice. All payment, price, rate and return examples are hypothetical. Funding receipts and hedged positions can produce losses. This page does not provide live funding quotes, automatic arbitrage or trade execution.

Sources and verification

Published by Pineify. Pineify is an independent product and is not affiliated with TradingView. Sources support the technical explanations; examples do not establish trading performance.