Rates change, and people write things wrong. Our stance is simple: if it's wrong, we fix it — and we say publicly what changed and why, rather than quietly swapping it out and pretending nothing happened. This page explains how we handle errors, and logs the corrections we've already made, one by one.
Our corrections policy
- Verify first. When we receive a correction, we check it against Binance's official pages or another authoritative source, and only correct when there's a genuine problem; if it turns out to be right as written, we'll reply and explain.
- Substantive corrections leave a trail. If a change touches rates, mechanics or calculation logic — anything that could affect a reader's judgment — we log it here: which article, how it read before, how it reads now, why we changed it, and the date. Typos and layout tweaks that don't affect understanding aren't logged individually.
- Handled promptly. We try to deal with incoming corrections within a reasonable time, prioritizing anything about rate timeliness.
- Sources transparent. Rate content is always marked "per Binance's current official page" with the verification month — which is itself a way to reduce errors.
How to report an error
If you spot something wrong, email [email protected], and please be as specific as you can:
- which page, which sentence or which number;
- what you believe the correct statement is;
- which official page or source backs it up (a link is ideal).
That lets us check it fastest. Thanks to every reader who helps us catch mistakes.
Correction log
Below are the substantive corrections this site has made, in reverse chronological order.
Where: Binance margin interest: how it's charged, section 2 and the FAQ answers "How is Binance margin interest calculated?" and "How do I pay less margin interest?"
Before: "anything under an hour is usually rounded up to a full hour … even a few minutes of borrowing may count as one full interest hour."
Changed to: a new loan's first interest charge is prorated by the second up to the next hourly settlement; after that a full hour is charged at each hour mark, an hour already entered is due even if you repay within it, the first charge is non-refundable, and interest is rounded up to 8 decimal places. What a short-term borrower should watch is whether the loan crosses an hour mark.
Why: Binance's announcement of April 30, 2026 switched new margin loans to a prorated first period from 08:00 UTC that day, and its margin interest FAQ describes the hourly settlement, non-refundable charges and rounding. Our text predated the change; we re-read both pages on November 4, 2026.
Where: are there deposit fees (description, section 2 heading and the note from the official pages) and what each funding rail really costs (section 4 heading and the paragraph under it).
Before: "P2P has no platform fee but a spread" and "P2P: no platform fee, the price is in the quote."
Changed to: the "no fee" applies to buying from a merchant's ad in the P2P Trade Zone, which carried a 0% taker fee in 111 of the 112 fiat currencies on Binance's P2P fee page on October 3, 2026. Express charged takers a fee in 92 of them, and posting your own ad often carries a maker fee. Both pages now say which route the "no fee" covers.
Why: our fees guide already said the P2P fee table is not zero everywhere, while these two pages read as if no P2P route ever carried a fee.
Where: BNB fee deduction: how to turn it on and what it saves, section 3 and the FAQ answer "How do I turn on the BNB discount?"
Before: section 3 said the toggle is "usually on by default" and placed it only roughly, in "the account-level 'fees' or trading-settings area"; the FAQ answer said "often on by default" and "Location per the current interface."
Changed to: you switch it on yourself. Web: [Fee Level] on a spot trading page, toggle [BNB/USDT], or the button under [BNB Discount] on the Fees & Transactions Overview page. App: [Account Center] → [Settings] → [BNB Discount] → [Use BNB to pay fees], or [Trade] – [Spot] → [...] – [Fee]. The title now uses "BNB fee deduction", the name the setting goes by.
Why: Binance's help article on using BNB to pay for fees (updated February 6, 2026, re-read October 3, 2026) says you must have BNB in your Spot Account and enable [Using BNB Deduction] first. Nothing on that page says the setting starts switched on.
Where: the Binance fees guide: the FAQ answer "Are Binance fees fixed?" and the opening paragraph.
Before: the FAQ said fees "shift with your VIP tier, whether you pay with BNB, and whether a code is bound"; the opening called the fee "a rate that shifts with who you are" and said the difference "comes down to whether you've turned on the BNB discount, bound a referral code, and which VIP tier you've reached."
Changed to: the rate moves with the VIP tier and with paying in BNB. A referral code leaves the rate unchanged; an eligible user gets part of the fee actually paid credited back afterwards. The opening now starts with the figures (0.1% maker and taker on spot for a regular account, 0.075% in BNB; 0.02% / 0.05% on USDⓈ-M futures, checked October 3, 2026) and says where to look up your own tier.
Why: Correction #12 (2026-09-25) already said the rebate is paid after the fee is charged and the rate itself does not move. This FAQ answer and the opening were missed at the time, and they contradicted the Chinese edition of the same guide and our sign-up tutorial.
Where: Binance VIP tiers and fee rates, the VIP Tier Threshold Calculator, the Binance fees guide, cutting costs on large trades, fee rebates, fee coupons and promos, the complete BNB fee-discount guide and the Binance fee-saving checklist.
Before: after Correction #13 went up earlier the same day, the VIP article said "Binance decides your VIP tier by two things, and you need both", "If your real trading comes nowhere near it, VIP1 isn't in play, and no amount of BNB changes that" and "holding BNB alone doesn't lift your tier"; the BNB discount guide said "every VIP tier asks for a BNB balance on top of its volume threshold, and both have to be met; the balance alone does not lift a tier"; the large-trades article said "A Binance VIP tier needs both trailing 30-day volume and a BNB balance"; the fees guide, the coupons article and the checklist said a tier comes once your 30-day volume and BNB balance both meet its thresholds; the tool's description said "A VIP tier needs both."
Changed to: Binance has several VIP tracks and meeting any one of them qualifies. For VIP 1: Trader (30-day spot volume of at least 1,000,000 USD, or futures volume of at least 5,000,000 USD), Holder (at least 100,000 USD in assets, 30-day average or previous day) and Borrower (at least 100,000 USD average borrowing over 30 days). Each of the three also needs a 5 BNB minimum daily average balance. There is also an Options fast-track and an Invitation programme. So the BNB balance still cannot replace trading volume, but trading volume is not the only way in: the Holder track looks at account assets. The VIP article's sections 2, 4 and 7 and two FAQ answers were rewritten, its threshold table now follows the columns on Binance's VIP page, and the daily update time (08:00 UTC) is stated. The tool's logic is unchanged; its text now says it checks the Trader track only and points to the Holder track. The other pages carry a shorter version of the same rule.
Why: Correction #13 was wrong on this point. The same day we re-read Binance's VIP page and its blog post "What Is the Binance VIP Program?": there are Trader, Holder and Borrower tracks, any one qualifies, and each also requires a BNB balance. Correction #13 described only the Trader track, taken from the fee table, and made trading volume sound mandatory.
Where: Binance VIP tiers and fee rates, the VIP Tier Threshold Calculator, the Binance fees guide, cutting costs on large trades, fee rebates, fee coupons and promos, the complete BNB fee-discount guide and the Binance fee-saving checklist.
Before: the large-trades article said "Binance's VIP tier is set jointly by trailing 30-day volume and BNB holdings — meet either to move up"; the VIP article said a tier could be propped up by holding enough BNB and that spot and futures tiers are maintained separately; the BNB discount guide said "a large enough holding can prop up your VIP tier too"; the tool applied "meeting either is enough" and its default VIP1 BNB threshold was 25.
Changed to: from VIP 1 up, a tier needs both the trailing 30-day volume and the BNB balance; holding BNB alone does not lift a tier. Spot VIP 1 is at least 1,000,000 USD of 30-day volume and at least 5 BNB; USDⓈ-M futures VIP 1 is 5,000,000 USD and 5 BNB. Spot and futures volumes are counted per table against different thresholds, but the VIP fees you earn apply across Binance products. The tool now requires both, with defaults of 1,000,000 USD and 5 BNB. The VIP article's trend sketch was replaced with the figures on the official tables, including that the spot VIP 1 taker rate stays at 0.100% and only the maker rate drops to 0.090%. The worked example in section 8 of the VIP article was recalculated from the official table (an all-taker trader saves nothing by reaching VIP 1), and one FAQ answer was rewritten in full. The BNB discount guide's line now says both requirements have to be met.
Why: re-reading Binance's official spot and USDⓈ-M futures fee tables on 2026-09-30, every VIP row prints "and" between the volume and the BNB balance; only the Regular User row prints "or". Above the table Binance states: "VIP fees and benefits gained from any VIP program will apply universally to all Binance products." The old text applied the "or" to every tier. The fees guide was re-checked against the spot, futures and P2P tables the same day. The "both are required" and "holding BNB alone does not lift a tier" wording in this entry was itself corrected the same day; see Correction #14.
Where: the home page, the sign-up tutorial, the referral rebate explainer, binding a referral code at sign-up, how to check your real fees and the real fee audit tool, plus the same wording on a handful of other pages.
Before: the tutorial was titled "from sign-up to your fee discount kicking in" and its last step said the effective rate "should read lower than the plain VIP0 baseline"; the binding article said every later trade "runs at a discounted rate" and the rebate "shows up as a lower rate"; the fee check and the audit tool treated the rebate as something that lowers the fee deducted on a trade; the home page said the two switches "cut fees on the spot"; and the country-availability FAQ told readers to "check the discount shown on your own fee page".
Changed to: the referral rebate is described as money returned after the fee is charged, with the fee rate itself unchanged. The tutorial's last step now checks two places: the trade history for the BNB discount, and the wallet history for rebate credits. The audit tool now reads only the BNB discount and VIP tier. The BNB discount is still called a discount.
Why: "discount" suggests you are charged less at order time, which sends readers to the fee table looking for a change that never comes. The site's Chinese-language piece on checking whether a rebate has arrived already said the rate table does not move; these pages had not caught up. Source: Binance Help Center FAQ on the referral programme — rebates are calculated hourly, converted to USDC and paid to the spot wallet within six hours (checked July 2026). The cover images, which carried the old wording, were redrawn the same day.
Where: the mini ledger for the cost stacking comparator on the home page.
Before: $100 base fee, BNB discount −$25, referral rebate −$20, total saved $45.
Changed to: the rebate is taken on the $75 left after the BNB discount, so 20% is −$15 and the total saved is $40.
Why: the home page applied the rebate to the full $100, which disagreed with the worked example in the sign-up guide and with the comparator itself (BNB discount first, rebate on what is actually paid). The figures remain assumptions; 20% is a ceiling, and the sign-up page and your account decide the real number.
Where: section 4 “How to bind” of Binance referral rebate: where the 20% comes from (the list of conditions and the paragraph after it), the verification note, the second myth in the myths list, and the FAQ answer “Can existing users still bind a code?” (page text and structured data).
Before: three hurdles — “the account has never traded”, “no other referral relationship was ever bound”, and “sometimes a registration-age limit” — plus “you usually can't switch”; the FAQ said “sometimes a registration-age limit. Accounts that have traded mostly can't bind.”
Changed to: day 30 after sign-up is a hard cut-off, on a par with no trades and no existing referrer; a deposit counts too; the other three conditions are a parent account, KYC details unused elsewhere for 180 days, and no wash-trader flag; a referral relationship cannot be changed or removed once set; the place to do it is the Bind Referral Pro Code page.
Why: the same mistake as Correction #9 — the sign-up window was treated as occasional and the no-deposit condition was missing. Once the late-binding article was fixed, this explainer still said otherwise, so the two pages disagreed. Sources as in #9.
Where: signed up without a referral code — can you add one later?: the opening answer, the self-triage table, the list of conditions, the section on where to bind, the pitfalls list, the closing check-up note and the FAQ (in the page text and in its structured data).
Before: “whether you can add a code later hinges not on how long ago you signed up, but on whether you’ve traded”; three conditions (no earlier referral, no trades, still inside a time window); “look in your account’s Referral pages” for the entry point; and “usually not” for accounts that have already traded.
Changed to: the six conditions Binance lists, all of which must hold: registered within 30 days, no deposit or trading activity, no existing referral relationship, a parent account, KYC details not used on another account in the past 180 days, and not flagged as a wash trader; the Bind Referral Pro Code page (binance.com/en/activity/referral/bind-ref, login required) as the place to do it; a flat “no” once the account has traded or been funded; and the note that a referral relationship cannot be changed or removed once set.
Why: the first version treated the 30-day window as secondary and left out the no-deposit condition, so a reader could have funded the account first, or waited months, and then found the door closed. Source: Binance Help Center, “Frequently Asked Questions on Binance Referral Pro Mode”, questions 4, 6 and 7 (updated 2026-08-05), read on 2026-09-24; the bind page’s address and title were checked in a browser the same day without logging in. The same day, the two late-binding notes in the sign-up walkthrough were made specific as well.
Where: the third item of “Four things people misread” in identifying an unfamiliar charge.
Before: “Divide the shortfall by the trade value; if it matches your rate, it is normal.”
Changed to: “Divide the shortfall by the quantity filled (the quantity you ordered, on a fully filled order); if the result is the order of magnitude of your rate, it is normal,” with a link to the article that sets out which asset each case is charged in.
Why: on a spot buy the shortfall is a quantity of the coin bought, while the trade value is an amount of the quote asset, so dividing one by the other does not return a rate at all. The correct denominator is the quantity filled, which equals the ordered quantity only when the order fills in full. Spotted while writing the article on which asset a fee is charged in; the rule itself is stated on the Binance help page “How to Calculate Binance Spot Trading Fees?”, read on 2026-09-16.
Where: the “At sign-up, where the code goes” section of binding a referral code at sign-up — its three bullets and the callout under them, the closing check-up note, and one FAQ answer (both in the page text and in the page's structured data).
Before: the code was described as a field on the sign-up form — “the sign-up page often has a Referral code or Referral ID field,” “sometimes the field is collapsed by default and you open optional to see it,” “glance at the referral field before you submit.”
Changed to: the first sign-up screen takes only an email address or phone number and carries no referral field; the code comes at the step right after the account is created, where the flow asks whether you have an inviter. Arriving through a referral link it is pre-filled and shown with a green tick and “Bound,” an invalid code can still be changed there, the step can be skipped if you don't have one, and once the code is bound it can no longer be edited. The three bullets, the callout, the check-up note and the FAQ answer were rewritten to match.
Why: this site tested the accounts.binance.com sign-up page in a browser on 2026-09-08 and read the two Binance Help Center walkthroughs, “How to Register on the Binance Website?” and “How to Register on the Binance App?”; none of the three shows a referral field on the sign-up form. This is a different article from the sign-up tutorial corrected earlier the same day, so it is logged separately. The old wording sent readers hunting for a box that isn't there, and a missing box could read as a code that had failed to bind.
Where: the sentences about where the referral code goes in steps 1, 2 and 3 of the sign-up tutorial, the second row of its six-step table, the closing check-up note, and one FAQ answer.
Before: the referral code was described as a field on the sign-up form — “the sign-up form usually shows a Referral code or Referral ID field,” “sometimes tucked under optional or more options, expand that section,” “make sure the field reads BN6987 before you submit.”
Changed to: the first sign-up screen has only an email/phone box and no code field; the referral code appears at the step after the account is created, pre-filled from the referral link with a green tick and “Bound,” editable if invalid, skippable if absent, and locked once bound. Each sentence was rewritten to match; the “expand the optional section” item became “editable until bound, locked after”; the table row and the check-up note were updated in step.
Why: this site tested the accounts.binance.com sign-up page in a browser on 2026-09-08 and compared it with the Help Center pages “How to Register on the Binance Website?” (Binance marks it updated on 2025-11-24) and “How to Register on the Binance App?” (updated on 2025-11-23); all three agree that the sign-up form has no referral code field. The old wording sent readers hunting for a box that does not exist, and could make them think a missing box meant the code had not bound.
Where: the worked example tables in the sign-up tutorial and the fees guide.
Before: the "up to 20%" referral rebate was applied to the $10 sticker fee (−$2, net $5.5).
Changed to: the rebate is applied to the $7.5 actually paid after the BNB discount (about −$1.5, net about $6, roughly six-tenths of sticker), and the table now says the rebate is credited afterwards rather than taken off at order time.
Why: the rebate is calculated on the fee you actually pay; discount first, rebate after — they are not two separate cuts off the sticker price.
Where: the "From our own check" notes at the end of several articles, and the origin story on About.
Before: those notes described checking Binance's official pages line by line as if we had operated a live account — for example "we pulled a stretch of spot fills and backed out the rate," "we tested Post Only," "KYC review came back without drama."
Changed to: the notes now say only what the official pages state and what our judgment is, and make clear no live account was used; the conclusions, rate wording and risk warnings of each article are unchanged.
Why: this site has no publishable record of live-account operations. Writing a check-up as a hands-on run makes readers overestimate the strength of the evidence; accuracy comes before vividness.
Where: the spot-rate section of the complete Binance fee guide.
Before: the first draft wrote the spot taker rate as a single fixed number (a precise value presented as permanent), giving the impression that "this is the permanent rate."
Changed to: a range expression on the order of "around 0.1%," with the note added that it follows "whatever Binance's official fee page currently shows, verified June 2026."
Why: Binance adjusts rates with policy and VIP structure, and treating one moment's precise figure as fixed can mislead readers after the rate changes.
Where: the futures-fee section of the complete Binance fee guide.
Before: the first draft explained futures fees without stating the charging base, which could lead readers to assume they're charged "on margin" or "on the same basis as spot."
Changed to: added the key clarification — futures fees are charged on the notional value of the position; with leverage the notional is amplified, and the fee is charged on the amplified figure — plus a note that this is the thing new traders most often miss.
Why: the charging base directly affects how readers estimate futures cost, and leaving it out makes people badly underestimate the real fee.
Where: the withdrawal-cost section of the complete Binance fee guide.
Before: the first draft described the withdrawal fee as though it's "charged as a percentage of the withdrawal amount," which is easy to misread.
Changed to: corrected to say the withdrawal fee is mainly set by the blockchain network you choose and is largely unrelated to the amount; the same coin can differ severalfold across networks, with a reminder to confirm the receiving side supports the network before picking one.
Why: the way withdrawal fees are charged (by network, not by amount) is where an ordinary user can save the most and slip up the most, and the original description would have directly misled withdrawal choices.
Whenever there's a further substantive correction, we'll add it here. You can also learn our editorial principles on about us, and the "rates per official pages" stance in the disclaimer.