Unmasking the Fake Contractor Page That Took Andrei's Deposit

The situation

Andrei and Radu had known each other for nearly a decade, first as coworkers at a warehouse and later as neighbours in the same New Liskeard building, close enough that Andrei had lent Radu money twice over the years without much worry about getting it back on any particular schedule. When Radu moved away for work two years earlier, they stayed loosely in touch, and Andrei thought little of it when a local renovation business page started appearing in his social media feed, sharing photos of balcony and railing repairs around town.

Andrei worked as a gas station attendant and owned a small condominium unit with a balcony that needed structural repair work before the building's next inspection cycle. The page, presenting itself as a licensed local contractor, quoted him eighteen thousand dollars for the job, asked for half up front to secure materials and a start date, and provided what looked like a normal invoice and a business name Andrei did not recognize. He paid the nine-thousand-dollar deposit by e-transfer, since that matched the fifty percent up front the page asked for, and he had no reason at the time to question anything more than the invoice he was sent. The contractor never showed up on the agreed date, then stopped responding, then the page itself disappeared entirely.

Rizki, a factory technician who lived two floors down from Andrei, mentioned a few weeks later that he had paid a similar nine-thousand-dollar deposit to what sounded like the exact same page for a comparable repair, and had the same experience: a quote, an invoice, a deposit, then silence. Neither of them had a name to go on beyond the page's business branding and a profile photo that could have belonged to anyone.

It was only after comparing notes with Rizki that Andrei started to wonder, uneasily, whether the writing style in the page's messages, blunt and oddly specific about payment timing, reminded him of someone. He did not want to believe it, and he had no way to confirm it. What he had was a platform account with no visible real name attached to it, a missing eighteen thousand dollars between the two of them, and a growing suspicion he could not yet prove.

What the documents showed

Suing an anonymous social media account is not possible in any practical sense; a claim needs a real person or company as a defendant. The platform hosting the page knew who had created and operated the account, but platforms do not hand that information over on request, and privacy law generally prevents them from doing so voluntarily even when the request comes from someone with a legitimate grievance.

The tool that exists for exactly this situation is what is commonly called a Norwich order, named for the case that first recognized it, though we do not need the case name to explain what it does. It is a court order compelling a third party, here the platform, to disclose identifying information about someone it holds records on, where that third party is not itself accused of wrongdoing but happens to be the only source of information needed to identify who is. Courts do not grant these lightly. The applicant has to show a real, arguable claim against the unknown person, that the information genuinely cannot be obtained another way, and that the request is proportionate rather than a fishing expedition.

We had the arguable claim: a clear pattern of a business page taking deposits under false pretenses and disappearing, affecting at least two people with matching stories. What we needed to strengthen before applying was evidence that the platform's own records were genuinely necessary, since a court is far more willing to compel disclosure when simpler routes have already been exhausted and no other realistic path to an identity exists.

That is where an ordinary piece of paper mattered more than anything either of us expected. Rizki, going through his own records for the claim, found a receipt from a hardware supply store where he had once picked up materials on Radu's behalf years earlier, back when they were still on good terms and Radu asked him for a favour. The pickup slip listed a name and a phone number for verification, tying an identifiable name directly to the transaction. It was not proof on its own that Radu operated the fake page, but combined with the writing style Andrei had noticed and the timeline of when Radu had moved and when the page appeared, it gave us something no amount of platform records alone would have provided: a specific person to test the theory against, and a way to check the platform's eventual answer rather than simply trusting it.

What we did

1. Documented the scam pattern with corroborating evidence. Before pursuing any court order, we needed more than Andrei's word that this was a genuine fraud rather than a contractor who had simply fallen through. We gathered every message exchanged with the page, the e-transfer confirmations showing the deposit leaving Andrei's account, and Rizki's parallel account of the same experience, building a documented pattern rather than a single anecdote. That record became the foundation for the arguable claim a Norwich order requires.
2. Assessed the claim against the legal test before filing. A Norwich order is not granted automatically, so we worked through each element in advance: whether the claim against the unknown operator was genuinely arguable, whether the platform's records were truly the only practical way to identify them, and whether a request limited to one page's registration information was proportionate rather than a broad fishing expedition. Confirming all three in advance meant we were not filing speculatively.
3. Prepared and filed the application against the platform. We drafted the application narrowly, seeking only the registration details tied to the specific page rather than any wider account history, since an overbroad request invites opposition and delay. The platform reviewed the material, was satisfied the legal threshold was met, and did not oppose the application, which let the court grant the order without a contested hearing.
4. Investigated the hardware store receipt independently. While the platform application moved through the court, we followed up on the pickup slip Rizki had found, contacting the store directly to confirm through its own records that the name and phone number on the slip matched Radu's. Doing this before the platform's disclosure arrived meant we would have an independent way to test whatever the platform eventually produced, rather than taking a single source at face value.
5. Compared the platform's disclosure against the independent lead. When the order was complied with, the registration details, an email address and phone number, traced to Radu, matching what the receipt had already suggested. Having two independent sources point to the same person, rather than relying on the platform's records alone, gave the identification real weight and meant Radu had little room to dispute who was being accused.
6. Sent a formal demand and pursued a negotiated resolution. We wrote to Radu directly, laying out the evidence, the pattern involving both Andrei and Rizki, and the platform disclosure, and gave him a deadline to respond. Given the uncertainty over where he was living and what he owned, we judged that a contested court process risked ending in a judgment that could not actually be collected, so once he responded we moved straight into settlement discussions aimed at a repayment plan he could realistically keep to.

The outcome

Radu did not admit to running the page outright, but he agreed to a repayment plan covering roughly two-thirds of what he and Rizki had lost between them, paid in installments over a year rather than as a lump sum. The remaining balance was written off as part of the settlement rather than pursued further, since a judgment against someone with limited and uncertain assets carries real value only if it can actually be collected.

The friendship between Andrei and Radu did not survive the episode, and Andrei was candid that the hardest part was not the money but realizing someone he had trusted for a decade had targeted him and his neighbour deliberately. The balcony repair itself was eventually completed by a different, verified contractor, at a cost close to the original quote.

What made this case work despite the modest amount at stake was that the cost of identifying Radu never became disproportionate to what was recoverable. Narrowing the platform application to a single page's registration information, and pairing it with independent verification through the hardware store receipt, kept the process efficient enough that pursuing a claim in this range still made practical sense. A broader, more contested application against the platform, chasing every record it held rather than one specific account, would likely have cost more in time and legal fees than either Andrei or Rizki stood to recover.

Andrei and Rizki both now insist on verifying any contractor's business registration directly with the province before paying a deposit, rather than relying on how established a social media page looks. Andrei has also mentioned the case to two other neighbours in the building since, both of whom now do the same check before hiring anyone found online.

What you can learn from this