Skip to content

Governance. Passed. See the Governance report.

Money at risk. What to do right now

Take a breath. You are not alone.
This page helps you act fast without panic.

Use this topic if you or someone you support:
  • Shared card details, a bank login, or a one-time code
  • Approved a payment or transfer and now regret it
  • Think money may be at risk after a call, text, email, or a fake website

If you are not sure what happened, start with: 2-minute check

If you feel in immediate danger

Call 999 or 112.

Do these 3 things first

If you are helping someone else, do not ask them to share a one-time code with you. If possible, sit with them and let them type it themselves.

1. Stop the contact

  • Stop replying. Stop answering calls.
  • Do not click again. Do not download anything.
  • If someone is telling you what to do on the phone, hang up.

2. Protect your money

If this involves your bank account, card, or a one-time code, treat it as urgent.
A one-time code is the short code you get by text or in an app to approve a sign-in or payment.

  • Call your bank now using a trusted number. Use the number on the back of your card, your official banking app, or your bank’s official website.

  • Tell them what you shared and when.

  • Ask them to:

    • Freeze your card or online banking (if needed)
    • Try to stop or reverse any pending payment or transfer
    • Block new payees or transfers until your account is secure
    • Watch for suspicious activity

Say: “I think I’ve been scammed. Please freeze my account or card. Please try to stop or reverse any pending payments. Please block new payees.”

If you cannot get through straight away, keep trying or use another official contact method listed by your bank (for example in your official banking app or on your bank’s official website).

3. Secure your accounts

  • Change the password on the account you were asked to “verify”.
  • Then change your email password too. (Email is often the key to resetting other accounts.)
  • Turn on two-factor authentication where you can.

Choose what happened

Open the first match. If more than one happened, start at the top and work down.

You shared a one-time code, PIN, password, or bank login
  • Call your bank and ask them to lock down your account.
  • Change your banking password and your email password.
  • Check your bank account for new payees, new devices, or new settings.
You typed card details into a website
  • Call your bank or card provider.
  • Ask them to cancel the card and issue a new one if needed.
  • Check recent transactions and report any you do not recognise.
You sent money already
  • Call your bank immediately. Ask if the payment can be stopped or reversed.
  • Save any transaction references, screenshots, or receipts.
  • If you were pressured or threatened, you can also report to your local Garda station.

Important

  • Save copies of messages, emails, and transaction details (for example screenshots).
  • Do not share your password, PIN, or one-time codes with anyone.
You clicked a link, opened an attachment, or installed an app

Go here next: Malware, remote access, ransomware

Save evidence (optional). 60 seconds

If you can, capture a little evidence now. It makes reporting simpler later.

  • Take a screenshot of the message and sender details.
  • Note the date and time.
  • Keep any bank alerts or transaction screenshots.

Important

  • Save copies of messages, emails, and transaction details (for example screenshots).
  • Do not share your password, PIN, or one-time codes with anyone.

Tip

If you want a simple place to write everything down, use: Report and record. Simple incident log

If you want to report it

  • If money is involved, your bank should advise the best next reporting step.
  • If you believe a crime happened, report to your local Garda station and bring your evidence.

When you are steady again

Governance report

AI governance. Passed
Run date: 2026-01-29 Profile: B
Read governance summary Open Issues checklist

Internal QA artefacts. Included for traceability.

What this means
  • Sources were registered and validated.
  • External claims were checked against inspected snapshots.
  • Any fixes required are captured in the PR checklist.