Using Snap
How Detection Works
Section titled “How Detection Works”Athenty Snap runs a content script on every page you visit. The script scans the visible text for identity fields — names, email addresses, and phone numbers — and reports findings to the extension.
The extension icon in your browser toolbar reflects the current state of the active tab:
| Icon state | Meaning |
|---|---|
| Gray | No identity fields detected (or extension is inactive) |
| Colored | Identity fields detected — badge shows field count |
Colored + … | Verification request being submitted |
Colored + ✓ | Verification submitted successfully |
Colored + ! | Submission error — click to retry |
Detection happens automatically when a page loads. For pages that load content dynamically, the extension also monitors DOM changes and re-scans when new content appears. To manually trigger a scan at any time, press Ctrl+Shift+Y (Windows/Linux) or Cmd+Shift+Y (Mac).
Reviewing Detected Fields
Section titled “Reviewing Detected Fields”When the icon turns colored, click it to open the extension popup. The popup shows:
- Detected Identity — the fields found on the page (name, email, phone), each with a type label and edit button
- Matched Client — if an existing client in your Athenty account matches the detected email or name, their record is shown automatically
Editing a Field
Section titled “Editing a Field”If a detected value is incorrect or partially captured, click the pencil icon next to the field to edit it before submitting.
Client Matching
Section titled “Client Matching”When the extension detects an email address, it automatically searches your Athenty client records for a match. If a match is found, the client’s name and record details appear below the detected fields.
You can also manually search for a client by name or email using the search field in the popup. Select a client from the results to link the verification to their record.
If no client match exists, the verification is submitted with the detected information only, and a new request is created in your dashboard.
Submitting a Verification
Section titled “Submitting a Verification”Choose a Verification Type
Section titled “Choose a Verification Type”At the bottom of the popup, select either:
- IDV — Identity Verification: confirms the subject’s identity with document verification and biometric matching
- KYC — Know Your Client: full KYC flow including PEP/sanctions screening, beneficial ownership, and enhanced due diligence
Your default type can be set in the extension settings (see below).
Duplicate Check
Section titled “Duplicate Check”Before submitting, the extension checks whether an active verification already exists for the detected email. If one is found, a warning appears. You can proceed anyway or cancel.
Send the Request
Section titled “Send the Request”Click Send IDV Verification or Send KYC Verification. The extension:
- Sends the request to your Athenty account via the API
- Changes the icon badge to
✓for 3 seconds, then returns to the field count - Shows a browser notification confirming the request was created
- Opens a link to the new request in your Athenty dashboard (accessible by clicking the notification)
Extension Settings
Section titled “Extension Settings”Click the gear icon in the top right of the popup to open Settings.
Default Verification Type
Section titled “Default Verification Type”Set whether new verifications default to IDV or KYC. This determines which button is pre-selected when you open the popup.
Auto-Scan
Section titled “Auto-Scan”Toggle automatic scanning on or off. When off, pages are not scanned on load — you must press Ctrl+Shift+Y to trigger a scan manually. Useful if you work on pages with sensitive content you do not want scanned automatically.
Connected Account
Section titled “Connected Account”The Settings panel shows your connected organization name and your user role. Click Disconnect to unlink the extension from your account and return to the pairing screen.
Security Details
Section titled “Security Details”- Token storage: Access and refresh tokens are stored in
chrome.storage.session— encrypted, never synced to your Google or Firefox account, and cleared when the browser closes. - Token lifetime: Access tokens expire after 15 minutes and are refreshed automatically. Refresh tokens last 30 days.
- Scope: Extension tokens are scoped to
requests:rw,clients:rwonly — they cannot access billing, org settings, or user management. - Page content: Page text is processed entirely in your browser. Nothing from the page is sent to Athenty servers unless you explicitly click Verify.
- Revocation: Each extension token can be revoked individually from Settings → General → Browser Extension in your Athenty dashboard without affecting other extensions or API integrations.