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.
Correction #8 · 2026-09-16 — Identifying an unfamiliar charge: the buy-side fee check divided by the wrong figure
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 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.
Correction #7 · 2026-09-09 — Binding a referral code at sign-up: the code step was described in the wrong place
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 “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.
Correction #6 · 2026-09-09 — Registration guide: the referral code step was described in the wrong place
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 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.
Correction #5 · 2026-09-06
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 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.
Correction #4 · 2026-09-05
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 "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.
Correction #1 · 2026-06-28
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 hard-coded precise value), 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 spot-rate section of the complete Binance fee guide.
Before: the first draft wrote the spot taker rate as a single fixed number (a hard-coded precise value), 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.
Correction #2 · 2026-06-28
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 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.
Correction #3 · 2026-06-28
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.
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.