What to do after a crypto scam in Canada
Stop further payments, secure affected accounts and prepare a useful report. Start with what you sent or shared, then choose the right next step.
In this guide · 9 sections
- Identify what you sent or shared
- Contact the provider and secure affected access
- Address identity information that was exposed
- Save a private incident record
- Report to the right Canadian organizations
- Help a family member without taking over their account
- Follow up and handle an unresolved response
- Understand recovery limits before paying anyone
- Questions after a crypto scam
After a crypto scam in Canada, stop further payments and contact the bank or exchange involved through its official channel. The Canadian Anti Fraud Centre’s victim guidance calls for preserving records, contacting financial institutions and reporting to police. You do not need to finish a perfect evidence file before asking your provider for urgent help.
If a person is still directing you, end that conversation. Do not send another deposit to release a balance or prove that a wallet works. Your first task is to tell the genuine provider what has happened and ask what can still be protected. Identifying every person involved or proving the entire scheme can wait. A suspected loss and exposed account access may need attention at the same time.
Use this guide in that order: identify what you sent or shared, contact the relevant provider, preserve a private record and use the Canadian reporting routes. Later sections explain identity concerns, help from family and follow up when the outcome is unclear. Suggested wording and hypothetical examples are editorial aids, not official forms or accounts of real victims. Adapt them to what you actually know. No checklist can promise reimbursement, but an accurate account gives each organization a clearer problem to assess.
Identify what you sent or shared
The payment state and the exposed access determine your next step. Several rows can apply to the same incident.
| What happened | First action | Do not assume |
|---|---|---|
| A bank or exchange request is still pending | Ask the genuine provider whether it can stop or restrict the request | That a pending label guarantees cancellation |
| Crypto has left your wallet | Save the transaction details and contact your provider and police | That wallet support can reverse a completed transfer |
| You shared an exchange password or login code | Use the provider’s compromised account process | That changing only one password addresses every exposed account |
| You shared recovery words or a private key | Follow the wallet provider’s compromised wallet guidance | That changing the app password protects the exposed secret |
| You approved a suspicious wallet prompt | Review the specific permission through verified wallet guidance | That disconnecting the website revokes its spending access |
This is a decision aid, not a diagnosis of your transaction. If the facts are unclear, tell support exactly what you entered, signed or sent.
Separate the payment from the account display
Start with a record you control, such as the genuine bank or exchange account used to send money. Write down what it shows, including any status you cannot interpret. A suspicious investment site’s claim that a withdrawal is pending is a different piece of information. Preserve that claim, but ask the actual payment provider about its own transaction rather than treating the investment site’s label as the provider’s answer.
If the sequence involved a bank payment, a crypto purchase and a later transfer, describe those as separate events. Do not compress them into “the bank sent my investment.” That wording may leave out the point at which crypto moved to another destination. You can ask each provider to identify the transaction it handled without knowing whether it can help with the later transfer. Record uncertainty about the destination instead of guessing its owner.
Hypothetical example: A person buys crypto through an exchange, sends it to an address supplied in a chat and later sees a larger balance on another website. Their report should distinguish the money used for the purchase, the crypto sent onward and the website’s claimed balance. Those are different records. Adding all three together would describe the same funds more than once and include an unverified profit claim.
Describe access separately from missing money
A payment record cannot answer every account security question. Make a separate note of the accounts, devices or wallet permissions you believe were involved. Include what you did yourself and what you observed afterward. “I entered my password on a page reached through a message” is more useful than confidently naming a technical attack you have not identified. Keep the page address, if available, without opening it again to recreate the event.
If you do not know whether a wallet request was a transfer or a permission, say so. Preserve the wallet’s existing activity record and ask where to obtain verified help interpreting it. Do not sign another request as a demonstration. An unanswered technical question should stay visible in the report; it should not be silently converted into an assumption that either everything is safe or every account has been compromised.
Contact the provider and secure affected access
Ask your bank or exchange to check the actual payment status and explain its available fraud response. State whether you authorized the payment after being deceived or someone accessed the account without permission. These are different circumstances; report them accurately.
Open the app yourself or use a known official website. Do not use a support link supplied by the person who requested the payment.
Make the first contact short and specific
Lead with the concern and the action you need assessed. Explain which account is involved, whether money was sent and whether someone may still have access. Then provide the payment date, amount and reference you can confirm. If the provider asks a question you cannot answer, distinguish “I do not know” from “that did not happen.” You can supply a longer chronology after the urgent payment or access question has been addressed.
Suggested wording, written for this guide: “I suspect fraud involving my account. Please check the status of the payment I identify and tell me whether any action can still be taken. I also need help assessing the access I may have exposed. Please give me the incident reference and explain how to send supporting records securely.” This is a starting point for your own explanation, not a statement that a payment can be stopped.
Describe authorization honestly. If you pressed send because someone deceived you, say that. If you noticed a transfer you did not make, describe that instead. If both happened, separate them. Do not choose a description because someone online says it produces a better refund outcome. An accurate sequence lets the provider assess the circumstances rather than spending the conversation untangling conflicting versions of what happened.
Before ending the contact, clarify the next action. Ask whether the request has reached the appropriate team, what you should do about affected access and how to submit the remaining evidence. Note any instruction and its source. If you were told to wait, ask what you are waiting for and how to follow up. Do not assume an acknowledgment means a transfer has been blocked or a recovery has begun.
For an exposed exchange login: follow that provider’s security process promptly. For example, Coinbase offers an account lock that disables transfers and signs devices out. Other services have their own procedures. Tell support if email access, login codes or remote device access were also exposed; a password reset alone may not address those risks.
For an exposed recovery phrase: treat the wallet as compromised. MetaMask’s guidance describes creating a new wallet and discontinuing accounts tied to the compromised phrase. It warns against adding funds for network fees when an automated sweeper may be present. Do not improvise a rescue by sending more crypto into the exposed wallet.
For a suspicious approval: a token approval can permit a contract to move a particular asset. Review the permission using your wallet provider’s instructions. Disconnecting a site does not revoke existing approvals. Revoking an approval also does not repair a leaked recovery phrase. Our wallet drainer case study explains why those risks differ.
Include the email account and device in the explanation
If you lost access to email or received an unexpected account security notice, tell the relevant account provider. Get Cyber Safe recommends using the provider’s recovery process, changing compromised passwords and enabling additional authentication. Use the instructions for that service. An exchange account and the email used to communicate with its support team should not be treated as one interchangeable login.
Also disclose any software you installed or remote access you allowed during the approach. Record the program’s name if you know it and what the other person asked you to do. Ask the genuine provider which account actions are appropriate while that exposure is unresolved. This guide cannot determine the state of your device from a list of symptoms, so avoid treating an app’s removal or a stranger’s assurance as a completed security assessment.
Address identity information that was exposed
Identity information deserves its own response even when the payment issue is already reported. List the categories of information you shared, such as a document image, account statement or Social Insurance Number. Do not paste the documents or full identifiers into a general incident summary. The useful first description is what was disclosed, when, through which channel and whether you can still identify the recipient’s claimed website or account.
The CAFC’s victim guidance distinguishes financial account concerns from lost or misused identity documents and directs readers to the relevant issuers. Use that distinction when asking for help. A notification to a bank does not answer what the passport or provincial document issuer wants you to do. Equally, asking a document issuer about exposure does not replace reporting a disputed payment to the organization that handled it.
Record exposure without claiming misuse you have not seen
“I uploaded a document to the suspected website” and “someone opened an account in my name” describe different observations. Report the first accurately even if you have no evidence of the second. If a later letter, statement or account notification suggests misuse, preserve it as a new development. Record where the information came from and what you have confirmed. Do not describe a suspicion as an established new account or debt.
For an exposed SIN, Service Canada’s current guidance explains monitoring financial statements and credit reports for unauthorized use. It also distinguishes suspected exposure from documented fraud and sets out when information is needed by the SIN Program. Follow the instructions that match your circumstances rather than assuming every exposure requires a replacement number. Keep any unexpected financial activity separate from the original crypto payment in your notes.
Share documents through a verified channel
Ask the receiving organization which documents it needs and how to provide them. A request to prove your identity should be evaluated in the context of the genuine service you contacted, not accepted because a new message quotes details of the incident. Return to the independently established channel if you are unsure. You can describe the request to the organization before sending another copy of a document.
Keep a record of which organization received which supporting file. This is an organizational aid, not a claim that a particular upload is legally required or that a specific document will resolve the case. It helps you answer later questions without sending the same sensitive material indiscriminately to everyone involved. Recovery words, private keys and account passwords do not belong in this document bundle.
Save a private incident record
Keep original messages and receipts, with a short timeline that another person can follow. The CAFC recommends gathering documents and correspondence. For a crypto incident, the following record also helps distinguish the network transfer from a balance displayed on a website.
| Record | Details to save privately |
|---|---|
| Timeline | Date, time and time zone of the contact, payment and discovery |
| Payment | Asset, amount, blockchain network and any bank or exchange reference |
| Transaction | Transaction ID or hash, sending address and destination address, where available |
| Claimed recipient | Website address, platform name and the identity the person claimed |
| Communication | Original messages, emails, withdrawal demands and screenshots showing context |
| Exposed access | Whether a login, identity document, recovery phrase or permission was involved; do not copy the secret itself |
| Follow up | Provider ticket, police file and reporting reference numbers, plus dates of updates |
Do not reconnect a wallet, sign a request or pay a fee just to collect more evidence. Mark missing details as unknown. Keep the file private and provide it through verified reporting channels, not in public comments asking for help.
Make the timeline readable without rewriting the originals
Use the summary to explain the sequence, while retaining the original records alongside it. Begin with the first contact you can identify, then note the payments, access requests and the point at which you suspected a problem. You do not need to reconstruct every conversation before making the initial report. Add dates you later confirm and identify estimates as estimates. A date taken from a receipt is different from one recalled from memory.
Keep the speaker clear when summarizing a promise. Write that the contact claimed a withdrawal would be released, rather than writing that a withdrawal was approved unless you have independent confirmation. This distinction matters when a support team or investigator reads the chronology without seeing the whole conversation. The same rule applies to names, roles and companies: record the identity claimed without implying that you verified the person held that role.
The FBI’s IC3 cryptocurrency guidance identifies transaction hashes, addresses, amounts and transaction times as useful evidence. Those technical fields can help describe a Canadian incident too; the Canadian reporting routes remain below. Copy identifiers from existing records where possible rather than retyping long strings. Keep the network and asset with the identifier so the record is understandable to someone who did not see the original screen.
Distinguish what left, what returned and what was displayed
Prepare separate lines for payments you made, payments you actually received and balances claimed by the suspected platform. If the same money passed through several of your own accounts before leaving, show the sequence instead of adding every movement to the loss. Where the calculation is unclear, provide the underlying records and explain the uncertainty. Do not turn a large displayed profit into a verified amount you deposited.
Hypothetical record example: A person saves an exchange purchase receipt, an onward crypto transaction and a screenshot of a supposed investment balance. They label the receipt “purchase,” the transaction “transfer to the address supplied” and the screenshot “balance shown by the website.” They do not describe the screenshot as proof of funds held for them. If a small payment later arrives, it receives its own entry rather than erasing the earlier transfer from the timeline.
This method is a way to organize the facts, not an official formula for calculating compensation. Fees, conversions and multiple assets can make a single total hard to interpret. Preserve the original amounts and units, and label any conversion you calculated yourself. Ask the organization handling the report what measure it requires. Do not supply a confident total merely because a form or conversation seems to expect one.
Keep useful context around screenshots and messages
A tightly cropped image may omit who sent a demand or when it arrived. Preserve the surrounding conversation and the website address where available. If you make a shorter copy for a summary, retain the original too and label the copy. Avoid editing the original text to make it clearer. Put your explanation in the chronology so a reader can distinguish your interpretation from what the sender actually wrote.
Do not place passwords or recovery words in screenshots prepared for a report. If an existing record contains a secret, ask the verified recipient how to provide the relevant evidence without exposing it further. You can describe that a secret was requested or shared without reproducing it. A file that helps explain the incident should not itself become another source of account or wallet access.
Report to the right Canadian organizations
Contact local police about the suspected crime and report to the CAFC as well. The CAFC explains their different roles: local police investigate, while the CAFC collects information that assists law enforcement.
| Organization | What to ask or report |
|---|---|
| Bank or exchange involved | Payment status, exposed account access and available fraud handling |
| Local police | The suspected offence, payment trail and communications; keep the file number |
| CAFC | Submit the incident through its official reporting route, including attempted fraud |
| Provincial or territorial securities regulator | A suspected fraudulent investment offer or securities related misconduct |
Use the CAFC reporting page to reach the online reporting service. If an investment offer was involved, the CSA’s reporting guidance directs you to your local securities regulator. Regulators can investigate securities misconduct, but normally do not recover investors’ money or undo transactions.
Tell your financial institution if identity information was exposed. Follow the CAFC’s identity fraud and document guidance for the affected accounts and document issuers. Save subsequent developments under the same incident record.
Explain the same incident for different purposes
Use one consistent chronology, then make clear what you are asking each organization to do. The bank or exchange needs the payment or account issue within its service. Police need an account of the suspected crime. A securities regulator needs the investment offer and conduct you are reporting. You do not have to rewrite the story to suit each recipient, but the question at the top of the submission should match its role.
Do not assume that telling one organization automatically tells all the others. Ask which reports you should make yourself and keep a note of what was submitted. When a form asks whether the incident has been reported elsewhere, give the references you actually have. If you are still waiting for a reference, say that. Avoid inventing a case status from an automated receipt or from a message that simply acknowledges your submission.
The CSA notes that a regulator may request further documents or an interview. Keep the record accessible for that possibility. A request for more detail is an opportunity to clarify a specific point; it does not require you to investigate the entire network yourself. Ask what the recipient needs when the requested material is unclear, and explain honestly when a record is unavailable.
Help a family member without taking over their account
Start with the next unresolved action. Ask whether they are still in contact with the person requesting money, whether a payment is pending and whether any login or wallet access was shared. Focus on those facts before debating why the offer seemed convincing. A useful first contribution is helping them reach an official provider and describe the concern clearly. A complete theory of the scam is not required for that conversation.
Divide the practical work with permission
Offer to take notes while they speak to the provider, find the relevant official reporting page or organize receipts they choose to share. Agree on what help they want. Do not ask for their password or recovery phrase in order to be useful. If an organization needs the account holder to confirm something, let it explain its process directly rather than pretending to be the account holder or supplying answers on their behalf.
Keep the account holder’s observations distinct from your own. In the shared chronology, identify who received a message, saw an account screen or spoke to the provider. If you are reconstructing an event from what your family member remembers, label that source. This avoids turning a helpful summary into an apparent eyewitness account of actions you did not see. Corrections can be added later without hiding the original uncertainty.
Hypothetical family example: One person is speaking to the exchange while a relative organizes payment receipts. The relative records the questions and next steps but does not attempt a wallet transfer or negotiate with the suspected scammer. After the call, they compare the provider’s instructions with the notes and identify what is still missing. Their role is to reduce confusion, not to promise a result or demonstrate technical control over the account.
Keep the discussion focused on the current decision
If your family member still believes the promised payout is real, separate that belief from the immediate request for another payment. You can suggest checking the demand through an independently reached provider before anyone pays. Ask what evidence would answer the specific question. Repeated arguments about intelligence or blame do not produce a payment reference, a confirmed contact route or a clearer record of what happened.
Agree where the documents will be kept and who will handle follow up. Avoid creating several circulating copies containing sensitive information. If the person wants you involved in a later provider conversation, ask the organization how it permits that involvement. Do not assume that being a relative gives you authority to direct account changes or receive confidential information. Practical support can remain useful while the account holder keeps control of those decisions.
Follow up and handle an unresolved response
Follow up with the incident reference, the specific unresolved question and any genuinely new evidence. A provider ticket, police file number and CAFC report reference serve different records. Label each with the organization that issued it and the date. Keep an acknowledgment separate from a decision. This makes it easier to establish whether you are asking about an account restriction, a disputed payment, a crime report or a complaint about service.
Keep a short record of each contact
Write down the date, the channel used, the reference and the action described by the recipient. Note what you agreed to send and whether the organization gave a next step. You do not need to transcribe every exchange. Preserve the original written response, then summarize the unresolved point in your own words. If a later explanation differs, keep both versions and ask for clarification rather than silently replacing the earlier one.
Suggested follow up wording, written for this guide: “I am following up on the incident reference already provided. I have an additional record relating to the payment and need to confirm how to submit it. Please clarify the status of the action previously discussed and any information still required from me.” Add the actual reference privately. Do not describe a recovery as approved unless the organization has explicitly confirmed that outcome.
When you obtain a missing transaction identifier or correct an amount, explain what changed. Identify the earlier entry and the record supporting the correction. The purpose is to make the file more accurate, not to produce a new version that conceals a mistake. A clear correction is more useful than allowing two conflicting totals or dates to circulate without explanation. Keep the correction with the rest of your incident record.
Separate the fraud report from a complaint about the bank
If your concern is how a bank handled your request, use its complaint process as well as the incident response channel. The Financial Consumer Agency of Canada explains how to file a bank complaint, including setting out the facts and desired outcome. Its guidance also explains escalation to OBSI. FCAC itself does not resolve individual complaints. Read the current process for the bank rather than applying a bank procedure to every crypto service.
Make the complaint specific. Identify the response or action you dispute, the date you requested help and the records you believe support your concern. State what you want clarified or reviewed without presenting a refund as an automatic entitlement. A complaint about the provider’s handling and an investigation of the suspected scammer answer different questions. Keep their references separate even when both arise from the same payment.
Record what remains unknown
An unresolved case can leave several different questions open. You may know that a payment completed but not who controls the destination. You may have secured one login while still awaiting advice about a device. Write these as separate open items with the organization you have asked about each. Do not collapse them into “nothing has happened,” or assume that one useful response has settled the entire incident.
Understand recovery limits before paying anyone
A completed blockchain transfer cannot simply be cancelled by wallet support. That does not mean recovery is impossible in every case. In a May 2022 account of an earlier investigation, the RCMP described police tracing, seizing and returning stolen cryptocurrency. That historical outcome is not a forecast for another victim.
Be cautious if someone contacts you claiming they have already found your funds. CIRO and the CAFC warn about recovery fraud involving fees, remote device access and impersonation of regulators. A transaction screenshot or official looking badge does not establish authority to retrieve money.
Do not pay a stranger to unlock a refund. Verify any claimed agency independently and preserve the new approach as evidence. If you are still assessing the original request, use the Canadian crypto scam warning signs.
Separate tracing, control and return of funds
These are different claims. A person might show a transaction on a public record without demonstrating that they can control the funds or return them to you. In the RCMP account above, the recovery involved an investigation and a seizure, not a victim pressing a cancellation button. Do not treat an image with arrows between wallet addresses as proof that the sender has authority to take the next step.
Ask what an unsolicited recovery contact is actually requesting from you. A new payment, a wallet signature, remote access or a secret is a new exposure to assess, even when the conversation begins with sympathetic language. Verify a claimed agency through a separately established official route. Do not let the contact supply both the claim and the only means of confirming it. Keep their messages as a separate development in the original incident record.
The US FTC’s refund scam guidance describes unsolicited recovery offers that demand payment first. Hypothetical recovery example: After reporting a loss, a person receives a message claiming that the funds have been located. The sender attaches a transaction image and asks for a release payment. The useful question is not whether the image looks technical. It is whether the claimed organization independently confirms the contact and process. Until that is established, the message remains an unverified approach, not a confirmed stage of recovery.
Do not borrow or move more money solely to preserve an alleged chance of getting the original amount back. A deadline supplied by the same unverified contact does not resolve the question of authority.
Check a recovery offer without sending more money
Verify the claimed organization through a channel you find independently. A business name, an investigator’s name and the website or email contacting you are separate facts. A real organization’s existence does not establish that this person represents it. Search the organization yourself, use its published contact route and ask whether it sent the specific request. Do not use the callback details inside the disputed message as your only check.
The FTC’s recovery scam guidance warns about requests for payment or personal information to recover money already lost. CIRO’s Canadian warning describes impersonation and purported assistance. Neither an official looking document nor a claim that funds are already located substitutes for independent verification.
Ask what the proposed service would actually do. A tracing report, an investigation, a court process and a transfer of money back to you are different deliverables. Someone may be able to point to public transactions without controlling an address. If they claim they can release funds, ask what establishes that authority and verify it outside their own documents. Do not treat screenshots of a wallet balance as proof of custody.
Use this private worksheet before replying. Record descriptions and references, not passwords, seed phrases, identity document copies or complete payment credentials. The worksheet is an aid to organizing a question; it does not certify a service as legitimate when every row is filled.
| Check | What to record privately | What remains unresolved |
|---|---|---|
| Claimed identity | Organization, representative and exact domain | Does an independently reached organization confirm this approach? |
| Claimed case | Existing report reference and who issued it | Does the actual reporting organization recognize the reference? |
| Proposed work | Tracing report, legal representation, investigation or return of funds | What concrete deliverable is promised, and who can provide it? |
| Authority over funds | The explanation supplied for release or transfer | Can the claimed authority be confirmed independently? |
| New payment request | Amount, stated purpose and destination type | Why is the payment necessary, and who actually receives it? |
| Access request | Whether software, screen sharing, a signature or recovery words are requested | What would that access allow? Do not supply the secret to check it. |
| Independent response | Date and source of a response you obtained yourself | Which parts were confirmed and which were only repeated by the offeror? |
| Next action | Contact your existing provider or reporting organization | What can be done without sending money or granting new access? |
Download a blank recovery offer worksheet. It is a plain text file you can keep locally or print. The download sends no incident information to NEXT LEVEL. Store completed notes privately and use only verified recipient channels if an organization later needs them.
An unresolved row is a reason to pause the requested action and ask the relevant organization. It is not a score to average against reassuring rows. A real address, a plausible fee and a professional document can coexist with a false identity claim. Keep the identity question open until it is answered independently.
If you already paid the recovery contact or granted access, add that as a separate event to the original incident record. Contact the actual bank, exchange or account provider involved and explain the new transfer or access. Do not let a second person’s promise delay the response to the first loss, and do not send a final payment simply because previous fees have already been paid.
Questions after a crypto scam
Should I wait until I have every transaction detail to report it?
No. Contact your provider promptly with what you know. Gather the missing records afterward and ask how to add them to the incident. Keep facts separate from guesses.
Begin with the account or payment you can identify and describe the uncertainty. If a date is approximate or an amount came only from the suspected website, label it that way. The next useful task is obtaining the supporting record, not delaying contact until the narrative sounds complete.
Can I report an attempt if I never sent money?
Yes. The CAFC accepts reports from witnesses and victims. Preserve the approach without sending a test payment or continuing the conversation to prove your suspicion.
State clearly that no payment was made. If you shared information or granted access despite making no transfer, include that separately. “No money sent” does not describe everything that may have happened during the interaction, so avoid using it as a substitute for the access details.
Is changing my wallet password enough after sharing my seed phrase?
No. A new app password does not change the exposed recovery words. Follow your wallet provider’s compromised wallet process rather than continuing to use that phrase as if it were private.
Tell the verified support channel that the phrase was exposed without sending it again. An account password change and a wallet recovery phrase concern different forms of access. If you are unsure what you shared, describe the screen and action rather than copying a secret into a message for someone to identify.
Does a police or CAFC report guarantee reimbursement?
No. Reporting supports investigation and information gathering. Whether money can be recovered depends on the circumstances; neither a report number nor a private recovery promise establishes that funds will be returned.
Keep the acknowledgment because it helps with follow up, but read what it actually says. Receipt of a submission is different from a decision about your payment. If an update is unclear, ask the issuing organization which action it confirms instead of relying on someone outside the case to interpret it as a refund approval.
What if the website has disappeared before I saved everything?
Describe what you still have: payment records, messages, browser history or receipts. Do not reconstruct missing terms from memory as if they were an exact copy. Record that the website is no longer available to you and when you noticed. Ask the recipient of your report which remaining records are useful. Do not pay someone who claims they can restore the website or retrieve evidence only after receiving your wallet access.
Should I post the full story publicly to find other victims?
Prepare a private version for verified providers and reporting organizations first. Public discussion should not expose recovery words, passwords, identity documents or a complete sensitive evidence bundle. If you later choose to describe the experience publicly, separate that choice from the material needed for the official report. Finding someone with a similar story does not establish their identity, authority or ability to recover your payment.
Sources and further reading
- Canadian Anti Fraud Centre: What to do after fraud
- Canadian Anti Fraud Centre: Report fraud and cybercrime
- Coinbase: Lock or unlock your compromised account
- MetaMask: Unauthorized transactions and compromised wallets
- MetaMask: What is a token approval?
- MetaMask: Disconnecting a wallet from a dapp
- Canadian Securities Administrators: Reporting wrongdoing
- RCMP: Police help a crypto fraud victim recover funds
- CIRO: Recovery scams on the rise
- Get Cyber Safe: Recovering a hacked account
- Service Canada: SIN fraud and data breaches
- IC3: Cryptocurrency evidence and reporting
- Financial Consumer Agency of Canada: Bank complaint process
- US Federal Trade Commission: Refund and recovery scams