Interactive checker inputs and results
Before checking: This is a warning-sign checklist, not a fraud probability test. Even one unexpected request for a verification code, account transfer, or difficult-to-reverse payment is enough to pause and verify independently. Never use a phone number or link supplied in the suspicious message to confirm its legitimacy.
Interactive calculator unavailable: JavaScript is required to process your own inputs. The worked example, calculation assumptions and related guidance on this page remain available without JavaScript.
Example: one dangerous payment request is enough to stop
A fictional message appears to be from a bank and asks you to transfer funds to a “safe account.” Even if only that single warning sign is checked, do not send money based on the message. Independently contact the institution using a phone number or app you already trust. Counting one sign does not make the request “low risk”; this tool reports a checklist count, not fraud probability.
A different message might involve an unexpected sender, pressure to act quickly, and a request for a verification code. Three selected items mean three warning signs selected, not a 30% or 60% chance of fraud. The analyzer cannot verify the sender, transaction or destination; and selecting zero items never certifies legitimacy.
If money has already been sent: Immediately contact the payment institution through its official channel and report the situation. Save a masked transaction reference, timing and communications. Use the FTC’s response guidance and payment-fraud decision paths.
1. Pause the request
Do not send a new payment, password or verification code.
2. Verify independently
Use a number or app you already trust—not contact details in the message.
3. Record the outcome
Keep the verified purpose, destination and next action in a masked local record.
How to interpret the result
Use each selected warning to decide what to verify. The analyzer cannot authenticate the sender, payment destination or transaction. No selection certifies legitimacy; use the response plan below if money or account access has already moved.
For independent guidance, see the FTC’s mobile payment app scam guidance and its advice on common scam warning signs. When a request appears to come from a person, bank, business, or agency you know, verify it using contact information you independently know to be genuine.
For a payment already initiated or an account that may be compromised, use the four-situation response plan below.
A response plan for four different payment situations
The number of selected warning signs is not a probability score. Choose what to do based on the specific request and whether money or account access has already moved, not a high or low badge.
- Unexpected request before payment: Stop. Confirm the person, destination and purpose through a number or app you independently know is genuine. Do not send a code, new transfer or “account protection” payment.
- Transfer initiated but pending: Contact the payment provider and funding bank promptly using verified channels. Ask whether cancellation or a hold is available. Do not assume a pending display means the transfer is reversible.
- Payment you authorized after deception: Report the suspected scam immediately and ask about available recovery or dispute procedures. Recovery is not guaranteed; keep the time, amount and a masked transaction reference.
- Activity initiated by someone else: Secure the account, notify the institution and request an investigation. Rights and timelines can differ by the payment method and circumstances, including whether the transfer was legally unauthorized.
What evidence is useful—and what is unsafe to share?
Keep a local timeline of when the request arrived, who claimed to contact you, the provider you reached independently, what was reported and each case number. Use masked references rather than storing passwords, one-time codes, full account numbers or identity documents in the checker. If someone offers to recover the money for an advance fee, treat that as another potential scam.
Use the FTC’s payment-app safety guidance and ReportFraud.ftc.gov for U.S. consumer-scam reporting. For account misuse consult the identity-theft response guide. This checklist cannot authenticate a real message, resolve a dispute or guarantee that funds will be returned.