What happened
A mobile preview can omit the details needed for a safe decision. Begin with the installed app and account record, rather than the alert’s branding or urgent wording. First identify whether it concerns a login, a trade, or another account event. A notification received at the expected time is still incomplete evidence if you cannot match its operation and active account.
What to check
Open the Steam app directly and confirm the signed-in account. Find the corresponding request and read its full details. Compare them with the action you deliberately initiated. If no matching record exists, avoid external links and investigate the message separately. If the account differs from the one you intended, resolve that context before approving anything; do not assume all alerts on the device belong to the same profile.
Worked example
For example, the phone preview asks for confirmation without showing a recipient. Inside the app, you discover a different account or item direction from your intended operation. The missing preview details were precisely what mattered. In another case, a chat message imitates a mobile notice but has no matching Steam record. Treat it as a separate message, not as evidence that the app requires an urgent trade.
Result and next step
The useful outcome matches the alert to a known account and intentional action, or keeps the unexplained request unapproved. Record the alert time and request reference if one exists; state honestly when no match was found. Read Steam account security recommendations and trading practices. A legitimate notification cannot authenticate an unrelated chat instruction, and a verified recipient link cannot authorize a different operation hidden behind an abbreviated preview.