Corrections Record
This page logs the places we've changed. Fix what's wrong, and put the change in the open—that's what we think a content site should look like.
01Why we log corrections openly
Nobody can promise never to be wrong, especially writing about fees and policy—things that change constantly. What sets sites apart is what they do afterward. Our approach: when we find a problem, we fix it, and once fixed, we note "what it said before, what it says now" on this page.
There are two reasons. One is accountability to readers—you have a right to know the version you saw earlier may have been off. The other is that putting corrections in plain sight is itself a constraint, pushing us to be more careful before writing and to check seriously after feedback. Below are the corrections from the site's early run.
02Correction entries
Before: an account-opening article wrote a hard number for a monthly account fee.
Now: changed to "go by the official page at the time," with a note of roughly when we checked the fee. The reason is that platforms adjust these charges, a hard number dates quickly and can mislead, and pointing readers to where to verify is steadier.
Before: one spot described the validity of a HK/Macau permit endorsement too absolutely, reading as if every case were the same.
Now: rephrased more cautiously, noting that endorsement types and validity vary from person to person, that the immigration authority's rules govern, and asking readers to confirm against their own document.
Before: in a few early articles, the wording for the referral code wasn't quite consistent—some said "use our code," with slight variations elsewhere.
Now: standardized site-wide to "through our referral code," consistent in wording and less open to misreading. The code itself (Binance BNTIKTOK) hasn't changed.
Before: "Monzo vs Revolut: Opening a UK Digital Bank" put the FSCS deposit protection limit at roughly £85,000 per person.
Now: updated to the figure in force—since 1 December 2025 the limit is £120,000 per eligible person, per bank. We checked it against the FSCS's own page before making the change.
Before: "How to Open a Hong Kong Bank Account" and a few other places said you could open ZA Bank remotely and that "there's no need to fly over specially," and that Mox was the one that effectively required a Hong Kong ID card.
Now: rewritten against ZA Bank's and Mox's own account-opening eligibility pages—both of their published paths require you to be in Hong Kong at the time of opening, so being able to submit in the app doesn't mean you can finish the application from elsewhere. Mox doesn't only accept a Hong Kong ID either: it leaves a visitor path open to holders of a Mainland resident ID card, except that its site says this is currently by invitation only, and after opening you have to transfer money in under your own name before some limits lift. We also fixed the same claim on the home page card, in "Mox vs WeLab" and in the card checklist tool.
Before: in the safety section of "Funding Binance from a Hong Kong card," the instruction "confirm the money arrived, then release the coins" was written as if it were the buyer's job.
Now: releasing the coins is the seller's move. The buyer has three steps only—pay, tap "Paid", and wait for release. If you've paid and the seller still hasn't released, keep the order and your transfer receipt and raise a dispute; don't cancel the order.
03Spot an error? Tell us
If you read something that seems off—a figure out of date, a flow changed, an ambiguous claim—you're welcome to write. Include the article link and what you're going on, and once we've checked, we'll correct it; the important changes go into this page too. Address: [email protected].
This page logs only content-level corrections (fees, flows, claims and the like), not typos or minor layout tweaks—so the corrections that matter don't get buried.