How is the Perpetual Contract Funding Rate Calculated? From Settlement Rules to Platform Billing Design

A user had no new trades, yet an extra deduction appeared in their account. Operations checked the trade history, customer support checked the trading fees, and finally discovered this change came from funding fees. This issue can often be clarified in the statement, provided the page clearly displays the settlement time, payment direction, and associated position.

For platforms integrating perpetual contracts via API or SDK, the funding rate page needs to answer three questions. When is the next settlement? Which party pays under the current rate? Where can the amount be verified after settlement?

Who pays when the funding rate is positive or negative?

Perpetual contracts have no fixed maturity date. The funding rate mechanism helps the contract price track the underlying market price through periodic fee payments between long and short positions. When the funding rate is positive, longs pay shorts. When the funding rate is negative, shorts pay longs. Rates fluctuate with the market, and the currently displayed value may differ from the rate used at settlement.

According to 6MM official documentation, funding fees are settled according to contract rules, paid and received between long and short parties, and recorded separately from trading fees. The actual payment direction, amount, and settlement result can be verified in the account funding fee records and associated logs. For details, see Perpetual Contract Trading Fee Structure.

How are funding fees calculated? Understand it with an example

Taking a linear perpetual contract billed by position notional value as an example, you can estimate a single payment amount using "position notional value at settlement × absolute funding rate", and then determine whether it is income or expense based on the rate sign and position direction.

Assume the position notional value used for settlement is 10,000 USDT, the settlement rate is +0.01%, and the funding fee amount is 1 USDT. In this example, longs pay 1 USDT and shorts receive 1 USDT. If the rate changes to −0.01%, assuming all other conditions remain the same, shorts pay and longs receive.

When checking statements, look at the position valuation basis used for this settlement. For example, if a user invests 1,000 USDT in margin and holds a position with a notional value of 10,000 USDT, 10,000 USDT is used for calculation in the above example. This calculation example is used to explain the calculation relationship. The actual position, valuation price, settlement cycle, and precision used should be confirmed according to the corresponding contract rules.

How long do you need to hold a position to generate funding fees?

The basis for judgment is whether the position is included in the corresponding settlement time point; holding duration alone cannot answer this question. Assuming a contract settles at 16:00, a position opened at 15:58 that still meets the inclusion criteria at the settlement point may generate a funding fee. In contrast, a position held for several hours but closed before the settlement point typically will not generate funding fees for that period. In case of opening/closing close to settlement, partial position reductions, or time display discrepancies, the corresponding contract rules and actual settlement records shall prevail.

Therefore, the market page is suitable for displaying the next settlement time, time zone, and currently displayed rate. The statement page should display the settled time, actual payment amount, and applicable settlement rate. Pages using countdowns can also retain absolute time for user screenshots, customer support reviews, and cross-time-zone communication.

How should trading platforms build funding fee statements?

1. Let users distinguish income from expenses at a glance

Give funding fees an independent type name in the fund transaction logs, and clearly mark them as "Funding Fee Expense" or "Funding Fee Income". The same statement should ideally display the contract identifier, direction, amount, currency, and settlement time. This allows users to understand the balance change without having to understand whether the funding rate is positive or negative first.

2. Enable customer support to trace corresponding settlement records

When a user reports "where did this deduction come from", customer support should be able to find the fund log by account, contract, and time, and locate the corresponding settlement record from the log. When checking, support can first confirm the deduction type, then confirm whether there is a position meeting the rules at the settlement point, and finally re-verify the amount and page display. If settlement data is still syncing, the page should clearly state the status and retain verifiable record identifiers.

3. Run through settlement and display before launching

During acceptance testing, go through scenarios such as positive and negative rates, closing positions before settlement, partial position reductions before settlement, and duplicate receipt of the same statement record. Check the payment direction, time, amount, and currency of the front-end and back-end against the actual saved settlement records on the platform, and confirm that the same record is displayed only once in the user's log.

A clear set of funding fee statements allows users to see expectations before settlement and actual receipts/payments after settlement, and enables the platform team to trace issues along the same log when problems occur. When integrating perpetual contracts, market displays, settlement records, and account logs can be included in the same round of acceptance testing.

Build, Empower, and Drive Your Digital Asset Business

Choose a time with our product team to discuss integration needs, liquidity options, and deployment timelines.

Book a Demo