Verification
Conceptual framing for identity checks—always upload documents inside official Secure flows.
Individual (mock)
Individual · identity verification queue (mock)
Profile basics
DoneIdentity document (demo)
PendingExample review banner
Selfie similarity check
PendingIllustrative only
Final confirmation
PendingIllustrative mock • not signed-in data • not a real screenshot
- Document review states shown are illustrative for education only.
- Submit real documents strictly through authenticated verification flows.
Overview
Verification exists to protect you and the network from stolen identities and synthetic accounts. Community threads can explain stages and timeline language; they are never a place to upload ID photos, selfie videos, or bank letters.
What verification is protecting
Fraud resistance
Strong identity signals let BinaxPay release higher limits and faster rails without manual review on every send.
Regulatory alignment
Partner banks expect verifiable Individuals—verification is prerequisite plumbing, not a personal judgment.
Typical review flow
Submitted
You finish the in-app questionnaire and upload authorized documents privately.
Automated screening
Systems validate format, face match quality, or document anomalies.
Human review queue
Edge cases queue for analysts—holiday spikes can extend windows for everyone.
Outcome
Approved, additional info requested, or denied with a category you see in-product only.
Preparing calmly
- Complete captures in good lighting; blur and glare are frequent retry reasons.
- Ask Community about averages for “Submitted → first update,” not about your adjudication payloads.
- If prompts look phishy versus authenticated flows, stop and escalate through Support—not DMs.
Questions that thread well vs poorly
Helpful framing
“How long do re-verifications usually take after a legal name change?”—no documents required.
Risky framing
Posting denial PDFs or screenshots asks peers to handle data that should stay in Support.