Private digital intelligence bureau Lawful OSINT · Cyber monitoring · Due diligence
Checking a payment request with a phone and documents

Is the requested action legitimate?

First action

Pause payment, document transfer or remote access. Reconnect through a known channel found outside the received message.

Useful output

A record of the original request, independently reached contact, verified destination and payment or access decision.

Interpretation limit

A legitimate company, genuine invoice or correct logo does not authenticate the request. If a transfer has already occurred, contact the bank through its official channel immediately.

Keep the decision traceable

Record the fact being checked, the material reviewed, what remains unknown, the person responsible and the next review trigger. A result is useful when another reader can understand why an action was chosen and what would change it.

Consult primary source portals

Match the situation to a check and a usable output

SituationCheckRecord to keep
Changed bank detailsPause the change; call a known contact using a previously retained number.Contact identity, confirmed destination and approval independent of the message.
Recruiter demanding an advanceVerify the opening through the employer and confirm the recruiter’s mandate.Job reference and independently obtained response.
Support requesting remote accessClose the solicitation and independently open official support.Original message and actions taken; notify IT if access was granted.
Urgent fundraising storyIdentify organiser, beneficiary and payment route.Source of need, donation destination and remaining unknowns.

When to pause and escalate

Requests for secrecy, urgency or bypassing normal approval warrant a pause. Do not let pressure choose the verification channel. If funds have already been sent, immediate contact with the bank takes priority over lengthy OSINT research.

Prepare a source and decision log →

FAQ

Does an authenticated email make the request safe?

No. A genuine account can be compromised. Check the action and beneficiary independently.

What belongs in an initial report?

Original request, relevant times, action taken and a short timeline. Exclude passwords and temporary codes.

Reading technical evidence

Read Authentication-Results within its trust context

A result copied into an email is not automatically trustworthy. Its origin in the mail chain matters.

Field or situation and its interpretation
Observed itemWhat it means
authserv-idIdentify the service claiming to have performed the check.
spf=pass or dkim=passRead the mechanism and domain concerned, rather than just the word pass.
An upstream headerAsk the mail team which results originate from its trusted services.

Preserve the original message and headers. Even a trustworthy result does not authorise a requested bank-account change.

RFC 8601, § 7

Fictional learning scenario

A known supplier sends new bank details

The message is in the usual thread and quotes the exact invoice amount. The new account has not been approved.

  1. Observed fact
  2. Missing evidence
  3. Independent check
  4. Decision condition

What is established?

The supplier and invoice are known. Authorisation of the bank change remains unknown: these are three separate facts.

Which check matters?

Call the contact using a previously retained number, confirm the change under the internal procedure and retain the approval reference.

What changes the decision?

An independent callback contradicts the message: keep the change paused and pass the original to the responsible person. Independent confirmation allows the usual process to resume; it does not establish that the entire mailbox is secure.

The shortcut to avoid

A logo, signature, conversation thread or technically authenticated email cannot replace approval of the requested action.

Further reading

Editorial resources on other sites