Skip to main content

Identity Verification with sajn ID

Use sajn ID to verify customer identities using Swedish BankID before granting access to services or completing transactions.

Overview

sajn ID provides two verification methods:
  • SSN-based: Verifies identity AND Swedish personal number
  • Name-based: Verifies identity and name match without requiring SSN

Quick Start

Create and send a verification request:
The user receives an email with a verification link and completes BankID authentication.
Creating a verification immediately sends it to the recipient over the chosen channel — there is no separate send step.

Use Cases

Customer Onboarding

Verify identity during account creation:

Age Verification

Verify someone is 18+ without collecting SSN:

Pre-Contract Verification

Verify identity before allowing document signing:

SSN-Based vs Name-Based

When to Use SSN-Based

Use SSN-based verification when you:
  • Need to verify the exact person (e.g., financial services)
  • Are legally required to collect and verify SSN
  • Need to match against government databases

When to Use Name-Based

Use name-based verification when you:
  • Only need to verify identity, not specific SSN
  • Want to respect privacy (GDPR-friendly)
  • Just need age verification

Verification Flow

  1. Create verification via API
  2. User receives link via email or SMS
  3. User clicks link and opens verification page
  4. User authenticates with BankID app
  5. Verification completes and you receive webhook notification
  6. Retrieve results via API

Checking Verification Status

Poll for status updates:
Response when pending:
Response when completed:

Webhook Integration

Receive real-time notifications:

Linking to Contacts

Link verifications to existing contacts for audit trail:
This creates a permanent record in the contact’s history.

Implementation Example

Complete verification workflow:

Security & Privacy

SSNs are encrypted at rest and only accessible to authorized users.
Verification tokens are single-use and expire after completion or timeout.
Complete audit trail tracks every step of the verification process.
Name-based verification minimizes personal data collection per GDPR principles.

Best Practices

Reference IDs

Always include a reference to link the verification to your workflow and trace it for compliance.

Control Expiry

Set expiresAt to control how long the verification link stays valid (defaults to 7 days).

Minimal Data

Use name-based verification when SSN isn’t legally required.

Webhooks

Use webhooks instead of polling for better user experience.

Troubleshooting

Verification Not Received

  • Check spam/junk folders
  • Verify email/phone is correct
  • Check verification wasn’t already used
  • Look for delivery failures in dashboard

BankID Failed

Common reasons:
  • User canceled authentication
  • BankID app not responding
  • Wrong personal number provided
  • BankID account issues
The user can retry by clicking the link again.

Name Mismatch

If name-based verification fails due to mismatch:
  • Double-check spelling in request
  • Ask user for their exact registered name
  • Consider SSN-based verification for certainty

Next Steps

sajn ID Concept

Learn more about sajn ID

API Reference

Explore the sajn ID API