Who owns which step
The account side comes first, and it is the side that stopped. ACBuy and AllChinaBuy are two names for the same operator, and both now sit in the closed column on the platform ledger. Both names appear on the same row of that ledger, which matters when you are searching for a support channel. Whatever a balance was — credit from a cancelled order, an unspent top-up, a refund that was approved but never landed — the obligation starts there. Nothing on this page holds money, and no tool here can move any.
Second comes the route the money travelled. A card, a bank transfer, a wallet and an in-app payment each carry their own rules, and the deadlines attached to them are set by whoever provided that route. This site does not verify those terms and cannot state them accurately, so treat any specific window you read anywhere as belonging to the provider until that provider confirms it in writing for your case. Ask that provider what its own limit is, in writing, for the specific payment you made.
Third comes the service you move to next. An agent that accepts your remaining item, or the link that identifies it, becomes a new counterparty for shipping and storage. It does not inherit the old balance. Its terms describe its own fees and its own holding limits, and this site lists those terms as unverified for every service, including the eleven with object pages in the public directory. Ask what it will take before you ship anything to it, not after the parcel has landed.
Fourth comes you, because the record is the only part of the chain that never went offline. Steps one to three depend on organisations answering, and the measure of what you recover is not what you remember owing but what you can put in front of someone with a date attached. Nobody else is keeping a copy for you, and the organisations involved have already shown how long they keep answering. That ceiling is set on your side of the table, and it is the one part you can still raise.
Where to raise it
Start where the clock is shortest. The payment route carries the tightest limits in almost every case, so a request there should go out before a complaint to anyone else, even if the amount is small. Write it as a plain sequence: what you paid, when it was paid, what it was for, what you have already asked for, and what answer you received. Dates do the arguing for you; adjectives do not. Keep a copy of what you sent, because the reply often quotes only part of it.
The platform route is quieter than it was. The last dated statement this site holds from that side came around 2026-07-10, when a community representative said ordering had not been restored and gave no new date. A permanent closure was never announced, which is why the ledger still records names rather than a closing notice. Requests sent there have no stated response time, and silence is a possible outcome rather than a surprise. Record the date you sent it, and the date you stopped waiting.
The destination route is a fresh question rather than a continuation. Ask in writing whether the service accepts the item or the link, what it needs from you, and what it will not take. The platform ledger lists eleven objects with public pages, from Kakobuy to Sugargoo and the rest, and reading the page first tells you whether the question is worth sending at all. Keep the reply, whatever it says. A refusal in writing is still a useful document, because it closes that option cleanly.
Where a question has no answer yet, the open questions page is the honest place to leave it. That page exists because this site would rather show a blank than fill it with a guess, and it also keeps a running list of what buyers asked that nobody could close. It is also where a settled question gets closed rather than quietly dropped. If you have come across a document, a notice or a working channel that settles one of those items, the corrections page is how it gets recorded.
What to keep as evidence
A screenshot is worth keeping when the date is visible in it. Balances, order rows, refund entries and support replies all look different on different days, and a picture with no date attached invites an argument you cannot win. Capture the whole window rather than a cropped figure, and keep the original file. Dates inside a screenshot are the closest thing to a receipt that a browser session produces. Renaming everything into a tidy folder system feels productive and quietly destroys the sequence that makes the record useful.
Keep both halves of every address. The wrapped form you were given and the source form it rebuilds into belong in the same row, because the first shows where the hand-off started and the second is what still answers. Where an item has a sample identifier from a weekly snapshot, keep that too. A row that says 2026W39-014 and 7577045115 tells a stranger everything needed to test the claim without trusting you. The pair is what lets somebody else reproduce your check instead of taking your word for it.
Messages are evidence only in their original wording. Copy the text, note who sent it, and note the date it arrived, rather than summarising it into your own sentence. A paraphrase cannot be checked by anyone else, and a checkable record is the entire point. Copy the channel it came through as well, since the same words carry different weight in different places. If a representative said ordering had not returned, that sentence with a date is useful; your memory that things were still broken is not.
Build one row per claim and give it fixed fields: amount, date, what the payment was for, the reference you were given, the address that identifies the item, the channel you raised it through, the reply you received, and the date you last looked. Eight fields, filled honestly, will do more for you than a long narrative. The reason is simple: the fields can be compared against someone else's records, and the narrative cannot. Fill the last field even when nothing has changed, because a stale date reads like an abandoned claim.
The part nobody can recover
Time does not come back. Between the first notice on 2026-06-01 and the moment you read this, weeks passed that no refund will cover, and any reply that arrives later still arrives later. That is worth stating plainly because deadline panic usually pushes people into repeating the same request through five channels at once, which produces more waiting rather than less. One clear request per channel, dated and kept, outperforms volume. The weeks are gone whether or not the money comes back.
Session history behind a login is usually gone. This site never used an account or stored credentials during its checks, and it does not hold anything belonging to you, so the only copy of your own dashboard history is the one you made yourself. Payment records survive on the other side of the transaction, which is why they are the reconstruction route. If nothing was downloaded or photographed, the amounts, the approval notes and the order of events have to be rebuilt from those records instead, which is possible but thinner.
Photos are the quiet loss. A photo set that showed the item before it went into storage settles questions about condition that no later evidence can touch, and once the page stops answering there is no second chance to capture it. Anything you did not write down then has to be argued from memory now. That is why the QC scorecard is built around writing down what a set showed, item by item, with the date. A scorecard made in June would have been worth more than any follow-up sent in September.
Then there is the layer that failed. Thirty-one wrapped addresses from public sheet pages did not answer at all in the 2026-W39 window, while all thirty-one source addresses they encode answered normally. A balance story follows the same shape: the record in front of you may look dead while the thing behind it is intact. The rest is a matter of how completely things were written down at the time. What you cannot recover is the part that was never recorded, and that part is decided long before any window closes.