Pause Before an Unexpected Payment Request

Start by describing the requested action in plain language using information already visible without engaging further. The sender may ask for money, a change of payment information or sensitive information supposedly needed to receive earnings. Do not collapse those into a vague label such as account update. The specific action matters because each has consequences that a reassuring subject line does not explain. Keep the preparation private and avoid collecting more of the message through suspicious links or attachments.

Separate the action from the reason the sender gives. A claim that a payment is delayed is not proof that you must pay a release fee. A familiar project reference is not proof that a new financial instruction came from the real organisation. Record the stated reason as a claim, with any uncertainty visible. This guide does not decide whether a particular sender committed a crime or determine the legal status of an invoice.

Identify whether you have already acted. If a transfer, disclosure or access event may have occurred, use the appropriate genuine response route promptly rather than remaining in a pre-action exercise. The FTC response resource supplies US context, but the actual bank, provider and country govern the real next steps. For a fictional practice message, the useful result is a clear action-and-claim pair. It should show the decision you are being asked to make without accepting the sender's account as the starting truth or treating an alarming deadline as permission to skip verification.