Checked on, and what this guide does with a disagreement

Each figure below is stamped with where it came from and when it was last looked at. When two official pages contradict each other, both stay on the page.

The notices themselves

Reading dates by topic

Also emitted as /content-freshness.json, so the record can be diffed rather than read.
Claim	Where it came from	Read on	Stale after
Stock display mismatch	Notice 1775413756723527681	2026-10-14	180 days
Out-of-stock handling and the reply window	Operator help centre	2026-10-10	90 days
Refund destination and withdrawal	Operator help centre	2026-10-10	90 days
Return window and ineligibility list	Notice 1740656181012172801	2026-10-14	90 days
Storage periods	Notice 1740664252140720130	2026-10-10	90 days
Fee composition	Notice 1740653781924810754	2026-10-14	60 days
Prohibited and counterfeit policy	Notice 1772880724846247937	2026-10-10	180 days
Operating entity	Notice 1798905530716098562	2026-10-10	365 days
Interface captures	Operator site	2026-10-10	180 days
Every outbound address	Fetched one by one	2026-10-13	90 days

Short windows go on the things that move. Fee tables and campaign values move fastest, which is why no campaign value is printed here at all.

Where the operator's pages disagree with themselves

The dated captures contain top-up and service-fee differences. The 14 October 2026 recheck also found that the current returns notice describes a bank-refund estimate different from the older help answer’s finance-processing estimate. These need context rather than a single chosen number.

Read 2026-10-10.
Subject	First published figure	Second published figure	What this site does
Top-up surcharge on the wallet route	4.5 per cent plus a fixed charge, on the top-up page	Approximately 3.7 per cent plus the same fixed charge, in an older help answer	Neither is quoted as settled; the figure shown at payment is the one to trust
Service fee in the registration agreement	The published formula names no agent commission	A percentage appears in a registration agreement of the kind used across this sort of service	The fee formula is described with its source date; check the agreement and current checkout rather than treating either as a guaranteed total.

Why a figure in an agreement is not a price

Published pages can conflict. This site does not dismiss a contractual term merely because it resembles a template. Compare the current agreement with the checkout charge and ask the operator to clarify an unresolved difference before payment.

Official announcements and campaigns

The official site displays changing announcements and campaigns. Check dates, account eligibility, minimum spend, route restrictions and whether a coupon covers product cost or shipping before applying it. Historical interface captures illustrate a task and do not offer the prices or promotions shown in them.

Dates and source scope matter for every policy. The current review rechecked stock-display mismatch, fee composition, inspection and returns through the official API; other historical facts retain their 10 October capture date.

Community feedback, and the one question it answers well

The operator runs its own channels, and shoppers also talk on Reddit, YouTube and TikTok. There is exactly one question those places answer better than any published page: whether this is happening to other people right now.

What community reports are good for

Noticing that a particular shop has stopped answering
Finding a sibling listing when one dies
Seeing how long a route is actually taking this month

What they cannot settle

Whether a listing is in stock, which only the seller's own reply settles
The length of any published window, because recollection drifts and the notice does not
Whether an operator's policy has changed, which the notice index answers directly

So a thread is a timing signal. For anything about what the rules actually say, the notice index settles it faster than reading the replies.

Revision log

Newest first. Each entry is a change to this site, not to the operator's rules.
When	What moved
2026-10-14	Local revision: five-module homepage, full buying guide, conditional link triage and corrected breadcrumbs. Rechecked official stock, fees, inspection and returns text. Recorded the different refund-processing contexts.
2026-10-13	Initial guide draft. Link states, reply handling, refund route, storage and fee formula were recorded from dated notices.
2026-10-13	Two different top-up percentages found; both kept, neither chosen.
2026-10-13	Historical interface captures retained as examples; live promotional terms must be checked on the official site.

Refund timing needs a channel and a starting event

The help answer captured on 10 October 2026 mentions 2–3 working days for finance processing of a withdrawal. The Returns and Refunds notice rechecked through the official API on 14 October 2026 describes an expected 7–15 days to a bank card after confirmation, depending on the bank. Neither establishes a universal timeline from the day a listing fails.

Check the refund destination and stage before choosing which description applies. All other retained policy captures keep their original reading date.