Preserve each demand
Keep the wording, sender details, payment instructions, and dates of each request.
A platform may describe another payment as a tax, verification charge, or release requirement. We help you organize those demands alongside the original transfers and prepare a clear account of the incident.
Get started
A thoughtful approach. A clear next step.Keep the wording, sender details, payment instructions, and dates of each request.
Link receipts and transaction references to the demands that prompted them.
Explain how the requests developed and which channels were used to communicate.
Start with the information you already have. A short timeline and a few relevant records can make the first conversation more productive.
Clear records begin with the right network, wallet address, and transaction reference. Keep these details with your account of what happened.
Start a case reviewLogos identify the assets discussed. They do not imply an affiliation with, or endorsement by, a network.
No. The available options depend on the transaction, the evidence, the recipient, and the institutions involved. A review can clarify possible steps, but it cannot promise that funds will be returned.
There is no single timetable. The complexity of the incident and the response of banks, platforms, and other parties affect the process. Keep a record of responses and any deadlines they give you.
No. Do not share passwords, authentication codes, private keys, or seed phrases. Public transaction references and relevant records are different from the credentials used to control an account.

When a payment goes to the wrong place, understanding the transaction is the first step.
Explore service
A missing pet, a fictitious carrier, and repeated delivery charges can leave you unsure where to turn.
Explore service
Unfamiliar requests, pressure to act quickly, and unexpected account changes deserve a closer look.
Explore serviceExplore your account options, or reach out for help with a financial concern.