Security
Stay ahead of impersonation tactics and learn how freezes differ from bans—still route incidents through Support.
Individual (mock)
Individual · security center (mock)
Mock reminder: impersonators rarely match official banners or lock icons you see behind sign-in.
Illustrative mock • not signed-in data • not a real screenshot
- Toggles emulate safe-device patterns without reading your account settings.
- Apply real controls only from authenticated BinaxPay security surfaces.
Overview
Security layers strong authentication, device awareness, freezes, and human review when signals look suspicious. Use Community for education and skepticism—not for incident response that requires SOC tooling or reversing unauthorized movement.
Daily habits that pay off
- Prefer phishing-resistant MFA (security keys or OTP apps) over SMS wherever offered.
- Rotate passwords whenever reuse or coercion is plausible—never paste old hashes publicly.
- Freeze cards from official apps at the first suspicion; unfreeze only after validating history privately.
- Review active device lists periodically and revoke sessions you cannot attribute.
If something feels wrong
Isolate
Stop interacting with suspicious links/SMS threads; switch to LTE if Wi-Fi feels tampered.
Freeze / revoke
Use authenticated surfaces to halt cards or remote shells before debating next steps aloud.
Report
Open Support fraud or dispute queues—they can ingest evidence portals that Community lacks.
Document
Write a chronological narrative referencing category labels—not raw OTP strings or PAN fragments.
Teachable narratives peers share
Phishing pings
Compare legitimacy signals—“Support never chats payment from a personal WhatsApp”—without dumping SMS payloads.
Travel friction
Geo-blocking sometimes pairs with Cards topics; discuss toggle concepts, not itineraries with ticket costs.