We'd rather list our mistakes here than let a reader run into one first. This page logs factual errors we caught in KashRail guides, what was wrong, and what we changed. The July entries came out of our own pre-publication review — editors rechecking each other's drafts against the live Binance and OKX interfaces before the site went live. The September ones came from a recheck of published guides against Binance's own fee schedule and help pages, which is the sort of thing that has to happen periodically rather than once. Reader reports, when they come, get logged here in the same format rather than quietly folded into an edit.
September 2026
Late referral binding and the futures exception, corrected again. Our 16 September fix below overshot. It said a missed Binance code could never be added after signup, apart from a futures referral code entered before opening a futures account. Binance's Referral Pro FAQ says otherwise on both points: a new account can still bind a missed code within 30 days of registration if it has had no deposit or trading activity and meets the other listed conditions, and a futures referral code cannot be used to activate a futures account on an account that was not registered with a Referral Pro code. We rewrote the guide, the matching section of the referral code guide, and the shorter mentions elsewhere on the site. Fixed 24 September 2026.
M-PESA option outside P2P no longer stated as fact. Our July entry below, and the guides it describes, stated that Binance opened a direct M-PESA channel for Kenyan users in January 2026, trading against Binance's own liquidity. On a recheck we could not find an official Binance announcement or help page to support the date, the counterparty or the payment flow. We rewrote the M-PESA guide, the Kenya legal status guide and the shorter mentions elsewhere to treat a Buy Crypto option with M-PESA as something to check in your own app, not a confirmed feature. Fixed 24 September 2026.
Referral codes described as addable after signup. The forgot-a-referral-code guide said a code could be bound to an account retroactively within a window of "months rather than days" for a mostly inactive account, and the referral code guide repeated it. Binance's referral rules say the opposite: the code goes in at registration, and where it was forgotten or entered incorrectly the commission cannot be collected. The only later entry point is on the futures side, before a futures account is opened. We rewrote the guide and the corresponding section of the referral code guide around the actual rule. Fixed 16 September 2026.
Spot trading fee described as a low single-digit percentage. The fees guide avoided naming a figure and described the base spot rate in a range an order of magnitude above the real one. Binance's Regular tier is 0.100% for both maker and taker, 0.075% with the BNB discount. We replaced the vague range with the dated figures and a note about when to recheck them. The same guide also said maker fees are typically lower than taker fees; at the Regular tier they are identical, and a lower maker rate belongs to the higher VIP tiers or specific pairs and promotions. Both the body and the FAQ were corrected. Fixed 16 September 2026.
KYC country selection explained as one field instead of two. The KYC documents guide told readers to select the country matching the document they were submitting rather than where they live. Verification actually asks separately for residence and for the document's issuing country — residence has to be truthful, and treating it as a choice is itself a cause of rejection. We rewrote that section, and added Binance's published review time (usually within 48 hours, longer in some cases) alongside our own experience of it. Fixed 16 September 2026.
P2P release described as an on-chain transaction. The payment reversal guide said releasing crypto settles on a public ledger. A P2P release is an internal transfer on the exchange's books; only a withdrawal to an outside address goes on-chain. The practical point for a seller is unchanged, but the mechanism was wrong, and we corrected it. Fixed 16 September 2026.
July 2026
M-PESA direct channel described as P2P-only. An early draft of the M-PESA guide treated Binance's M-PESA support as if it only ran through P2P merchants, the same as bKash or JazzCash. That was incomplete: Binance opened a direct M-PESA deposit and withdrawal channel for Kenyan users in January 2026, which sits alongside P2P rather than replacing it. We rewrote the relevant section of the M-PESA guide to cover both routes and explain when one makes more sense than the other. Fixed mid-July 2026.
EasyPaisa limits quoted from an outdated tier. The first version of the EasyPaisa guide gave a single fixed transaction limit that turned out to reflect an older EasyPaisa account tier, not the current range across account types. We corrected the guide to describe limits as a range tied to account tier and verification level, with a note pointing readers to the EasyPaisa app for the figure that actually applies to their account, since these tiers are set by the wallet provider and change independently of Binance. Fixed mid-July 2026.
OKX KYC document list misstated for the Binance-alternatives guide. The guide covering what to do after repeated Binance KYC rejections originally listed OKX's accepted ID documents based on assumptions carried over from the Binance KYC guide rather than OKX's own requirements. After checking OKX's published verification page directly, we corrected the document list in that guide to match what OKX actually asks for. Fixed mid-July 2026.
If you spot something else that looks wrong on any guide, the fastest way to flag it is through the contact page — see that page for what we can and can't act on.
How we catch these
The July three didn't come from a reader report or from months of the site being live — it hasn't been live long enough for either. They came out of our pre-publication check: before a guide went out, a second editor read it against the actual Binance or OKX interface instead of trusting the first draft, looking specifically for claims that had shifted, been assumed rather than verified, or gotten carried over from a similar guide without a recheck. That's how the M-PESA channel gap, the EasyPaisa tier mismatch, and the OKX document list all got caught before anything went live. The September batch is the other half of that habit: not reader reports, but a recheck of guides that had already been published, read against Binance's own fee schedule and help pages rather than against our earlier drafts. Reader reports, when they arrive, get described the same plain way.
We don't quietly edit a guide and pretend the earlier version never existed. If a correction changes something a reader might act on — a limit, a step order, a document requirement — it gets logged here with when it was caught, whether that's before publication or after.