How Paylark guides are written and checked

Choosing what to write

We start from questions people ask at the moment they’re being paid: in forums, in search results and in the messages clients send. A topic earns a guide if the answer is hard to find in one place or is usually answered badly. Whether a topic has anything to do with our referral code doesn’t come into it. Most guides don’t mention an exchange at all.

Sources that count

• Official pages first. For how an exchange feature works, what it costs or what it requires, the source is the exchange’s own help centre, fee page or terms.
• Public records for anything on a blockchain. Transaction behaviour is checked against public block explorers and the network’s own documentation.
• Government and consumer-protection pages for scams and warnings.

We don’t treat social media posts, videos or other guide sites as sources of fact.

How checking works

Each guide carries a short note saying which pages it relies on and the month they were last opened and read. If we couldn’t open a page, or a detail isn’t published, the guide says so instead of guessing. We don’t state fees, limits or processing times as fixed numbers. We give the formula and the typical range, and point to where the live figure is.

We haven’t logged into anyone’s account to write these guides, and we don’t claim success rates or personal results. Where a guide describes a screen, it’s the public version of that screen or the platform’s own published instructions.

Worked examples

Examples use round, invented numbers so the arithmetic is easy to follow. Every example is recalculated before publishing, and the inputs are shown so you can redo it with your own figures.

The referral code and editorial independence

Referral links appear on two pages only (the home page and the sign-up guide), and the code is shown there and nowhere as a banner. No guide is written, changed or removed because of commission. See the disclosure page.

Corrections

When something is wrong, we fix the sentence itself rather than adding a note underneath, update the page’s “updated” date, and log the change on the corrections page with the date and what changed.